You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to set up OnionShare in a container, while having the Tor client in another container.
OnionShare starts, connects to the Tor service, and is seemingly ready to serve files, but my guess is that the registration of the ephemeral onion doesn't take this scenario into account. It's simply not possible to connect to the service via the reported onion host.
While I have found that creating /usr/share/anon-ws-base-files/workstation does make the web service listen on all interfaces, this does not help in this case.
Putting OnionShare into the same network namespace as the Tor client (while still being in a separate container) does make it work, but it'd be nice if OnionShare could use a Tor client that is "elsewhere".
The text was updated successfully, but these errors were encountered:
Thanks for a great tool.
I wanted to set up OnionShare in a container, while having the Tor client in another container.
OnionShare starts, connects to the Tor service, and is seemingly ready to serve files, but my guess is that the registration of the ephemeral onion doesn't take this scenario into account. It's simply not possible to connect to the service via the reported onion host.
While I have found that creating
/usr/share/anon-ws-base-files/workstation
does make the web service listen on all interfaces, this does not help in this case.Putting OnionShare into the same network namespace as the Tor client (while still being in a separate container) does make it work, but it'd be nice if OnionShare could use a Tor client that is "elsewhere".
The text was updated successfully, but these errors were encountered: