Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upspecifically sys-whonix fails to establish circuit #3511
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Rerun whonixcheck on sys-whonix. Showing alright?
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
hyperfekt
Jan 31, 2018
It failed every time I reran whonixcheck or whonixsetup. However it seems fixed with a fresh install of the just released rc4. I guess we can close this.
hyperfekt
commented
Jan 31, 2018
•
|
It failed every time I reran whonixcheck or whonixsetup. However it seems fixed with a fresh install of the just released rc4. I guess we can close this. |
andrewdavidwong
added
the
C: Whonix
label
Feb 1, 2018
andrewdavidwong
added this to the Release 4.0 milestone
Feb 1, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Feb 1, 2018
Member
Closing this as "resolved." If you believe the issue is not yet resolved, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen this. Thank you.
|
Closing this as "resolved." If you believe the issue is not yet resolved, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen this. Thank you. |
hyperfekt commentedJan 31, 2018
•
edited
Edited 2 times
-
hyperfekt
edited Jan 31, 2018 (most recent)
-
hyperfekt
edited Jan 31, 2018
Qubes OS version:
R4.0rc3
Affected TemplateVMs:
whonix-gw
Steps to reproduce the behavior:
perform the following steps in sys-whonix:
Expected behavior:
Tor Bootstrap completes successfully, a circuit is established.
Actual behavior:
Whonixcheck aborts with the following message:
General notes:
In an AppVM with the same whonix-gw template and the same settings, a circuit is successfully established. The same failure occurs with a clone of sys-whonix.
Nothing was changed, this is a fresh install.
The testing repository as of 22:15 UTC+1, 31-01-18 does not include a fix for this issue.
Related issues: