Troubleshooting

I can ping 1.1.1.1 but DNS lookups fail

This likely means that the operating system requires a DNS entry in the WireGuard configuration. Add a working DNS server to the WireGuard configuration under the Interface heading, e.g. DNS = 9.9.9.9 or DNS = 1.1.1.1, 2606:4700:4700::1111. Then, restart the tunnel and see if this works.

I can only connect to google.com or some websites fail to load:

Usually if only certain services such as Google are accessible from your Hoppy tunnel, this indicates an MTU issue. This is because Google always uses an MTU of 1280 for maximum compatibility. In the client configuration, add MTU = 1280 under the Interface heading. Fine-tune the MTU based on your network topology.

I can't connect to my LAN devices:

Android Client (Go backend)

If you cannot access clients within your local network (e.g. 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16), edit your tunnel configuration inside the Android app, and select "Exclude private IPs".

Linux Client

Generally, Linux allows access to the local subnet, but may not be aware of additional private networks.

First, click "More..." under "Download Client Configuration" in the tunnel's Manage page, and download the .conf configuration under "Exclude Private Networks and Endpoints". Replace your original .conf file with the newly downloaded one. Note this disables Linux fwmark routing.

macOS/iOS Client

macOS or iOS will allow access to the local network, but may not be aware of additional private networks.

First, click "More..." under "Download Client Configuration" in the tunnel's Manage page, and download the .zip configuration under "Exclude Private Networks and Endpoints". Remove your original configuration from your client, and import the newly downloaded one.

The connection stops working when roaming to another network:

Make sure that you are using a raw IPv4 endpoint. If you are you are using the dual IPv4/IPv6 endpoint, sometimes the DNS lookup can fail as well, so use either the raw IPv4 or raw IPv6 endpoint.