This is difficult and may not work for you.
To learn why this is difficult, please press on Expand on the right.
Tor Browser, which is developed by upstream, The Tor Project (TPO), an independent entity has hard configured to use Tor as a proxy.
* Upstream does not support user using Tor Browser with an additional extra proxy at the end of the chain, i.e.: user → Tor → proxy → destination
* Upstream does also not support using Tor Browser with a proxy other than Tor, i.e.: user → custom proxy → destination. This may or may not currently be possible but upstream does not provide documentation on how to do this.
* Upstream does also not support using Tor Browser with a VPN instead of Tor, i.e. user → VPN → destination.
* Upstream does also not support using Tor Browser with a VPN in addition before Tor, i.e. user → Tor → VPN → destination.
That makes sense from TPO's perspective as a project that maintains a browser that should always connect using the Tor network. Due to that perspective, proxy settings have been removed from Tor Browser to avoid user confusion and accidental misconfiguration. Little attention is spend on custom proxy settings. That, from TPO's perspective is assumed to only make sense for users using a Tor transparent proxy and that are already running Tor on a different computer in their LAN. Only a minority of users is using such configurations.
Because of this organisational and technical background, the highly specialized use case of configuring Tor Browser running inside {{project_name_workstation_long}} to use an additional proxy (user -> Tor -> proxy -> destination) is difficult to accomplish.
To learn more about this organisational and technical background see also {{kicksecure_wiki
|wikipage=Linux_User_Experience_versus_Commercial_Operating_Systems
|text=Linux User Experience versus Commercial Operating Systems
}}
{{Community_Support|scope=chapter}}
}}