bekh6ex / firefox-container-proxy

[Firefox extension] Assign a proxy to a Firefox container
https://addons.mozilla.org/en-US/firefox/addon/container-proxy/
BSD 2-Clause "Simplified" License
137 stars 14 forks source link

Strange request failure when using SOCKS5 proxy in recent versions of Firefox #42

Open koma-cute opened 3 years ago

koma-cute commented 3 years ago

I'm running Firefox 92 on Windows 21H1 (19043). I believe this issue started happening in the last few weeks, so could be a regression in Firefox 91 or 90. When using Container Proxy with a localhost SOCKS5 connection to a remote Shadowsocks server, pages will mysteriously not load with the following error about checking the system has the Personal Security Manager installed: firefox_2021-09-10_18-21-21 This usually disappears after clicking try again, but then XHRs and other resource requests will fail in a similarly mysterious way (left: with container tab proxy, right: without container tab proxy, using built in Firefox SOCKS5 proxy settings): firefox_2021-09-10_18-39-40 (the science requests are analytics blocked by uBlock and disabling the extension does not change the result)

mattberther commented 2 years ago

I was able to get around this by turning off "Enable DNS over HTTPS" in Settings | General | Network Settings.

bekh6ex commented 2 years ago

There is a default setting to always proxy DNS requests for Socks proxies and I see it becoming a problem several times. I'm currently making it configurable, don't want to make any promises, but I plan to finish it in the next days.

bekh6ex commented 2 years ago

Please, update to 0.1.21 and verify! Should be working, but honestly speaking I didn't really test it due to proxy setup dificulty, so anything's possible 😄 Due to that, feedback will be double-extra appreciated this time!

koma-cute commented 2 years ago

I'm not seeing any Firefox error pages anymore. Cloudflare is telling me on the https://www.cloudflare.com/ssl/encrypted-sni/ page that DoH is not in use in proxied container tabs. I don't know if that's an error on their end due to not detecting any requests from my proxied IP, or if they're being sent by the proxy in the clear. It's not a huge deal for my use case, but may be worth investigating.