Web Protection uses Android's VPN facility to handle DNS requests. It is a DNS-only connection: normal web traffic is not routed through a location-changing VPN.
Another VPN is already active
Android permits one active VPN per user profile. A VPN app, firewall or ad blocker using that facility can conflict with Web Protection. Connecting another VPN may disconnect Gridinsoft, and starting Gridinsoft may require switching away from the other connection.
- Check Android's VPN settings and identify the currently active connection.
- If you want to use Web Protection, disconnect the other VPN through its app or Android settings.
- Return to Web Protection, start it, and verify Protection is ON.
On a work-managed phone, ask your administrator before changing a required VPN. If you need that VPN to remain active, these two connections cannot be used together in the same profile.
A custom Private DNS provider is selected
A manually specified Android Private DNS hostname prevents Web Protection from starting. Search Android Settings for Private DNS. If you choose to use Gridinsoft, change the custom provider setting to Automatic or Off, then retry protection. Android menus differ between manufacturers. Gridinsoft's own DNS connection still uses HTTPS.
A browser uses its own Secure DNS
Some browsers and apps send DNS directly to a provider chosen in their own settings. Those requests can bypass the system DNS route. Check the affected browser's Secure DNS or DNS provider setting; turn off its custom DNS override if you want that browser to use the system route.
Reload or restart the affected app after changing settings. Previously cached addresses and existing connections can remain usable for a while. Do not visit a known dangerous site to test coverage.