New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Journalist UI could not be reached via v3 URL 1.0.0~rc1 #4738
Comments
Confirmed. |
The problem seems to be that the I think the cause is that the |
Nope, It looks like we might want to either populate |
This is an existing bug iirc - FWIW I couldn't reproduce on a fresh VM install, but that's probably because the network hook did run when |
Moving the hook to a task makes most sense to me. |
Makes sense to me. That's a simple approach, and the only downside is that the hook will run (and bounce tor) every time
That'd indeed be slightly cleaner, requiring the network hook to bounce only if changes were detected, but it doesn't seem worth the effort in order to provide a stable experience to Admins. |
OK. On it. Thanks! |
There's an extra directive to be added to |
Description
I could not reach the journalist UI via v3 onion address.
Steps to Reproduce
1.0.0~rc1
to bothv2
andv3
enabled system../securedrop-admin tailsconfig
on the admin workstationNote: The source
v3
onion address is working fine, and if I type in the oldv2
onion address manually, it is currently working.Expected Behavior
The journalist UI should come up.
Actual Behavior
The Tor Browser can not find the onion address.
The text was updated successfully, but these errors were encountered: