IPv6-only servers
Check client connectivity before connecting to a server without public IPv4.
Common symptoms
IPv6 only, no IPv4, Network is unreachable, IPv6 timeout, VPN, jump host, NAT64
What to check
- Check the order and server's IPv4/IPv6 assignments. An IPv6-only server has no public IPv4 address; a client with only IPv4 cannot directly connect to its IPv6 address.
- Use a network, VPN or jump host with working IPv6 access. Copy the panel's SSH command; IPv6 address syntax differs between SSH, scp and browser URLs.
- If it still fails, use Console to check the guest interface, assigned IPv6 address, default route and firewall. Test IPv6 from the client too and check relevant maintenance notices.
Common questions
Can I connect from an IPv4-only home or office network?
Not directly to an IPv6-only address. Use working IPv6 access or an IPv6-capable VPN or jump host. The server does not automatically provide your computer with IPv6 connectivity or an IPv4 address.
Does an IPv6-only server automatically include NAT64?
Do not assume NAT64, an IPv4 proxy or IPv4-only destination access is included. Check the available service details and your chosen network arrangement before relying on IPv4-only services.
Open the relevant page
Before contacting support
Include the server name, sanitized connection error, time with timezone and whether the client has working IPv6. Remove all credentials and tokens from command output.
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.
Official reference documentation
This opens an editable ticket draft. Nothing is sent automatically.