[tor-bugs] #33279 [Applications/Tor Browser]: Tor Browser cannot bind SOCKS port 9050: How to change browser settings? (not torrc)

[Tor Bug Tracker & Wiki]

#33279: Tor Browser cannot bind SOCKS port 9050: How to change browser settings?
(not torrc)
--------------------------------------+-----------------------------------
 Reporter:  psisis                    |          Owner:  tbb-team
     Type:  defect                    |         Status:  needs_information
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:                            |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+-----------------------------------

Comment (by psisis):

 Replying to [comment:6 mcs]:
 > Replying to [comment:5 psisis]:
 > > And besides the problem not making much sense, is there a possible way
 to change Tor Browser settings from files or sqlite? It seems to behave
 somewhat differently from standard FF.
 >
 > It is difficult to understand your setup, but the default SOCKS port
 used by Tor Browser when it starts tor is 9150, not 9050. That is
 configured by the browser via args passed when starting tor.exe, e.g.,
 `__SocksPort 127.0.0.1:9150 IPv6Traffic PreferIPv6
 KeepAliveIsolateSOCKSAuth`. It will not normally be stored in `torrc`.
 >
 > You should not need to add any `SocksPort` lines to your `torrc` file.
 In the absence of any other unusual configuration, the SOCKS port is
 derived from the `network.proxy.socks_port` preference value. You can
 change it by editing `prefs.js` within the Tor Browser profile.


 I don’t know why you guys give me such a hard time. I outlined the problem
 clearly, posted my tor.exe output log, and said what I’ve tried. You keep
 assuming the real issue is deep within my system. A fresh bundle will not
 start either, and it’s impossible Tor is already running, since it’s on a
 drive not mounted at startup.

 I put `user_pref("network.proxy.socks_port", 443);` in my `prefs.js`. And
 Tor starts now, thank you very much.

 Fwiw, Resource Mon says tor.exe is also using port `9151` but that was
 allowed and never restricted. And inspecting the packets, tor is having
 TCP/socks traffic from ports `~5470-5700` (tor was completely dead before
 changing prefs.js)


 For clarification, Tor worked literally for years until two days ago. Two
 days ago I removed my router and hooked up to WAN, nothing else happened,
 I promise

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33279#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online