Databáze řešení

My server is unreachable (network troubleshooting) View PDF

  • network, unreachable, troubleshooting, connectivity
  • 0

Overview

When a Pod stops responding to ping, SSH or HTTP, you need to work out whether the problem is on the Pod, the network, or your own connection. This article walks through a logical diagnosis.

Before you begin

  • Your Pod's IP address.
  • Access to the ALYPOD Console and, ideally, a second network (such as mobile data) to rule out local issues.

Steps

  1. Check the Pod status and console. In the ALYPOD Console, confirm the Pod shows as running and open the VNC console. If you can log in there, the Pod is up and the issue is network-related.
  2. Rule out your own connection. Try from a different network, or use an external check:

bash ping -c 4 <pod-ip> traceroute <pod-ip>

  1. Check the firewall from inside the Pod. Via the VNC console:

bash sudo ufw status sudo iptables -L -n sudo firewall-cmd --list-all

An overly strict rule or a self-lockout is a common cause.

  1. Confirm the services are running:

bash systemctl status ssh nginx ss -tulpn

  1. Check the network configuration inside the Pod:

bash ip addr ip route cat /etc/resolv.conf

If the Pod got no address or the default route is missing, restart networking:

```bash sudo systemctl restart networking

or, on NetworkManager systems:

sudo nmcli networking off && sudo nmcli networking on ```

  1. Look for a DDoS or abuse suspension. If traffic suddenly spiked, the Pod may have been filtered. Check for any notification from ALYPOD.
  2. Reboot the Pod from the ALYPOD Console if all else fails — the console usually survives when the network does not.

Troubleshooting

  • Problem: Ping fails but HTTP works. Solution: ICMP is likely filtered; that is not a fault.
  • Problem: The Pod is up in the console but has no network at all. Solution: Compare the interface config with a working state, correct it via VNC, and restart networking.
  • Problem: Everything looks fine but remote access still fails. Solution: Contact ALYPOD support with your Pod ID and traceroute output.

Related articles

  • [I cannot connect to my Pod via SSH]
  • [The server will not boot]
  • [DNS changes are not propagating]

Byla tato odpověď nápomocná?

<< Zpět