Knowledgebase article

My server isn't responding. What should I do?

Your server has gone quiet: websites don't load, and SSH won't connect. Take a deep breath. Here's how to find out what's wrong, step by step.

1. Is it just you?

  • Check Network Status in Romeo's client area for known issues or maintenance.
  • Try from another network (your phone's mobile data). If it works there, your own IP may be blocked by the server's firewall, often after too many failed logins.

2. Can you reach the server at all?

From your computer:

ping your-server-ip
  • No reply? The server may be down, or ping may be blocked by your firewall. Go to step 4.
  • Replies come back? The server is alive, so a service has stopped. Go to step 3.

3. The server is alive, but websites or SSH aren't

If you can still log in with SSH:

systemctl status httpd     # or nginx / apache2
systemctl status mysqld    # or mariadb
df -h                      # is the disk full?
free -h                    # out of memory?

Restart what's stopped:

systemctl restart httpd

A full disk is a very common cause. Free up space (old logs, backups), then restart services.

4. Reboot

If nothing responds, reboot the server:

  • from the client area: Services > My Services, open your server, and use Reboot if it's available
  • or open a ticket and Romeo will reboot it for you

After the reboot, give it a few minutes before testing again.

5. Still down after a reboot?

Open a ticket with:

  • your server's IP address
  • when it stopped working
  • anything you changed just before (updates, firewall rules, new software)

Romeo can check the server from the console and the data centre side, even when you can't get in.

Managed Server customers: you don't need to do any of this. Just message Romeo on WhatsApp or open a ticket right away, and we'll take care of it.

Was this answer helpful?

Related articles

Still stuck? Romeo's got you.
Our support team replies around the clock, real humans who know your server.