when I install whonix gateway, during the final installation I still have 5% while downloading, the track works normally for me, my country does not block it either
I did everything and it still doesnât work. after entering systemcheck: [WARNING] [systemcheck] Tor Check Result:
Tor is disabled. Therefore you most likely can not connect to the internet.
(Debugging information: Could not find DisableNetwork 0 in Tor config.)
Please close this window and enable Tor using Anon Connection Wizard!
Start Menu â System â Anon Connection Wizard
or in Terminal: sudo setup-dist
or manually (If you know about the public Tor network!) and open /usr/local/etc/torrc.d/50_user.conf with root rights
(Start Menu â System â Tor User Config) and set:
DisableNetwork 0
Then run systemcheck again.
zsh: exit 1 systemcheck
This.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 6 seconds. | 5 % done.
- Tor Circuit: not established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=5 TAG=conn SUMMARY=âConnecting to a relayâ
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information, see: sdwdate-gui â right click â Open sdwdateâs log
- onion-time-pre-script reports:
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time âMon Jun 12 00:00:00 UTC 2023â and expiration timestamp âTue May 17 10:00:00 UTC 2033â, ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=5 TAG=conn SUMMARY=âConnecting to a relayâ
__ Tor circuit: not established
__ Tor Consensus Time Sanity Check: Consensus time sanity check failed.
__ anondate_use: Running âanondate-setâ (by creating file â/run/sdwdate/request_anondate-setâ)âŚ
__ ### END: ### Exiting with exit_code â2â indicating âwait, show busy icon and retry.â.
This isnât the first time this is happening and it wonât be the last time either. Therefore documentation has troubleshooting steps exactly for this situation. It wonât be possible to provide any help without going through these steps.
The only way to make progress and maybe resolve this issue is going through the troubleshooting steps and then report their results here.
-
is good
-
working
-
with ping all is good
-
with all is the same
-
[gateway user ~]% sudo anondate-get
[sudo] password for user:
______ ### START: ### /usr/sbin/anondate-get
______ WARNING: Tor bootstrap not done.
______ INFO: Attempting to determine Tor consensus time middle rangeâŚ
______ WARNING: Could not determine Tor consensus time middle range.
______ INFO: Attempting to determine Tor certificate lifetimeâŚ
______ INFO: Tor certificate lifetime valid, ok.
______ INFO: Could not determine a time later than minimum time from either Tor consensus time or Tor certificate lifetime, ok.
______ INFO: Showing minimum time instead as resultâŚ
______ INFO: minimum time: â2023-06-12 00:00:00â
2023-06-12 00:00:00
______ ### END: ### Exiting with exit_code â0â indicating âShowed Tor consensus time middle range or minimum time.â.
[gateway user ~]% -
i have the correct one
-
I didnât configure anything
-
nothing helped
-
Tor browser runs on the host
-
I sent the error from the console above
-
so others have
-
Tor failed to (re)start
Job for tor@default.service failed because the control process exited with error code.
Error Code: 1
Often, this is because of your torrc file(s) has corrupted settings.
See âsystemctl status tor@default.serviceâ and âjournalctl -xeâ for details.
You may not be able to use any network facing application for now.
14. not
15. --verbose --leak-tests
[INFO] [systemcheck] | Whonix-Gateway | Sun Nov 5 20:08:46 UTC 2023
[INFO] [systemcheck] Check sudo Result: OK
[INFO] [systemcheck] Whonix build version: 17.0.4.5
[INFO] [systemcheck] whonix-gateway-packages-dependencies-cli: 23.8-1
[INFO] [systemcheck] derivative_major_release_version /etc/whonix_version: 17
[INFO] [systemcheck] Whonix Support Status of this Major Version: Ok.
[WARNING] [systemcheck] Hardened Malloc: Disabled.
[INFO] [systemcheck] Spectre Meltdown Test: skipping since spectre_meltdown_check=false, ok.
[INFO] [systemcheck] Package Manager Consistency Check Result: Output of command dpkg --audit was empty, ok.
[INFO] [systemcheck] ERROR: ARG_MAX exceeded!
debug information:
output_func was called with too many arguments.
${FUNCNAME[0]}: output_func
${FUNCNAME[1]}: output_func_cli
${FUNCNAME[2]}: check_journal
${FUNCNAME[3]}: systemcheck_main
${FUNCNAME[5]}: main
${FUNCNAME[6]}:
$0: /usr/libexec/systemcheck/systemcheck
[INFO] [systemcheck] check network interfaces Result: Ok.
[INFO] [systemcheck] Qubes Settings Test Result: Skipped, because Qubes not detected.
[INFO] [systemcheck] Check Kernel Messages Test Result: Found nothing remarkable, ok.
[INFO] [systemcheck] Whonix firewall systemd unit check Result: Ok.
[INFO] [systemcheck] Check setup-dist Result: done, ok.
[INFO] [systemcheck] Check Package Manager Running Result: None running, ok.
[INFO] [systemcheck] Tor Check Result: âDisableNetwork 1â not active, ok.
[INFO] [systemcheck] Tor Config Check Result: Tor config ok.
[ERROR] [systemcheck] Tor Running Check Result: Tor is not running.
You have to fix this error, before you can use Tor.
Please restart Tor after fixing this error.
Start Menu -> System -> Restart Tor
or in Terminal: sudo service tor@default restart
Restart systemcheck after fixing this error.
Start Menu â System â System Check
or in Terminal: systemcheck
See also:
www.whonixorg/wiki/Tor#Tor_not_running
Debugging information:
Pid file â/run/tor/tor.pidâ does not exist.
output of âsudo /bin/systemctl --no-pager --no-block status tor@defaultâ:
Ă tor@default.service - Anonymizing overlay network for TCP
Loaded: loaded (/lib/systemd/system/tor@default.service; enabled-runtime; preset: enabled)
Drop-In: /usr/lib/systemd/system/tor@default.service.d
ââ40_network-target.conf, 40_obfs4proxy-workaround.conf, 50_controlsocket-workaround.conf
Active: failed (Result: exit-code) since Sun 2023-11-05 20:03:50 UTC; 5min ago
Duration: 1min 51.283s
Process: 88293 ExecStartPre=/usr/bin/install -Z -m 02755 -o debian-tor -g debian-tor -d /run/tor (code=exited, status=0/SUCCESS)
Process: 88294 ExecStartPre=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 --verify-config (code=exited, status=1/FAILURE)
CPU: 20ms
Nov 05 20:03:50 host systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 5.
Nov 05 20:03:50 host systemd[1]: Stopped tor@default.service - Anonymizing overlay network for TCP.
Nov 05 20:03:50 host systemd[1]: tor@default.service: Start request repeated too quickly.
Nov 05 20:03:50 host systemd[1]: tor@default.service: Failed with result âexit-codeâ.
Nov 05 20:03:50 host systemd[1]: Failed to start tor@default.service - Anonymizing overlay network for TCP.
zsh: exit 1 systemcheck --verbose --leak-tests
[gateway user ~]% systemcheck --verbose --leak-tests --function check_tor_socks_port
[INFO] [systemcheck] SocksPort IP Leak Test: Testing Torâs SocksPort (SOCKS_PORT_SYSTEMCHECK: 9110)âŚ
[ERROR] [systemcheck] SocksPort IP Leak Test Result: check.torprojectorg/api/ip was not reachable.
You could check, if you can reach check.torprojectorg/api/ip via the Tor Browser Bundle.
(curl exit code: [7] - [Failed to connect to host.])
[gateway user ~]%
This is the issue.
Did you change any Tor config settings?
That link is a good one. Contains information on what to do next.
Tor Documentation for Whonix Users chapter Tor not running in Whonix wiki
To investigate further, see #Configuration Check and #Log Analysis.
I didnât change anything
gateway user ~]% sudo systemctl status tor@default
[sudo] password for user:
â tor@default.service - Anonymizing overlay network for TCP
Loaded: loaded (/lib/systemd/system/tor@default.service; enabled-runtime; >
Drop-In: /usr/lib/systemd/system/tor@default.service.d
ââ40_network-target.conf, 40_obfs4proxy-workaround.conf, 50_contro>
Active: inactive (dead) since Sun 2023-11-05 21:47:44 UTC; 6min ago
Duration: 8.462s
Process: 126969 ExecStartPre=/usr/bin/install -Z -m 02755 -o debian-tor -g >
Process: 126970 ExecStartPre=/usr/bin/tor --defaults-torrc /usr/share/tor/t>
Process: 126971 ExecStart=/usr/bin/tor --defaults-torrc /usr/share/tor/tor->
Process: 126973 ExecStartPost=/bin/kill -HUP ${MAINPID} (code=exited, statu>
Process: 126977 ExecReload=/bin/kill -HUP ${MAINPID} (code=exited, status=0>
Main PID: 126971 (code=exited, status=0/SUCCESS)
CPU: 196ms
Nov 05 21:47:36 host tor[126971]: Nov 05 21:47:36.039 [notice] Opening HTTP tun>
Nov 05 21:47:36 host tor[126971]: Nov 05 21:47:36.039 [notice] Opened HTTP tunn>
Nov 05 21:47:36 host tor[126971]: Nov 05 21:47:36.039 [notice] Opening Control >
Nov 05 21:47:36 host tor[126971]: Nov 05 21:47:36.039 [notice] Opened Control l>
Nov 05 21:47:36 host systemd[1]: Started tor@default.service - Anonymizing over>
Nov 05 21:47:36 host systemd[1]: Reloading tor@default.service - Anonymizing ov>
Nov 05 21:47:36 host systemd[1]: Reloaded tor@default.service - Anonymizing ove>
Nov 05 21:47:44 host systemd[1]: Stopping tor@default.service - Anonymizing ove>
Nov 05 21:47:44 host systemd[1]: tor@default.service: Deactivated successfully.
zsh: interrupt sudo systemctl status tor@default
after typing sudo anon-log I have a very long error OTICE[Sun Nov 05 20:39:27 2023]: Vanguards 0.3.1 connected to Tor 0.4.7.13 using stem 1.8.1
NOTICE[Sun Nov 05 20:39:27 2023]: Tor needs descriptors: Cannot read /var/lib/tor/cached-microdesc-consensus: [Errno 2] No such file or directory: â/var/lib/tor/cached-microdesc-consensusâ. Trying againâŚ
NOTICE[Sun Nov 05 20:39:28 2023]: Vanguards 0.3.1 connected to Tor 0.4.7.13 using stem 1.8.1
NOTICE[Sun Nov 05 20:39:28 2023]: Tor needs descriptors: Cannot read /var/lib/tor/cached-microdesc-consensus: [Errno 2] No such file or directory: â/var/lib/tor/cached-microdesc-consensusâ. Trying againâŚ
NOTICE[Sun Nov 05 20:39:29 2023]: Vanguards 0.3.1 connected to Tor 0.4.7.13 using stem 1.8.1
NOTICE[Sun Nov 05 20:39:29 2023]: Tor needs descriptors: Cannot read /var/lib/tor/cached-microdesc-consensus: [Errno 2] No such file or directory: â/var/lib/tor/cached-microdesc-consensusâ. Trying againâŚ
WARNING[Sun Nov 05 20:39:29 2023]: Tor daemon connection failed: Cannot read /var/lib/tor/cached-microdesc-consensus: [Errno 2] No such file or directory: â/var/lib/tor/cached-microdesc-consensusâ. Trying againâŚ
WARNING[Sun Nov 05 20:39:39 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:39:49 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:39:59 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:40:09 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:40:19 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:40:29 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:40:39 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:40:49 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:40:59 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:41:09 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:41:19 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:41:29 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:41:39 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:41:49 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:41:59 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:42:09 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:42:19 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:42:29 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:42:39 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:42:49 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:42:59 2023]: Tor daemon connection failed: [Errno 2] No such file or directory. Trying againâŚ
WARNING[Sun Nov 05 20:43:09 2023]: Tor daemon connection failed: [Errno 2] No su
- Tor Documentation for Whonix Users chapter Dump Tor Log in Whonix wiki
- Tor Documentation for Whonix Users chapter Watch Tor Log in Whonix wiki
Drop the -u vanguards at the end as it is not relevant for now.
again long error
Nov 05 21:47:36.039 [notice] Opened HTTP tunnel listener connection (ready) on 10.152.152.10:9225
Nov 05 21:47:36.039 [notice] Opening HTTP tunnel listener on 10.152.152.10:9226
Nov 05 21:47:36.039 [notice] Opened HTTP tunnel listener connection (ready) on 10.152.152.10:9226
Nov 05 21:47:36.039 [notice] Opening HTTP tunnel listener on 10.152.152.10:9227
Nov 05 21:47:36.039 [notice] Opened HTTP tunnel listener connection (ready) on 10.152.152.10:9227
Nov 05 21:47:36.039 [notice] Opening HTTP tunnel listener on 10.152.152.10:9228
Nov 05 21:47:36.039 [notice] Opened HTTP tunnel listener connection (ready) on 10.152.152.10:9228
Nov 05 21:47:36.039 [notice] Opening HTTP tunnel listener on 10.152.152.10:9229
Nov 05 21:47:36.039 [notice] Opened HTTP tunnel listener connection (ready) on 10.152.152.10:9229
Nov 05 21:47:36.039 [notice] Opening Control listener on 127.0.0.1:9052
Nov 05 21:47:36.039 [notice] Opened Control listener connection (ready) on 127.0.0.1:9052
Started tor@default.service - Anonymizing overlay network for TCP.
Reloading tor@default.service - Anonymizing overlay network for TCPâŚ
Reloaded tor@default.service - Anonymizing overlay network for TCP.
Stopping tor@default.service - Anonymizing overlay network for TCPâŚ
tor@default.service: Deactivated successfully.
Stopped tor@default.service - Anonymizing overlay network for TCP.
Nov 05 21:47:36.039 [notice] Opening HTTP tunnel listener on 10.152.152.10:9229
Nov 05 21:47:36.039 [notice] Opened HTTP tunnel listener connection (ready) on 10.152.152.10:9229
Nov 05 21:47:36.039 [notice] Opening Control listener on 127.0.0.1:9052
Nov 05 21:47:36.039 [notice] Opened Control listener connection (ready) on 127.0.0.1:9052
Started tor@default.service - Anonymizing overlay network for TCP.
Reloading tor@default.service - Anonymizing overlay network for TCPâŚ
Reloaded tor@default.service - Anonymizing overlay network for TCP.
Stopping tor@default.service - Anonymizing overlay network for TCPâŚ
tor@default.service: Deactivated successfully.
Stopped tor@default.service - Anonymizing overlay network for TCP.
Watch the Tor log + restart. There really should be a real error message at some point.
Itâs âonlyâ a Tor configuration issue. â Fix the Tor configuration issue.
This is unspecific to Whonix.
You can ignore any duplicate lines, no need to post for brevity.
Are you trying something special such as restoring from backup?
Build from source code with modifications and/or errors?
Are you sure you downloaded Whonix from whonix.org?
Which virtualizer?
First, you had this:
Which means Tor was already running. This is progress.
But now, Tor doesnât even start. This is a regression. That really should not happen unless you edited the Tor configuration or did some other special stuff. So some information is missing here.
Also this issue is hard to get. Didnât you just click through âyesâ in Anon Connection Wizard at the first start?
It should really be just a âclick yesâ experience. If you just started using Whonix, you could as well just do a factory reset. I.e. re-install Whonix.
Next time please exactly record any steps youâve taken.
(Whonix is based on Kicksecure.)
1 Like
OP check if your host system time is synced
Un-synced clock on the host can cause this issue
how?
everything except track works
it doesnât try anything else itâs a regular install from whonix org
I tried reinstalling, nothing helped
What is track?
I wrote that while downloading I still have Connecting a relay 5%
time is good