Server not connected to ServerPilot

If your server shows as “Not connected” in ServerPilot, the cause is usually one of the following reasons:

1. Your server is down or offline at your cloud provider.
2. Your server is not resolving DNS names correctly.
3. Your server’s firewall or server provider’s firewall has been configured to block outbound traffic.
4. Your server’s CPU is overloaded.
5. Your server ran out of memory.
6. Your server’s disk is full.

Resolve “not connected”

To resolve the problem, the first thing to do is to reboot your server at your cloud provider.

If the server does not come back online, even after rebooting, contact support.

Determine the cause of the problem

To determine if the server’s CPU is overloaded or if the server ran out of memory, check your server’s monitoring dashboards.

How a server connects to ServerPilot

Your server communicates with ServerPilot by opening encrypted network connections to ServerPilot. ServerPilot does not initiate connections to your server.

When a server shows as “Not connected” in ServerPilot, this means the server is not initiating connections to ServerPilot.