Why can I acces 1337 through chrome, but not through firefox?
Why can I acces 1337 through chrome, but not through firefox?
I found out today that I can change my dns to acces 1337.to again. My ISP was blocking it. However, it works on chrome, but not on firefox. Why doesn't it work on firefox?
-
Chrome has DNS-over-HTTPS enabled by default. Firefox, however, enables that by default in certain regions only.
Cloudflare has a comprehensive guide on how to enable it in various browsers.
P.S. If you dun wanna use Cloudflare as the resolver, quad9 can be an (maybe better) option.
-
Followup question, prowlarr seems to have the same issue. Do you know if and how I can setup prowlarr to use couldflare dns?
-
Prowlarr works fine but you need yomething inbetween to solve the CF captcha.
https://github.com/FlareSolverr/FlareSolverrEdit: Using both in a docker container
-
Thanks!
-
That seems as a weird decision by Firefox considering their relatively privacy focused image.
-
1.https does not mean more private. for regular browsing it does not matter 2. it is always good to have 2 browsers or use containers to seperate personal and regular stuff
-
Maybe a little off-topic, but I found this useful to explain difference between DoT and DoH: https://www.cloudflare.com/learning/dns/dns-over-tls/
Turns out I am using DoT instead of DoH. Both are encrypted, but DoT is distinguishable from HTTPS traffic.
-
-
Go into the settings and enable DNS over HTTPS. That should solve the problem, and honestly you should have it enabled anyway for privacy.
-
- adblocker or any other blocker
- DNS on browser
-
If you're accessing 1337.to without a VPN, I don't think you're going to be having issues with your internet for much longer, lol
-
Not everyone lives in the US
-
US or not accessing the site itself is in no way illegal.
-
-