No internet after setting up Zaksha
If a device can't open any site after you set up Zaksha, the address the device uses to reach Zaksha is usually wrong or can't be reached. Check these in order.
On an Android phone set up without the app
If you used Private DNS instead of the Zaksha app, Android says "Private DNS server cannot be accessed" when the Private DNS address is wrong.
- Open Settings and search for "Private DNS".
- Copy the Private DNS hostname again from the device's setup page in your app, and paste it in place of the old one. A missing letter or an extra space is enough to stop it.
- If you need the internet back right now, set Private DNS to Automatic. The device shows Not filtering until you fix the address.
On a Windows PC set up by hand
- Check the URL against the DNS-over-HTTPS URL on the PC's setup page. The steps are in Set it by hand.
- To get online straight away, set DNS back to automatic. Filtering is off until you put the right address back.
On hotel, airport or train Wi-Fi
Wi-Fi that shows a login page before the internet works can fail with filtering on. See Hotel and airport Wi-Fi.
Only some sites fail
If most sites open and a few don't, Zaksha is working and those sites are blocked. See Which rule wins, or allow one in Site blocked by mistake.
Still stuck? Ask a question. A person at Zaksha reads every one.