Setup ALGO to run on a small server on DO.
Obviously Chrome is out of use because of WebRTC leaks and can’t be shut off, but testing through Safari and Firefox I think DNS is still leaking.
My expectation is that if the server I setup on DO through ALGO is say 220.127.116.11 and my local machines IP is 18.104.22.168 that all traffic would route through the ALGO VPN and no other IP addresses would show up. However, using Firefox and Safari I still see a bunch of DNS show up with addresses like.
22.214.171.124 (which traces to Google) 126.96.36.199 (which traces to Google) 188.8.131.52 (which traces to Google) 184.108.40.206 (which traces to Google) 220.127.116.11 (which traces to Google) 18.104.22.168 (which traces to Google)
If a VPN is working properly the only address that should show up is the one running on ALGO server at the 22.214.171.124 address.
Could this be a plugin that’s leaking? I have HTTPS Everywhere running and a few others? What else could it be?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Click below to sign up and get $200 of credit to try our products over 60 days!