Skip to main content
Check the IPv6 address, route and DNS separately. Open the VNC console before changing network settings.

​
1. Compare the address with the control panel

Open the VPS’s Network tab. On Linux, run:
The interface should be UP. Its global IPv6 address must come from your assigned allocation and use the /48 interface prefix. A fe80:: address alone is only link-local and cannot provide Internet access. An address marked tentative is still being checked; dadfailed indicates a duplicate-address problem. Use IPv6 configuration if the assigned address is missing. Do not choose addresses outside your VPS’s allocation.

​
2. Check the gateway and route

Look for a default route through the exact gateway listed in the panel. Replace the example below with that gateway:
If the route is missing or uses the wrong gateway, correct the saved network configuration. A failed ping alone is not conclusive because ICMP can be filtered.

​
3. Test external connectivity and DNS

​
4. Check the application

An application listening only on IPv4 will not necessarily accept IPv6. Listening on ::1 allows local access only. Listening on :: can accept connections on all IPv6 addresses, so check firewall restrictions before changing it. Do not disable the whole firewall to test one port.

​
5. Check the settings survive a reboot

Once IPv6 works, save the configuration in the network manager used by your OS. Test IPv4 and IPv6 again after a planned restart.

​
Send useful details to support

Email support@edbb.com with the VPS IP, time and timezone, failing destination and the address/route results above. Include whether IPv4 still works and whether the problem affects incoming or outgoing connections. Remove passwords and other secrets from logs.