Support > About cloud server > Getting persistent "Internal Error" messages on your US-based cloud server? A guide to potential causes and troubleshooting steps.
Getting persistent "Internal Error" messages on your US-based cloud server? A guide to potential causes and troubleshooting steps.
Time : 2026-11-17 15:43:12
Edit : Jtti

After purchasing a US-based cloud server, one of the most frustrating experiences is attempting to connect via SSH or Remote Desktop, only to be met with a cold, recurring "Internal Error" or "Connection Refused" message. Such prompts are notoriously vague—they offer no indication of whether the issue stems from a network outage, an incorrect password, or a system crash. In essence, your connection request has been intercepted, dropped, or rejected somewhere along the path before reaching the target service. The root cause could lie anywhere: your local network, cross-border routing, the cloud platform’s security groups, the system firewall, or even the remote service process itself having unexpectedly stopped.

The most efficient way to diagnose such issues is to troubleshoot layer by layer—moving from the outside in, and from the network to the application.

Layer 1: Network Connectivity

Avoid making blind changes to your local configuration. Your first step should always be to verify that a basic network connection exists between your device and the server.

Use `ping` to test basic connectivity. Run `ping <your-server-IP>` from your computer. If the ping succeeds, the basic routing is functional, and the issue likely resides at the port or service level. If the ping fails, do not immediately assume the server is down; some cloud platforms disable ICMP by default, and network congestion—common on US-bound routes during peak hours—can also cause temporary connectivity issues.

Use `MTR` to trace the network path. If a ping fails or latency is extremely high, run `mtr -rwzc 100 <your-server-IP>` to identify the specific hop where packet loss begins. If packet loss consistently occurs during the cross-border segment (such as at an international gateway node), the problem lies with the network path itself, not your server configuration. This is a key distinction when troubleshooting US-based servers versus domestic ones: the physical distance and complex routing paths involved in cross-border connections can significantly extend TCP retransmission timeouts, causing "Internal Errors" to surface repeatedly whenever the network link becomes unstable.

Layer 2: Cloud Security Groups and System Firewalls

This is the most frequent point of failure and the most common technical root cause for "Internal Errors." Security groups on a cloud platform and firewalls running inside a server (such as `iptables`, `ufw`, or `firewalld`) are two independent rule systems. You must ensure that the relevant port—SSH (default: 22) or RDP (default: 3389)—is permitted in both systems for external requests to successfully reach the remote service.

A common pitfall is allowing a port (e.g., via `ufw allow 22`) inside the server while failing to add a corresponding inbound rule to the cloud platform's security group. In this scenario, external requests are dropped by the cloud platform before they ever reach the server's network interface, meaning the internal firewall rules never even come into play.

Troubleshooting: Log in to the Jtti console and verify that the inbound rules for the security group associated with your instance are set to "Allow" for TCP port 22 (Linux) or 3389 (Windows). If you are unsure, you can temporarily set the inbound rules to "Allow All" for testing purposes. If connectivity is restored, the issue lies with your security group configuration; you can then proceed to tighten the rules one by one.

Layer 3: Is the remote service actually running?

If the ports are open but the connection still fails, the remote service process may not be running, or it might be listening on an unexpected port.

For Linux (SSH): Log in to the server via the VNC/Web terminal in the Jtti console (an out-of-band management channel that bypasses SSH). Run `systemctl status sshd` (or `systemctl status ssh` on Ubuntu). If the status is `inactive` or `failed`, try running `systemctl start sshd` and check for any error messages. Additionally, use `ss -tlnp | grep :22` to confirm that port 22 is in the `LISTEN` state. If the port is not being listened on, there may be a syntax error in the configuration file; you can use `sshd -t` to identify and correct such errors.

For Windows (RDP): An "internal error" in Remote Desktop often has specific causes. After logging in via VNC, first check `services.msc` to ensure that the "Remote Desktop Services" service is running. RDP relies on TLS for encryption negotiation. If the server’s self-signed RDP certificate is corrupted or expired, or if the TLS protocol version negotiation fails, an "internal error" may occur during the handshake phase. Additionally, incorrect permissions on RDP machine key files—such as an accidental change in the ownership of the `MachineKeys` folder—can also cause connection failures.

Layer 4: "Passive Disconnection" Due to Exhausted System Resources

One often-overlooked scenario is the exhaustion of server resources, where the OOM (Out-of-Memory) Killer terminates the `sshd` or RDP service process, rendering remote connections impossible.

After logging in via VNC, use `free -h` to check memory and swap usage, and employ `top` or `htop` to identify any anomalous processes consuming excessive CPU or memory. If the system is terminating processes due to insufficient memory, you should optimize your application's memory configuration or increase the server's RAM. Similarly, if disk usage reaches 100%, the system may be unable to write to system logs or temporary files, causing service processes to exit unexpectedly; you can quickly verify this using `df -h`.

Why Are "Internal Errors" More Frequent with U.S.-Based Servers?

Setting aside configuration errors, servers located in the United States face greater challenges regarding connection stability compared to those in China or other Asian regions. High physical latency across international links—typically exceeding 130ms—amplifies the TCP protocol's sensitivity to packet loss. If the server's return path experiences congestion during evening peak hours, TCP may frequently trigger timeout retransmissions. If an SSH or RDP connection reaches the client-side timeout threshold while waiting for a response, the user will encounter an "internal error" or a dropped connection.

Prevention Is Better Than Emergency Repair

Always maintain access via VNC or a console. Regardless of how convenient SSH or RDP may be, remember that the VNC console provided by your cloud platform serves as your final fallback. Before modifying any configuration that could affect connectivity, verify that you can successfully log in via VNC.

Maintain Both "Old and New" Paths During Changes. When changing an SSH port, keep both the old and new ports in your configuration and ensure both are permitted in your security group. Only after successfully connecting via the new port should you disable the old one. A "one-size-fits-all" approach is the primary reason users end up locking themselves out.

Verify your connection using a test IP. Jtti’s US nodes provide test IPs (e.g., 177.3.40.254). Before making a purchase—or whenever you encounter connectivity issues—use MTR to perform a local traceroute. This allows you to confirm whether the return path consistently routes through the 59.43 CN2 GIA nodes and whether packet loss during evening peak hours remains within an acceptable range.

An "internal error" is merely a generic, catch-all notification. By systematically investigating network reachability, security groups and firewalls, service process status, system resources, and authentication configurations, you can pinpoint the root cause of most connection issues within minutes. Furthermore, opting for a CN2 GIA connection with low packet loss—paired with an underlying platform that delivers full, uncompromised resources—can significantly reduce the frequency of such errors from the outset.

Relevant contents

Does your personal website need a dedicated IP address? A comprehensive look at the pros and cons of a dedicated IP. How Do DE-CIX and AMS-IX Differ? An In-Depth Comparison of Scale, Architecture, and Ecosystem Migrating from Traditional Shared Hosting to Unmanaged VPS: Four Major Gaps to Bridge and an Upgrade Guide What Is a Data Processing Agreement (DPA)? A Compliance and Security Framework That Cloud Server Users Must Understand Comprehensive Guide to Common Default Ports and Port Configuration Strategies for Multi-IP Servers in Website Clusters Locked Out of Your Server? A Guide to Recovering Access After Losing SSH/RDP Connectivity—Including Out-of-Band Rescue via VNC Can’t connect to a server port? A deep dive into common reasons for port unreachability and blocked access How to Open Ports on a Cloud Server? A Guide to Configuring Both Security Groups and System Firewalls End-to-End Troubleshooting of Memory Errors in Multi-Container Docker Environments: From Tracing 'OOMKilled' Events to Implementing Resource Isolation with Jtti Reimagining DNS Traffic Steering for Bypass Gateways with Rust: A Practical Guide to Preventing DNS Poisoning and Leaks
Go back

24/7/365 support.Here for you 24/7/365.

Support