[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:  High                      |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Critical                  |     Resolution:
 Keywords:                            |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+-----------------------------------
Description changed by pospeselr:

Old description:

> I’m having a frustrating problem. I have no router right now, and am at
> the mercy of the ISP gateway, and they don’t give permission to port
> 9050. Starting Tor Browser, I instantly get closed unexpectedly/error,
> with no log message whatsoever. But running tor.exe manually I found the
> problem. (Permission denied [WSACCESS])
>
> I changed torrc SOCKS port to 443 and it works, tor.exe is starting. BUT,
> the actual browser will not start, it gives the same unexpected error.
> Tor service actually works though, if I enter the local proxy manually
> into my standard browser it reaches onion links. But that is not really a
> solution. I have tried looking through prefs.js and sqlite files but
> could not find any option for either proxy settings or ‘9050’. Can I
> change the proxy port manually without starting TorBrowser/FF?
>
> (A completely fresh bundle will not start either)

New description:

 I’m having a frustrating problem. I have no router right now, and am at
 the mercy of the ISP gateway, and they don’t give permission to port 9050.
 Starting Tor Browser, I instantly get closed unexpectedly/error, with no
 log message whatsoever. But running tor.exe manually I found the problem.
 (Permission denied [WSAEACCES])

 I changed torrc SOCKS port to 443 and it works, tor.exe is starting. BUT,
 the actual browser will not start, it gives the same unexpected error. Tor
 service actually works though, if I enter the local proxy manually into my
 standard browser it reaches onion links. But that is not really a
 solution. I have tried looking through prefs.js and sqlite files but could
 not find any option for either proxy settings or ‘9050’. Can I change the
 proxy port manually without starting TorBrowser/FF?

 (A completely fresh bundle will not start either)

--

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