Whonix Connection Issues

misterx · December 3, 2020, 6:13pm

Hi there.

I just installed Qubes and am trying to get Whonix to work.

The Tor Control Panel in sys-whonix shows “Connected to the Tor network” and nyx status monitor shows small tiny traffic spikes.

But: Tor Browser in anon-whonix gets connection timeouts.

Also: WhonixCheck in both sys-whonix and anon-whonix is stuck on “Waiting for Tor Connection”.

Any recommendations for how to troubleshoot this?

misterx · December 3, 2020, 6:41pm

Small update: after restarting, a whonixcheck in sys-whonix now reports “Connected to Tor Network”.

But the hanging issue is still present in anon-whonix (which I also restarted multiple times).

Clodius · December 5, 2020, 5:07am

i tend to keep a sys-whonix control panel open so you can see what is happening with the gateway,

i believe the -ws just uses the -gw, so not thinking whatever -ws is waiting for is relevant?

tanky0u · June 6, 2022, 12:51pm

I am having the same issue. The sys-whonix control panel up the right hand side on the xfce bar is having a padlock with “X” sign (I guess that means it is disconnected from Tor network).

However, when I click on that icon > sys-whonix > “Tor control panel” button, the opened window restarts the Tor connection and it says, “Tor status: Connected to the Tor network!”, all the while, the padlock icon is still with the “X” sign.

Furthermore, whonix Tor browser during this get timeout errors, while other untrusted qube Firefox is able to connect to the internet.

Any suggestions?

tzwcfq · June 6, 2022, 1:02pm

What if you restart sdwdate from Time Synchronisation Monitor icon in tray?

tanky0u · June 6, 2022, 1:05pm

You mean doing the “Time Synch Monitor icon in tray” > sys-whonix > “Tor control panel” > “Restart Tor” ?

If that’s the case, when I do that, tor-control-panel window opens and for a brief second I catch Tor status in yellow/orange colors, and this then quickly turns green, saying “Connected to the Tor Network!” however the Time Synchronization Monitor icon in the tray is still a lockpad with a cross in it.

tzwcfq · June 6, 2022, 1:16pm

No, “Time Synch Monitor icon in tray” > sys-whonix > “Restart sdwdate”

tanky0u · June 6, 2022, 1:24pm

Doing so doesn’t fix the connection issue. Tor browser in Whonix disposable qube still goes into timeout trying to connect to https://check.torproject.org

I also tried adding bridges (obfs, “the China one”, the snowflake), but they didn’t solve the Timeout error that I get with Tor Browser.

Maybe it’s the specific WiFi connection that I have in the cafe that I am in. I will try connecting with Whonix on different WiFi and report back.

tzwcfq · June 6, 2022, 1:27pm

Copy and paste here sdwdate log from “Time Synch Monitor icon in tray” > sys-whonix > “Open sdwdate’s log”

tanky0u · June 6, 2022, 1:36pm

It is quite lengty, but here it is below:

+ set -e
+ true 'INFO /usr/bin/sdwdate-log-viewer: START'
+ /bin/journalctl --boot --output cat -n 10000 -f
+ grep --color 'sdwdate\|bootclockrandomization\|anondate\|firewall\|suspend-pre\|suspend-post'
/var/lib/sdwdate is not a symlink
Bind mounting /rw/bind-dirs/var/lib/sdwdate onto /var/lib/sdwdate
Starting Whonix firewall loader...
2022-06-06 12:36:48 - /usr/bin/whonix-gateway-firewall - OK: Loading Whonix firewall...
2022-06-06 12:36:48 - /usr/bin/whonix-gateway-firewall - OK: Skipping firewall mode detection since already set to 'full'.
2022-06-06 12:36:48 - /usr/bin/whonix-gateway-firewall - OK: (Full torified network access allowed.)
audit: type=1400 audit(1654519008.964:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/whonix_firewall" pid=421 comm="apparmor_parser"
audit: type=1400 audit(1654519008.964:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/libexec/whonix-firewall/**" pid=421 comm="apparmor_parser"
AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/whonix_firewall" pid=421 comm="apparmor_parser"
AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/libexec/whonix-firewall/**" pid=421 comm="apparmor_parser"
audit: type=1400 audit(1654519008.995:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="bootclockrandomization" pid=437 comm="apparmor_parser"
AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="bootclockrandomization" pid=437 comm="apparmor_parser"
AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/sdwdate" pid=450 comm="apparmor_parser"
Condition check resulted in Qubes base firewall settings being skipped.
Condition check resulted in Qubes firewall updater being skipped.
+ addgroup sdwdate systemd-journal
The user `sdwdate' is already a member of `systemd-journal'.
+ gcc /usr/libexec/sdwdate/sclockadj.c -o /usr/libexec/sdwdate/sclockadj -ldl -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now
2022-06-06 12:36:04 - /usr/bin/whonix-gateway-firewall - OK: Whonix firewall loaded.
Finished Whonix firewall loader.
Started Whonix firewall watcher.
Finished Notify sdwdate-gui on gateway about shutdown..
2022-06-06 12:36:08 - sdwdate - INFO - sdwdate started. PID: 1068
2022-06-06 12:36:08 - sdwdate - INFO - Tor socks host: 127.0.0.1 Tor socks port: 9108
2022-06-06 12:36:08 - sdwdate - INFO - Running sdwdate main loop. iteration: 1 / 10000
2022-06-06 12:36:10 - sdwdate - INFO - PREPARATION:
2022-06-06 12:36:10 - sdwdate - INFO -
__ Status: First run after boot. (Creating file '/run/sdwdate/onion-time-script-after-boot'.)
2022-06-06 12:36:10 - sdwdate - INFO - PREPARATION RESULT: WAIT.
2022-06-06 12:36:10 - sdwdate - INFO -
2022-06-06 12:36:13 - sdwdate - INFO - PREPARATION:
2022-06-06 12:36:13 - sdwdate - INFO -
2022-06-06 12:36:13 - sdwdate - INFO - PREPARATION RESULT: WAIT.
2022-06-06 12:36:13 - sdwdate - INFO -
2022-06-06 12:36:17 - sdwdate - INFO - PREPARATION:
2022-06-06 12:36:17 - sdwdate - INFO - __ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
2022-06-06 12:36:17 - sdwdate - INFO - PREPARATION RESULT: SUCCESS.
2022-06-06 12:36:17 - sdwdate - INFO -
2022-06-06 12:36:17 - sdwdate - INFO - Initial time fetching in progress...
2022-06-06 12:36:17 - sdwdate - INFO - Running sdwdate fetch loop. iteration: 1
2022-06-06 12:36:17 - sdwdate - INFO - pool 0: pool_size: 18 url_index: 13 already_picked_number: 1 already_picked_index: [13]
2022-06-06 12:36:17 - sdwdate - INFO - pool 1: pool_size: 18 url_index: 11 already_picked_number: 1 already_picked_index: [11]
2022-06-06 12:36:17 - sdwdate - INFO - pool 2: pool_size: 25 url_index: 1 already_picked_number: 1 already_picked_index: [1]
2022-06-06 12:36:17 - sdwdate - INFO - requested urls ['http://monerotoruzizulg5ttgat2emf4d6fbmiea25detrmmy7erypseyteyd.onion', 'http://fpfjxcrmw437h6z2xl3w4czl55kvkmxpapg37bbopsafdu7q454byxid.onion', 'https://vfnmxpa6fo4jdpyq3yneqhglluweax2uclvxkytfpmpkp5rsl75ir5qd.onion']
[session uid=1000 pid=1269] Activating service name='org.gtk.vfs.Daemon' requested by ':1.7' (uid=1000 pid=5079 comm="xfce4-terminal --title=sdwdate Log Viewer --hold -")
    user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/sdwdate-log-viewer
2022-06-06 12:38:17 - sdwdate - INFO - returned urls "['http://monerotoruzizulg5ttgat2emf4d6fbmiea25detrmmy7erypseyteyd.onion', 'http://fpfjxcrmw437h6z2xl3w4czl55kvkmxpapg37bbopsafdu7q454byxid.onion', 'https://vfnmxpa6fo4jdpyq3yneqhglluweax2uclvxkytfpmpkp5rsl75ir5qd.onion']"
2022-06-06 12:38:17 - sdwdate - INFO -
2022-06-06 12:38:17 - sdwdate - INFO - failed_urls: 3 allowed_failures: 6
2022-06-06 12:38:17 - sdwdate - INFO - Running sdwdate fetch loop. iteration: 2
2022-06-06 12:38:17 - sdwdate - INFO - pool 0: pool_size: 18 url_index: 9 already_picked_number: 2 already_picked_index: [13, 9]
2022-06-06 12:38:17 - sdwdate - INFO - pool 1: pool_size: 18 url_index: 3 already_picked_number: 2 already_picked_index: [11, 3]
2022-06-06 12:38:17 - sdwdate - INFO - pool 2: pool_size: 25 url_index: 23 already_picked_number: 2 already_picked_index: [1, 23]
2022-06-06 12:38:17 - sdwdate - INFO - requested urls ['http://offprivqqdxfmssktx3y5h3miqvceq6yy37s5sxkhz4mojvsz74ohqid.onion', 'http://cct5wy6mzgmft24xzw6zeaf55aaqmo6324gjlsghdhbiw5gdaaf4pkad.onion', 'http://ogdwaroarq4p6rnfn2hl4crvldyruyc2g24435qtxmd3twhevg7dsqid.onion']
    user : PWD=/home/user ; USER=sdwdate-gui ; COMMAND=/usr/bin/bash -c echo "disp9062 status" | tee /run/sdwdate-gui/anon-status >/dev/null
pam_unix(sudo:session): session opened for user sdwdate-gui(uid=113) by (uid=1000)
pam_unix(sudo:session): session closed for user sdwdate-gui
2022-06-06 12:40:17 - sdwdate - INFO - returned urls "['http://offprivqqdxfmssktx3y5h3miqvceq6yy37s5sxkhz4mojvsz74ohqid.onion', 'http://cct5wy6mzgmft24xzw6zeaf55aaqmo6324gjlsghdhbiw5gdaaf4pkad.onion', 'http://ogdwaroarq4p6rnfn2hl4crvldyruyc2g24435qtxmd3twhevg7dsqid.onion']"
2022-06-06 12:40:17 - sdwdate - INFO -
2022-06-06 12:40:17 - sdwdate - ERROR - General Timeout Error. Internet connection might be down.
2022-06-06 12:40:17 - sdwdate - INFO - Sleeping for 97 minutes, ok.
2022-06-06 12:40:17 - sdwdate - INFO - running command: sleep 5815.215267807
    user : PWD=/home/user ; USER=sdwdate-gui ; COMMAND=/usr/bin/bash -c echo "disp9062 status" | tee /run/sdwdate-gui/anon-status >/dev/null
pam_unix(sudo:session): session opened for user sdwdate-gui(uid=113) by (uid=1000)
pam_unix(sudo:session): session closed for user sdwdate-gui
    user : PWD=/home/user ; USER=sdwdate-gui ; COMMAND=/usr/bin/bash -c echo "anon-whonix status" | tee /run/sdwdate-gui/anon-status >/dev/null
pam_unix(sudo:session): session opened for user sdwdate-gui(uid=113) by (uid=1000)
pam_unix(sudo:session): session closed for user sdwdate-gui
    user : PWD=/home/user ; USER=sdwdate-gui ; COMMAND=/usr/bin/bash -c echo "anon-whonix status" | tee /run/sdwdate-gui/anon-status >/dev/null
pam_unix(sudo:session): session opened for user sdwdate-gui(uid=113) by (uid=1000)
pam_unix(sudo:session): session closed for user sdwdate-gui
    user : PWD=/home/user ; USER=root ; COMMAND=/usr/sbin/sdwdate-clock-jump
    root : PWD=/home/user ; USER=sdwdate ; COMMAND=/usr/bin/touch /run/sdwdate/clock_jump_do_once
pam_unix(sudo:session): session opened for user sdwdate(uid=111) by (uid=0)
pam_unix(sudo:session): session closed for user sdwdate
2022-06-06 12:51:52 - sdwdate - INFO - Signal SIGTERM received.
2022-06-06 12:51:52 - sdwdate - INFO - Exiting with exit_code '143' because or reason 'signal_handler called'.
2022-06-06 12:51:52 - sdwdate - INFO - sdwdate stopped by user or system.
2022-06-06 12:51:52 - sdwdate - INFO - sclockadj process not running, ok.
2022-06-06 12:51:52 - sdwdate - INFO - Terminated sleep process.
2022-06-06 12:51:52 - sdwdate - INFO - End.
sdwdate.service: Succeeded.
sdwdate.service: Consumed 6.281s CPU time.
2022-06-06 12:51:53 - sdwdate - INFO - sdwdate started. PID: 5881
2022-06-06 12:51:53 - sdwdate - INFO - Tor socks host: 127.0.0.1 Tor socks port: 9108
2022-06-06 12:51:53 - sdwdate - INFO - Running sdwdate main loop. iteration: 1 / 10000
2022-06-06 12:51:54 - sdwdate - INFO - PREPARATION:
2022-06-06 12:51:54 - sdwdate - INFO - __ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
2022-06-06 12:51:54 - sdwdate - INFO - PREPARATION RESULT: SUCCESS.
2022-06-06 12:51:54 - sdwdate - INFO -
2022-06-06 12:51:54 - sdwdate - INFO - Initial time fetching in progress...
2022-06-06 12:51:54 - sdwdate - INFO - Running sdwdate fetch loop. iteration: 1
2022-06-06 12:51:54 - sdwdate - INFO - pool 0: pool_size: 18 url_index: 8 already_picked_number: 1 already_picked_index: [8]
2022-06-06 12:51:54 - sdwdate - INFO - pool 1: pool_size: 18 url_index: 1 already_picked_number: 1 already_picked_index: [1]
2022-06-06 12:51:54 - sdwdate - INFO - pool 2: pool_size: 25 url_index: 11 already_picked_number: 1 already_picked_index: [11]
2022-06-06 12:51:54 - sdwdate - INFO - requested urls ['http://45tbhx5prlejzjgn36nqaxqb6qnm73pbohuvqkpxz2zowh57bxqawkid.onion', 'http://zkaan2xfbuxia2wpf7ofnkbz6r5zdbbvxbunvp5g2iebopbfc4iqmbad.onion', 'http://lvtu6mh6dd6ynqcxtd2mseqfkm7g2iuxvjobbyzpgx2jt427zvd7n3ad.onion']
2022-06-06 12:53:54 - sdwdate - INFO - returned urls "['http://45tbhx5prlejzjgn36nqaxqb6qnm73pbohuvqkpxz2zowh57bxqawkid.onion', 'http://zkaan2xfbuxia2wpf7ofnkbz6r5zdbbvxbunvp5g2iebopbfc4iqmbad.onion', 'http://lvtu6mh6dd6ynqcxtd2mseqfkm7g2iuxvjobbyzpgx2jt427zvd7n3ad.onion']"
2022-06-06 12:53:54 - sdwdate - INFO -
2022-06-06 12:53:54 - sdwdate - INFO - failed_urls: 3 allowed_failures: 6
2022-06-06 12:53:54 - sdwdate - INFO - Running sdwdate fetch loop. iteration: 2
2022-06-06 12:53:54 - sdwdate - INFO - pool 0: pool_size: 18 url_index: 9 already_picked_number: 2 already_picked_index: [8, 9]
2022-06-06 12:53:54 - sdwdate - INFO - pool 1: pool_size: 18 url_index: 4 already_picked_number: 2 already_picked_index: [1, 4]
2022-06-06 12:53:54 - sdwdate - INFO - pool 2: pool_size: 25 url_index: 22 already_picked_number: 2 already_picked_index: [11, 22]
2022-06-06 12:53:54 - sdwdate - INFO - requested urls ['http://offprivqqdxfmssktx3y5h3miqvceq6yy37s5sxkhz4mojvsz74ohqid.onion', 'https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion', 'http://xm33ge4kupk5o66eqxcd2r4fqcplpqb2sbdduf5z2nw4g2jrxe57luid.onion']
2022-06-06 12:55:54 - sdwdate - INFO - returned urls "['http://offprivqqdxfmssktx3y5h3miqvceq6yy37s5sxkhz4mojvsz74ohqid.onion', 'https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion', 'http://xm33ge4kupk5o66eqxcd2r4fqcplpqb2sbdduf5z2nw4g2jrxe57luid.onion']"
2022-06-06 12:55:54 - sdwdate - INFO -
2022-06-06 12:55:54 - sdwdate - INFO - failed_urls: 6 allowed_failures: 6
2022-06-06 12:55:54 - sdwdate - INFO - Running sdwdate fetch loop. iteration: 3
2022-06-06 12:55:54 - sdwdate - INFO - pool 0: pool_size: 18 url_index: 0 already_picked_number: 3 already_picked_index: [8, 9, 0]
2022-06-06 12:55:54 - sdwdate - INFO - pool 1: pool_size: 18 url_index: 17 already_picked_number: 3 already_picked_index: [1, 4, 17]
2022-06-06 12:55:54 - sdwdate - INFO - pool 2: pool_size: 25 url_index: 5 already_picked_number: 3 already_picked_index: [11, 22, 5]
2022-06-06 12:55:54 - sdwdate - INFO - requested urls ['https://p53lf57qovyuvwsc6xnrppyply3vtqm7l6pcobkmyqsiofyeznfu5uqd.onion', 'http://5gdvpfoh6kb2iqbizb37lzk2ddzrwa47m6rpdueg2m656fovmbhoptqd.onion', 'http://b52gknakgsyqqeq476oi5nymw6yapysfig4owqgwppi5qpuk4az6bxad.onion']
2022-06-06 12:57:54 - sdwdate - INFO - returned urls "['https://p53lf57qovyuvwsc6xnrppyply3vtqm7l6pcobkmyqsiofyeznfu5uqd.onion', 'http://5gdvpfoh6kb2iqbizb37lzk2ddzrwa47m6rpdueg2m656fovmbhoptqd.onion', 'http://b52gknakgsyqqeq476oi5nymw6yapysfig4owqgwppi5qpuk4az6bxad.onion']"
2022-06-06 12:57:54 - sdwdate - INFO -
2022-06-06 12:57:54 - sdwdate - INFO - failed_urls: 9 allowed_failures: 6
2022-06-06 12:57:54 - sdwdate - ERROR - Maximum allowed number of failures. Giving up.
2022-06-06 12:57:54 - sdwdate - INFO - Sleeping for 116 minutes, ok.
2022-06-06 12:57:54 - sdwdate - INFO - running command: sleep 6959.217963267
    user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/sdwdate-log-viewer
    user : PWD=/home/user ; USER=root ; COMMAND=/usr/sbin/sdwdate-clock-jump
    root : PWD=/home/user ; USER=sdwdate ; COMMAND=/usr/bin/touch /run/sdwdate/clock_jump_do_once
pam_unix(sudo:session): session opened for user sdwdate(uid=111) by (uid=0)
pam_unix(sudo:session): session closed for user sdwdate
2022-06-06 13:16:04 - sdwdate - INFO - Signal SIGTERM received.
2022-06-06 13:16:04 - sdwdate - INFO - Exiting with exit_code '143' because or reason 'signal_handler called'.
2022-06-06 13:16:04 - sdwdate - INFO - sdwdate stopped by user or system.
2022-06-06 13:16:04 - sdwdate - INFO - sclockadj process not running, ok.
2022-06-06 13:16:04 - sdwdate - INFO - Terminated sleep process.
2022-06-06 13:16:04 - sdwdate - INFO - End.
sdwdate.service: Succeeded.
sdwdate.service: Consumed 6.020s CPU time.
2022-06-06 13:16:05 - sdwdate - INFO - sdwdate started. PID: 7000
2022-06-06 13:16:05 - sdwdate - INFO - Tor socks host: 127.0.0.1 Tor socks port: 9108
2022-06-06 13:16:05 - sdwdate - INFO - Running sdwdate main loop. iteration: 1 / 10000
2022-06-06 13:16:07 - sdwdate - INFO - PREPARATION:
2022-06-06 13:16:07 - sdwdate - INFO - __ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
2022-06-06 13:16:07 - sdwdate - INFO - PREPARATION RESULT: SUCCESS.
2022-06-06 13:16:07 - sdwdate - INFO -
2022-06-06 13:16:07 - sdwdate - INFO - Initial time fetching in progress...
2022-06-06 13:16:07 - sdwdate - INFO - Running sdwdate fetch loop. iteration: 1
2022-06-06 13:16:07 - sdwdate - INFO - pool 0: pool_size: 18 url_index: 4 already_picked_number: 1 already_picked_index: [4]
2022-06-06 13:16:07 - sdwdate - INFO - pool 1: pool_size: 18 url_index: 12 already_picked_number: 1 already_picked_index: [12]
2022-06-06 13:16:07 - sdwdate - INFO - pool 2: pool_size: 25 url_index: 17 already_picked_number: 1 already_picked_index: [17]
2022-06-06 13:16:07 - sdwdate - INFO - requested urls ['http://keybase5wmilwokqirssclfnsqrjdsi7jdir5wy7y7iu3tanwmtp6oid.onion', 'http://xp44cagis447k3lpb4wwhcqukix6cgqokbuys24vmxmbzmaq2gjvc2yd.onion', 'http://xpxduj55x2j27l2qytu2tcetykyfxbjbafin3x4i3ywddzphkbrd3jyd.onion']
2022-06-06 13:18:07 - sdwdate - INFO - returned urls "['http://keybase5wmilwokqirssclfnsqrjdsi7jdir5wy7y7iu3tanwmtp6oid.onion', 'http://xp44cagis447k3lpb4wwhcqukix6cgqokbuys24vmxmbzmaq2gjvc2yd.onion', 'http://xpxduj55x2j27l2qytu2tcetykyfxbjbafin3x4i3ywddzphkbrd3jyd.onion']"
2022-06-06 13:18:07 - sdwdate - INFO -
2022-06-06 13:18:07 - sdwdate - INFO - failed_urls: 3 allowed_failures: 6
2022-06-06 13:18:07 - sdwdate - INFO - Running sdwdate fetch loop. iteration: 2
2022-06-06 13:18:07 - sdwdate - INFO - pool 0: pool_size: 18 url_index: 7 already_picked_number: 2 already_picked_index: [4, 7]
2022-06-06 13:18:07 - sdwdate - INFO - pool 1: pool_size: 18 url_index: 7 already_picked_number: 2 already_picked_index: [12, 7]
2022-06-06 13:18:07 - sdwdate - INFO - pool 2: pool_size: 25 url_index: 5 already_picked_number: 2 already_picked_index: [17, 5]
2022-06-06 13:18:07 - sdwdate - INFO - requested urls ['http://potatoynwcg34xyodol6p6hvi5e4xelxdeowsl5t2daxywepub32y7yd.onion', 'http://lxjacvxrozjlxd7pqced7dyefnbityrwqjosuuaqponlg3v7esifrzad.onion', 'http://b52gknakgsyqqeq476oi5nymw6yapysfig4owqgwppi5qpuk4az6bxad.onion']
2022-06-06 13:20:07 - sdwdate - INFO - returned urls "['http://potatoynwcg34xyodol6p6hvi5e4xelxdeowsl5t2daxywepub32y7yd.onion', 'http://lxjacvxrozjlxd7pqced7dyefnbityrwqjosuuaqponlg3v7esifrzad.onion', 'http://b52gknakgsyqqeq476oi5nymw6yapysfig4owqgwppi5qpuk4az6bxad.onion']"
2022-06-06 13:20:07 - sdwdate - INFO -
2022-06-06 13:20:07 - sdwdate - INFO - failed_urls: 6 allowed_failures: 6
2022-06-06 13:20:07 - sdwdate - INFO - Running sdwdate fetch loop. iteration: 3
2022-06-06 13:20:07 - sdwdate - INFO - pool 0: pool_size: 18 url_index: 17 already_picked_number: 3 already_picked_index: [4, 7, 17]
2022-06-06 13:20:07 - sdwdate - INFO - pool 1: pool_size: 18 url_index: 11 already_picked_number: 3 already_picked_index: [12, 7, 11]
2022-06-06 13:20:07 - sdwdate - INFO - pool 2: pool_size: 25 url_index: 18 already_picked_number: 3 already_picked_index: [17, 5, 18]
2022-06-06 13:20:07 - sdwdate - INFO - requested urls ['http://jrw32khnmfehvdsvwdf34mywoqj5emvxh4mzbkls6jk2cb3thcgz6nid.onion', 'http://fpfjxcrmw437h6z2xl3w4czl55kvkmxpapg37bbopsafdu7q454byxid.onion', 'http://srumyob2jq5nvppzt66aaab333n2wmq6xgkg4khfe24ixdb7umf7mtyd.onion']
    user : PWD=/home/user ; USER=sdwdate-gui ; COMMAND=/usr/bin/bash -c echo "disp1823 status" | tee /run/sdwdate-gui/anon-status >/dev/null
pam_unix(sudo:session): session opened for user sdwdate-gui(uid=113) by (uid=1000)
pam_unix(sudo:session): session closed for user sdwdate-gui
2022-06-06 13:22:07 - sdwdate - INFO - returned urls "['http://jrw32khnmfehvdsvwdf34mywoqj5emvxh4mzbkls6jk2cb3thcgz6nid.onion', 'http://fpfjxcrmw437h6z2xl3w4czl55kvkmxpapg37bbopsafdu7q454byxid.onion', 'http://srumyob2jq5nvppzt66aaab333n2wmq6xgkg4khfe24ixdb7umf7mtyd.onion']"
2022-06-06 13:22:07 - sdwdate - INFO -
2022-06-06 13:22:07 - sdwdate - ERROR - General Timeout Error. Internet connection might be down.
2022-06-06 13:22:07 - sdwdate - INFO - Sleeping for 165 minutes, ok.
2022-06-06 13:22:07 - sdwdate - INFO - running command: sleep 9906.177963935
    user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/sdwdate-log-viewer

tzwcfq · June 6, 2022, 1:42pm

It seems that tor is not working.
Check tor log in Tor Control Panel and paste log after this line if you have it:
[notice] Bootstrapped 100% (done): Done
If you don’t have it then at what % is your bootstrap is stuck?

tanky0u · June 6, 2022, 1:53pm

I just checked the mentioned Tor log in the Tor Control Panel. It’s a quite lengthy log and the interface didn’t have a search bar/button, so, I had to peruse it with my eye. And I couldn’t see such “[notice] Bootstrapped 100% (done): Done” line in the logs.

The Tor log doesn’t seem to even have a percentage report for the bootstrapping process. It is crowded with such lines:

Jun 06 13:22... [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jun 06 13:22... [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jun 06 13:22... [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jun 06 13:23... [notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish.
Jun 06 13:25... [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
Jun 06 13:25... [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
Jun 06 13:25... [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
Jun 06 13:29... [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
Jun 06 13:29... [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes.
Jun 06 13:43... [notice] New control connection opened.
...
...

And a bit upper to these lines, there are lines such as,

Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9218' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9219' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9220' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9221' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9222' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9223' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9224' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9225' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9226' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9227' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9228' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] You configured a non-loopback address '10.137.0.12:9229' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 13:18... [notice] Tor 0.4.7.7 opening log file.
Jun 06 13:18... [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jun 06 13:18... [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)
Jun 06 13:18... [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit)

Oh, looking further up in the log file, I see such progression reporting for Bootstrapping:

Jun 06 12:41... [notice] You configured a non-loopback address '10.137.0.12:9225' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 12:41... [notice] You configured a non-loopback address '10.137.0.12:9226' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 12:41... [notice] You configured a non-loopback address '10.137.0.12:9227' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 12:41... [notice] You configured a non-loopback address '10.137.0.12:9228' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 12:41... [notice] You configured a non-loopback address '10.137.0.12:9229' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Jun 06 12:41... [notice] Tor 0.4.7.7 opening log file.
Jun 06 12:41... [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Jun 06 12:41... [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Jun 06 12:41... [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Jun 06 12:41... [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Jun 06 12:41... [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Jun 06 12:42... [notice] No circuits are opened. Relaxed timeout for circuit 6 (a Hidden service client: Fetching HS descriptor 5-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway.
Jun 06 12:42... [notice] Bootstrapped 100% (done): Done
Jun 06 12:43... [notice] New control connection opened from 127.0.0.1.
Jun 06 12:43... [notice] New control connection opened from 127.0.0.1.
Jun 06 12:43... [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes.
Jun 06 12:43... [notice] New control connection opened from 127.0.0.1.
Jun 06 12:43... [notice] New control connection opened from 127.0.0.1.
Jun 06 12:45... [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jun 06 12:45... [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)

Kinda messed up and long. But I hope these lines are telling something.

tzwcfq · June 6, 2022, 2:03pm

Not sure why your tor network stop to work after connection. Maybe try to use bridges.

ohno · June 30, 2022, 12:39am

I am having the same issue.

tanky0u · July 1, 2022, 11:14am

I have tried using all the bridges:

meek-azure gets stuck at 10%, the Tor log reads, “[warn] Problem bootsrapping. Stuck at 10% (conn_done): Connected to a relay. (TLS_ERROR; TLS_ERROR; count 22; recommendation warn; host <HOST_IDENTIFIER>”)
obfs4 manages to connect 100%, but the whonix tor browser cannot keep a clearnet connection (tested, https://check.torproject.org ), while the Tor log reads, "[warn] Proxy Client: unable to connect OR connection (handshaking (proxy)) with <IP_ADDRESS> ID= etc. etc. etc. (“general SOCKS server failure”). Also, one line below that [warn] notice reads, “[notice] Ignoring directory request, since no bridge nodes available yet.”
snowflake causes a crash in the tor widget.
Setting “Bridges type: None” also manages to connect 100%. But again a disposable whonix-ws Tor browser gets time out error in connecting to https://check.torproject.org website. While the Tor log reads many lines of, “[notice] New control connection opened from 127.0.0.1.” Also, I see a line that reads, “[notice] No circuits are opened. Relaxed timeout for circuit 84 (a Measuring circuit timeout 3-hop circuit in state waiting to see how other guards perform with channel state open) to 60000ms. However, it appears that the circuit has timed out anyway.”

That’s so freaking weird. I mean, I am in a 3rd wave coffee shop with a co-working desk. There is a WiFi for guests’ connecting. It’s not like I am in a Uighur concentration camp in Xinjiang or something. So, I am having difficulty in what to make of these Tor connectivity errors. And, this type of difficulty in connecting to Tor via Whonix on QubesOS that I listed above are only specific to this single coffee shop that I am frequenting. Using other coffee shops’ WiFi networks works and many of them do not even require a bridge setup to connect to Tor.

tzwcfq · July 1, 2022, 11:42am

Maybe this coffee shop has deep packet inspection setup for it’s network or something and it’s just filter all non-HTTP/HTTPS traffic so you’ll need to obfuscate the traffic as normal HTTPS with shadowsocks and plugins or something.

tanky0u · July 1, 2022, 11:43am

I thought this was exclusive to oppressive nation states. Is this tech becoming a commonplace so as to be seen in a “normal” coffee shop?

How would I do that?

tanky0u · July 1, 2022, 11:46am

Also, another funny thing is, my smartphone running grapheneos with Orbot is able to connect to Tor on the same coffee shop’s WiFi network. Also, the Tor Browser (installed via FDroid) on the same smartphone on the same coffee shop’s WiFi network is able to connect to websites.

So, whatever this is, I think it’s specific to Whonix within QubesOS, and not a general Deep Packet Inspection.

tzwcfq · July 1, 2022, 12:00pm

It’s not a simple setup but there’re guides about it if you search for “shadowsocks v2ray clouflare docker”.

But since you’re saying that it works on your smartphone then that’s not the case for you.
You can try to install tor package in debian/fedora template and check if you’ll have the same problem as with whonix.

tanky0u · July 6, 2022, 3:35pm

Just to update this thread:
The Whonix connection issues the way I described above still continue the same.

I tried connecting to the Tor network, this time, using TAILS. So I booted from the USB a TAILS OS, and tried connecting to the Tor. And it worked. I was able to connect to websites on Tor Browser without time-ing out.

So, this might be an indication that the there is an exotic issue with the way Whonix configures itself on QubesOS, that that single cafe wifi was just negating.