Opened 6 years ago
Last modified 5 months ago
#8336 new defect
TOR_SOCKS_HOST, TOR_SOCKS_PORT regression
Reported by: | proper | Owned by: | tbb-team |
---|---|---|---|
Priority: | High | Milestone: | |
Component: | Applications/Tor Browser | Version: | |
Severity: | Normal | Keywords: | tbb-rebase-regression, tbb-torbutton |
Cc: | proper, intrigeri | Actual Points: | |
Parent ID: | #10160 | Points: | |
Reviewer: | Sponsor: |
Description
TBB 2.3.25-2 not affected.
TBB 2.3.25-3 not tested (not available for download).
TBB 2.3.25-4 introduced this bug.
I am using /etc/environment on Debian Wheezy.
TOR_SOCKS_HOST="192.168.0.10" TOR_SOCKS_PORT="9100"
(I am using a patched startup script, which starts "./App/Firefox/firefox --profile Data/profile" instead of "./App/vidalia --datadir Data/Vidalia/ -style Cleanlooks".)
When Tor Browser starts, it automatically opens https://check.torproject.org/?lang=en-US&small=1&uptodate=1 as expected but says:
The proxy server is refusing connections Firefox is configured to use a proxy server that is refusing connections. Check the proxy settings to make sure that they are correct. Contact your network administrator to make sure the proxy server is working.
All other pages are working.
https://check.torproject.org/ can not be reached until Tor Browser is restarted. Before the browser gets restarted it always says "The proxy server is refusing connections" even when trying to reload or in new tabs.
After Tor Browser has been restarted, everything works.
Child Tickets
Change History (8)
comment:1 Changed 6 years ago by
Keywords: | tbb-rebase-regression added |
---|
comment:2 Changed 6 years ago by
I have a workaround. (The old trick.)
/home/user/tor-browser_en-US/Data/profile/user.js
user_pref("extensions.torbutton.use_privoxy", false); user_pref("extensions.torbutton.settings_method", "custom"); user_pref("extensions.torbutton.socks_host", "192.168.0.10"); user_pref("extensions.torbutton.socks_port", 9100); user_pref("network.proxy.socks", "192.168.0.10"); user_pref("network.proxy.socks_port", 9100); user_pref("extensions.torbutton.custom.socks_host", "192.168.0.10"); user_pref("extensions.torbutton.custom.socks_port", 9100);
It works.
But if you could fix this TOR_SOCKS_HOST, TOR_SOCKS_PORT regression, that would be awesome.
comment:3 Changed 6 years ago by
To be clear: is this ticket the explanation for all those other TBB users who are reporting "The proxy server is refusing connections" issues too?
I am unclear because the original ticket sure looks like somebody doing something nonstandard.
comment:4 Changed 6 years ago by
Most users that report this message are overwriting their old bundle. This keeps the old custom profile, with SOCKS Port 9050 set. -> fail.
comment:5 Changed 5 years ago by
Cc: | intrigeri added |
---|
comment:6 Changed 5 years ago by
Component: | TorBrowserButton → Tor Browser |
---|---|
Keywords: | tbb-torbutton added |
Owner: | changed from mikeperry to tbb-team |
comment:7 Changed 15 months ago by
Severity: | → Normal |
---|
Set all open tickets without a severity to "Normal"
comment:8 Changed 5 months ago by
Parent ID: | → #10160 |
---|
It's easy to test if this still happens, but i don't want to close my browser right now :)
This is technically an issue with HTTPS-Everywhere and Firefox's proxy behavior... Firefox 17 now caches proxy settings for some reason, and this fact in combination with HTTPS-Everywhere's tor test, followed by the SOCKS settings change causes check.tp.o to get stuck at the previous SOCKS settings until you restart.