#26350: MacOS Tor Browser cannot bind to port --------------------------------------+-------------------------- Reporter: phoul | Owner: tbb-team Type: defect | Status: new Priority: Medium | Milestone: Component: Applications/Tor Browser | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------------------+-------------------------- Changes (by mcs):
* cc: nickm (added) Comment: Replying to [comment:3 cypherpunks]: > Maybe `sudo lsof -n -P | grep LISTEN | grep 9150` yet? The above command is a good thing to try, although if another process was listening on TCP port 9150 I would expect to see an "Address already in use" error (EADDRINUSE). The error message that is being logged is from EADDRNOTAVAIL, which is a strange error to get. My guess is something is wrong with the networking stack at the macOS level. The error could also be caused by a programming error inside tor such as not properly initializing the sockaddr passed to bind(), but if that were the case we would have a lot more reports like this one. Cc Nick in case he has seen this problem before. Colin — We could ask this user to try using different TCP ports for tor, although I am not convinced it will help. To do that they would need to add lines like the following to the prefs.js file within their Tor Browser profile (under ~/Library/Application Support/TorBrowser- Data/Browser/*.default): user_pref("network.proxy.socks_port", 9160); user_pref("extensions.torlauncher.control_port", 9161); -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26350#comment:4> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs