
Server Not Found Error Occurs Frequently
I have an issue where I will frequently get the error pictured on random sites. This started happening a few years ago at my previous home with my old computer. It got so annoying that I had to switch to Brave browser for a while. I recently moved to a new residence, I have a new computer, and a different ISP and equipment, so I thought I would give Firefox a try again. To my shock, the issue still occurs exactly the same way at the same rate. I would say it is as frequent as 1 in 5 sites that I visit. If I hit the Try Again button 5 or so times, the site will load. The only thing I can think of that is common to the old computer and the new one is my Firefox account. Could there be something in my settings causing this to happen? I remember that I even tried Librewolf before switching to Brave but the issue occurred there as well. Any assistance or tips would be appreciated, I feel like I am going crazy at this point. xD
தீர்வு தேர்ந்தெடுக்கப்பட்டது
In Privacy & Security I switched DNS over HTTPS to Increased Protection and changed the provider from Cloudflare to NextDNS and the issue seems to have been resolved.
Read this answer in context 👍 0All Replies (5)
You don't need a Mozilla account to go to a site. Did you verify in PM that it's not a Addon caused issue?
Does the problem occur both with and without the VPN?
Any difference if you change your DNS over HTTPS setting (on/off, etc.): Configure DNS over HTTPS protection levels in Firefox?
I disabled all addons and changed the DNS over HTTPS but it still continued. When I connected to a vpn though it looked like it stopped. I'm not sure exactly what that means. I guess it is network related?
I'm still getting this error frequently. I don't want to have to use a vpn 100% of the time. Can anyone think of any reason why this would be different with vpn on vs off?
தீர்வு தேர்ந்தெடுக்கப்பட்டது
In Privacy & Security I switched DNS over HTTPS to Increased Protection and changed the provider from Cloudflare to NextDNS and the issue seems to have been resolved.