VPN troubleshooting

Start with a connection check while the issue is happening. Your support engineer may ask you to repeat it with the VPN disconnected and compare the results.

Start here

The guided check collects your public IP, ISP, browser, optional DNS result, selected TCP ports, and VPN state into one copyable summary.

Start guided connectivity check

Have the affected public hostname ready if support gave you one. The port checker tests TCP from our server; WireGuard tunnels normally use UDP, so a TCP result cannot confirm whether the VPN tunnel port is reachable.

A DNS record lookup checks a public hostname. The optional Client DNS setting in a WireGuard config controls which DNS server the client uses; it is a separate configuration choice.

Open a specific tool

Public IP

See the address and ISP visible to websites while your VPN is connected.

Open IP lookup

DNS

Check public DNS records for the service you are trying to reach.

Open DNS lookup

TCP ports

Probe a public host from our server. This does not test your device or a UDP VPN port.

Open port checker

Browser

View browser, operating system, and device details for a support call.

Open browser details

WireGuard configuration

Generate a sample config with optional client DNS and tunnel MTU. Use values supplied by your VPN provider; never share private keys.

Open WireGuard tool

Subnet

Check whether an IP address belongs to the expected network range.

Open subnet calculator

Website certificate

Inspect a public website certificate if HTTPS is part of the issue.

Open SSL checker