Hiddify Connected but No Internet: Websites Do Not Open

If Hiddify says “connected” but the browser cannot open websites, apps keep loading, or only some sites work, the problem occurs after the connection is established. The key is to distinguish the base network, client routing, subscription node, DNS/TLS, and server path.

Issue #1964 in the official repository records a case where system proxy worked but VPN mode timed out, along with DNS and TUN timeout logs. It is one user report and should not be treated as proof that one MTU or DNS value applies to everyone.

Symptoms

• The connection button is green, but no website opens.
• IP information or speed appears briefly, then requests time out.
• IP addresses work, but domain names do not.
• System proxy works but VPN/TUN does not, or the reverse.
• Small pages open, but large pages, images, or videos never finish loading.
• Only the current device fails, while the same subscription works on a phone or another computer.

Two-minute diagnosis

1. Disconnect Hiddify and open a site that normally works directly. If it still fails, restore the local network first.
2. Reconnect, test latency on the Proxy/Nodes page, and manually select a node that returns a clear result. The official usage guide describes the proxy list, latency test, and manual selection.
3. Switch once between Wi-Fi and a mobile hotspot. If changing the network restores access, the problem is closer to the local network, DNS, or an access-network restriction.
4. Compare system proxy and TUN/VPN once. If system proxy works and TUN fails, go to TUN mode troubleshooting.
5. Test the same subscription on another device. If that device also fails, check the subscription and server first.

Troubleshoot by layer

Client: start with the mode and conflicts

• Quit Hiddify completely, then start it normally from the application entry point so a stale process does not retain an old proxy state.
• Pause other VPNs, proxies, accelerators, ad filters, or virtual-adapter software and test with only Hiddify running.
• Confirm that the selected connection mode matches the requirement. System proxy mainly covers apps that respect operating-system proxy settings, while TUN/VPN handles a broader range of system traffic.
• Restore advanced routing, DNS, and TUN implementation options to their defaults before retesting so several custom settings do not overlap.
• Compare the installed version with the official Releases. If the problem began immediately after an upgrade, record the versions before and after and check the official Issues rather than installing an old package from an unknown source.

Subscription: a connected state does not prove the node works

• Refresh the subscription and confirm that the account has not expired and its traffic quota is not exhausted.
• Test multiple nodes in the proxy list. If only one fails, it is a node problem rather than a problem with the entire client.
• If every node in one subscription fails while another subscription works, contact the first provider.
• If the refresh itself reports an error, handle Subscription update failed first.

The official usage guide says the app can test proxy latency and select a node manually. A latency result proves only that the test request received a response; verify full traffic with an actual website or app.

DNS/TLS: narrow the scope using the symptom

• If an IP address works but a domain does not, and the log contains dns, exchange failed, or a resolution timeout, investigate DNS first.
• Restore Hiddify’s default DNS before testing any settings explicitly provided by the provider. Do not enter several DNS addresses copied from the internet at once.
• Correct the system time. An incorrect date can cause certificate errors across HTTPS sites.
• Retesting on another network helps distinguish device settings from DNS/TLS restrictions on the network path.
• Do not “fix” access by disabling certificate validation, installing an unfamiliar root certificate, or changing HTTPS to HTTP.

Issue #1976 in the official repository records one combination of a specific version, mobile network, and DNS errors. The same discussion also shows that one DNS change helped some users and not others, so rely on your own controlled comparison.

Server: check the node and upstream path

• If the same node fails across multiple networks and devices, the provider normally needs to inspect the server.
• Ask the provider to confirm the node port, domain certificate, protocol parameters, upstream network, traffic quota, and concurrency limit.
• If one region or carrier fails while other networks work, provide the time, network type, and redacted logs so the provider can investigate the route.

Verification

After the fix, do more than check the green button:

1. Open HTTPS pages on two different domains.
2. Complete a real request in a commonly used app instead of relying only on a latency number.
3. Disconnect and reconnect three times and confirm that access returns each time.
4. Record Wi-Fi and mobile-hotspot results separately to determine whether the issue belongs to one access network.
5. Quit Hiddify and confirm that direct system networking works without a stale proxy.

If access works but speed remains unstable, continue with Hiddify is slow or frequently disconnects.

When to contact the provider

Contact the subscription provider if the same subscription carries no traffic on multiple devices and networks, or every node times out. Redact the token, UUID, and subscription address from any account-status screenshot.

If the same node works in other clients and the failure is limited to one Hiddify version, operating system, or connection mode, search the official Issues and submit the shortest reproduction: system and app versions, system proxy/TUN mode, network type, time of occurrence, and redacted logs.