Your VPS shows Online in Virtualizor, but you cannot SSH in, websites do not load, or the server itself cannot reach the internet. Almost always the cause is inside the VPS: a network configuration change, a firewall rule or DNS. This checklist finds it step by step.
Before you start
- Access to the Virtualizor panel and the VNC console, which works without networking.
- Your IP details from the panel: address, prefix, gateway. See VPS IP addresses.
Check the panel first
- Status is Online, not suspended. Suspension (billing, abuse, bandwidth overuse) cuts network access.
- Bandwidth usage is below the limit; some plans throttle or block after the limit.
- The Tasks log shows no failed reinstall or ongoing migration.
Test from your side
ping -c 4 203.0.113.10Then try another network (for example mobile data). If it works from elsewhere, your own IP may be blocked by the VPS firewall or Fail2Ban.
Log in through VNC and test inside
- Check interfaces and addresses:
ip -br addr. The main interface (ofteneth0orens3) should be UP with your IP. - Check the default route:
ip routeshould showdefault via GATEWAY. - Ping the gateway, then a public IP:
ping -c 3 1.1.1.1. - Test DNS:
ping -c 3 google.com. If IPs work but names do not, it is a DNS problem.
Fix common causes
| Symptom | Fix |
|---|---|
| Interface DOWN or no IP | Bring it up (ip link set eth0 up) and correct the config file, then netplan apply or nmcli con up |
| No default route | Add the gateway in Netplan (routes: - to: default via: GATEWAY) or NetworkManager |
| Public IPs work, names fail | Set nameservers, e.g. in /etc/systemd/resolved.conf or the Netplan nameservers section |
| Outgoing works, incoming blocked | Firewall rule: check ufw status or firewall-cmd --list-all |
| Only SSH fails | sshd stopped or moved to another port: systemctl status ssh |
Recently changed something?
- Interface renamed after a kernel or OS upgrade: update the name in the network configuration.
- Docker installed: Docker can change firewall rules; restart Docker or review its iptables chains.
- Firewall enabled without allowing SSH: disable it in VNC, add the SSH rule, enable again. See firewall rules.
When to contact support
If the configuration matches the panel, the interface is up, and even the gateway does not answer, the issue may be on the host or network side, such as a MAC address or IP routing problem. Open a ticket with the VPS IP, the output of ip addr and ip route, and the time the problem started. MdmHost customers can use a support ticket.