#25390 closed defect (worksforme)
Tor browser fails to start when configured to use an external tor instance
| Reported by: | Zedfour | Owned by: | tbb-team |
|---|---|---|---|
| Priority: | Medium | Milestone: | |
| Component: | Applications/Tor Browser | Version: | |
| Severity: | Normal | Keywords: | |
| Cc: | Actual Points: | ||
| Parent ID: | Points: | ||
| Reviewer: | Sponsor: |
Description
I have configured Tor browser to use an independent Tor instance in my local network by changing the SOCKS5 proxy. Problem is, if there is such instance configured in Tor browser's Network settings, the startup will fail next time, since the included instance can not start listening on an interface that does not exist on the local machine.
Also, if I want to do the same with an instance running on the local machine, the included instance will also fail to start due to port conflict. Is there a correct way to do this?
Child Tickets
Change History (3)
comment:1 Changed 16 months ago by
| Summary: | Tor browser fails when external tor instance is configured → Tor browser fails to start when configured to use an external tor instance |
|---|
comment:2 Changed 16 months ago by
| Component: | Core Tor/Tor → Applications/Tor Browser |
|---|---|
| Owner: | set to tbb-team |
| Resolution: | → worksforme |
| Status: | new → closed |
comment:3 Changed 16 months ago by
I couldn't find anything that could be called "Tor Launcher documentation".
But I found a bug report that had the required info, namely this:
Note: See
TracTickets for help on using
tickets.
Yes, there are environmental variables that can be used to control Tor Launcher.
Please see the Tor Launcher documentation for details.