Allow users to configure outbound proxy about browserbox HOT 2 CLOSED

This is an excellent idea. We especially like your API proposal.

Definitely I’ll add this to the list.

Funnily enough, there may be a workaround that you can do right now without modifying any code.

This workaround involves where we get the proxy address from. I believe we retrieve it directly from the torrc file. There’s a bash function somewhere that parses that I think.

I may be mistaken, but what I’m thinking and hoping is that it’s simply possible to edit the torrc file in its default location and use that to specify the custom proxy.

So use —ontor option with setup_bbpro then modify torrc to point to your desired proxy. Then run bbpro.

For docker, You could run these from within a bash shell in the running container.

I’m not sure if this will work, but I think it or something like it likely will, and could function well as a temporary workaround until we actually add this.

Please note, we are quite busy right now with customizations and deployments for customers, and we do not have the resources to commit to a new sprint or even adding this right now outside of a dedicated support tier. If This is critical for your case, Please contact us at [email protected] and we can likely figure something out. We have a number of paid support tiers you can subscribe to.

Failing that, we will definitely eventually get to this, but just not sure when right now because we are super busy at this time.

finally, I really like your idea @mindcrunch4u. Thank you very much for sharing it!

from browserbox.

Closing to track in main list

from browserbox.