A single-site failure can involve its address, account, service policy or a temporary problem. Reinstalling the VPN is unlikely to be the best first observation.
Work through the checks
- Read and save the exact error, including any error code. Avoid including account tokens or private query parameters.
- Check the full website address against a known bookmark or the organization’s confirmed address.
- Try one unrelated website while leaving the VPN state unchanged. Establish whether the failure is actually limited to one service.
- If appropriate for the task, compare the affected site with the VPN disconnected. Keep the account, page and network unchanged.
- Read the affected service’s official help for that error. Follow its rules rather than cycling through locations to evade an account or access restriction.
Read the result
| What you observe | Next step |
|---|---|
| Only one site fails in both states | Check that service’s help and account status. |
| It fails only while VPN is connected | Record the service’s error and VPN state. |
| Several unrelated sites fail too | Return to broader connection troubleshooting. |
Make the comparison useful
A streaming page saying that a title is unavailable is different from a browser saying it cannot find a domain. Use the exact wording to choose the next investigation instead of treating both as a generic VPN error.
Before changing more settings
Stop if a site asks you to disable browser protection or enter credentials on an unfamiliar domain. Connecting through a VPN does not make an unexpected destination trustworthy.
Use the support-request template if you need to send the result. The reference guidance explains the underlying network or platform behavior; exact Zenshield controls depend on the installed app version.
