Open alepartenza opened 7 years ago
Thanks @alepartenza for reporting this.
can you please clarify about your setup? I expect it it in relation to GlobaLeaks right?
Are you using a custom setup of tor2web or a public setup?
Anyhow it is far common (if you do not have a stable connection, or just in relation to how Tor workds) that the connections between globaleaks and tor2web are subject to failures. To overcome this issue, whenever you do not need location anonymity for the globaleaks server you could use the dummy proxy configuration of tor2web.
e.g. with ``'#dummyproxy = http://127.0.0.1:8082``` you could point tor2web directly to a GlobaLeaks instance on IP:PORT.
We run into this at Publeaks as well quite frequently, Tor is fine, it seems the Tor2Web process comes into a weird loop and just completely stops and give an 500 error. This shouldn't be the case, I guess from a UX point of view, Tor2Web should keep trying in a separate thread for that specific user that is trying to go to an onion link in our case.
Thoughts?
How do I solve this problem? It often happens