Firefox notices an anonymous proxy while connecting to certain sites and displays this warning.
Firefox notices an anonymous proxy while connecting to certain sites and displays this warning.
Hey there. Not sure if this forum is the best spot for browser questions... But I saw this issue after Firefox's latest update. I've already tried a few fixes: turning off Query OCSP, disabling HTTPS-only mode, blocking DNS over HTTPS, clearing cookies and site data, and clearing the proxy. It worked for about 10 seconds before it started again. It seems to happen only with Firefox, not Chrome. Anyone else experienced this problem?
It might be the default DNS configuration. Consider updating them via https://support.mozilla.org/en-US/kb/how...s-settings. I attempted to open the site from your screenshot, but uBlock Origin was blocking it. Unclear why.
The issue stems from the site you're attempting to access, not your browser. They believe you're using a proxy and are being blocked.
They should disable the VPN or proxy service they're currently using.
It seems Chrome has a problem, but the message indicates your connection isn't secure. My dad's laptop is experiencing the same issue too. I reached out to my internet service provider to investigate... it looks like the issue might be with my router.
The message indicates a privacy issue with your connection. It suggests the site isn't using HTTPS or has an invalid certificate, which could stem from server misconfiguration or a compromised proxy. Your ISP likely can't resolve this, and it's unlikely to be an active attack unless someone physically accessed your network.
The technician arrived after about ten minutes of troubleshooting the router and resetting it. He explained that the DNS settings were likely incorrect from Chrome. Everything is now functioning properly. This seems unusual because it worked fine just a week prior.
Tech professional may be speculating. I store DNS locally and haven’t encountered this problem. A Firefox setting also allows custom caching duration, which still resolves the issue. Cloudflare DNS is currently the fastest available, marginally quicker than alternatives. Yet what’s even faster than that? A local cache on your device storage—whether magnetic or solid state. The next viable choice is a DNS cache within your network. Why? Every 175 seconds, web servers prompt connected devices to refresh their IP addresses, even if they remain unchanged, causing numerous devices and active connections to repeatedly reconnect. This constant looping wastes significant network resources. A practical solution is employing a local DNS service. I use unbound, which stores results; occasionally I update the cache infrequently (using an outdated file for testing) and still avoid problems. It operates in a virtual machine with saved state, preventing the system from restarting and ensuring IP updates aren’t refreshed within a reasonable timeframe. This suggests the issue likely isn’t DNS-related, but exploring further could clarify connection challenges. In Firefox—even on mobile—developer mode or an updated version might require adjusting network.dnsCacheExpiration in preferences:config. I set it to a high value (above 1000), though I rarely visit many sites and wouldn’t expect that many unique domains in a year.