Network, DNS and firewall checks
Find whether the problem is an address, route, DNS, port or firewall rule.
Common symptoms
No network, DNS failure, name resolution, packet loss, unreachable, port blocked, firewall, IPv4, IPv6
What to check
- Check server status and maintenance. Through Console, inspect the guest interface, assigned addresses and default route, and compare them with server details.
- Compare a connection to a known reachable IP with a hostname lookup. If IP access works but names fail, check the guest's DNS settings; if both fail, investigate the route and address family.
- Review guest and panel firewall rules for the affected protocol and port, plus whether the service is listening. Make a specific reversible rule change while preserving Console access; do not blindly disable all firewalls.
Common questions
IP access works, but hostnames fail. Is the server offline?
This points toward DNS rather than a complete network outage. Check the resolver configuration and the hostname's records, and compare IPv4 and IPv6 results where applicable.
Should I disable the firewall to fix a blocked port?
First confirm the service is listening and identify the exact guest or panel rule affecting the port. Adjust the required rule deliberately and keep a recovery path instead of removing all protection.
Open the relevant page
Before contacting support
Include the server name, source and destination address families, affected port, time with timezone and sanitized route, DNS or connection error. Remove credentials and unrelated private data.
Keep secrets out of support requests · Remove passwords, private keys, access tokens, TOTP codes, backup codes and full payment details from screenshots and logs. Share the server or order name, time with timezone and exact sanitized error.
This opens an editable ticket draft. Nothing is sent automatically.