• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

PatchMyPC website and firefox

Started by ferreirah, May 20, 2022, 01:59:25 PM

Previous topic - Next topic

ferreirah

Hi,

Your website doesn't work with firefox.

H.F.

Justin Chalfant (Patch My PC)

Could you provide some more details about what you are seeing? Maybe some screenshots or a video?

ferreirah

I tried it also with my vpn off and got the same result. I am using cloudfare as the secure dns service in firefox.

H.F.

Justin Chalfant (Patch My PC)


ferreirah

Hi,

I managed to figure out the solution. If you enable "dns over https" in network settings in firefox, then I can't access your site. I tried "Next" as well as "CloudFare" and they both failed. If you disable this option, then Firefox works perfectly. These 2 are secure dns providers used by Firefox. I tried it with and without my vpn and I can confirm that it does work if you leave this option off. It's in the network settings of Firefox. I can provide you with a screenshot if you need it?

H.F.

Jake Shackelford (Patch My PC)

If you'd like by all means, we can dig in and see if we can reproduce.

ferreirah

Hi,

Windows 11 64 bit with all the updates, Latest Firefox 64 bit for Windows.

Go to "Settings", "General Settings", "Network Settings".

Scroll right to the bottom.

Tick "DNS over HTTPS".

You can choose either "CloudFare" or "Next".

Click OK to Apply.

Close and open Firefox again.

I am attaching screenshots.

I hope it helps.

Please let me know if you could reproduce.

H.F.


Andrew Jimenez (Patch My PC)

Interesting, I was unable to replicate this issue.

ferreirah

May be there's an issue with their South African servers? I managed to reproduce it again tonight. I'm referring to the CloudFare and Next servers.

Any way, I woudn't worry about it too much. There is a workaround.

Thanks for looking into it.

H.F.

Andrew Jimenez (Patch My PC)

Possibly, it is odd because we actually use cloudflare for DNS I'm pretty sure, so I believe it may be a localized issue. I'll mark this as solved for now.