Sys-whonix does not connect anymore

solene · November 27, 2024, 12:10pm

Hi! I have a weird issue with sys-whonix on R4.2.3, tor connection status stays at 0% and I haven’t been able to debug this.

Here is sys-whonix ip a output, which I find weird but maybe it’s fine?

[gateway user ~]% ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:5e:6c:00 brd ff:ff:ff:ff:ff:ff
    inet 10.137.0.9/32 scope global eth0
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether aa:ce:04:79:7f:6c brd ff:ff:ff:ff:ff:ff
    inet 10.137.0.9/32 brd 10.255.255.255 scope global eth1
       valid_lft forever preferred_lft forever

tor control panel logs

Nov 27 12:08... [notice] Tor 0.4.8.12 opening new log file.
Nov 27 12:08... [notice] We compiled with OpenSSL 300000b0: OpenSSL 3.0.11 19 Sep 2023 and we are running with OpenSSL 300000e0: 3.0.14. These two versions should be binary compatible.
Nov 27 12:08... [notice] Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.14, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Nov 27 12:08... [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Nov 27 12:08... [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Nov 27 12:08... [notice] Read configuration file "/etc/tor/torrc".
Nov 27 12:08... [notice] Processing configuration path "/etc/torrc.d/*.conf" at recursion level 1.
Nov 27 12:08... [notice] Including configuration file "/etc/torrc.d/60_network.conf".
Nov 27 12:08... [notice] Including configuration file "/etc/torrc.d/65_gateway.conf".
Nov 27 12:08... [notice] Including configuration file "/etc/torrc.d/65_leak_tests.conf".
Nov 27 12:08... [notice] Including configuration file "/etc/torrc.d/70_workstation.conf".
Nov 27 12:08... [notice] Processing configuration path "/usr/share/tor/tor-service-defaults-torrc.anondist" at recursion level 2.
Nov 27 12:08... [notice] Including configuration file "/usr/share/tor/tor-service-defaults-torrc.anondist".
Nov 27 12:08... [notice] Including configuration file "/etc/torrc.d/95_whonix.conf".
Nov 27 12:08... [notice] Processing configuration path "/usr/local/etc/torrc.d/*.conf" at recursion level 2.
Nov 27 12:08... [notice] Including configuration file "/usr/local/etc/torrc.d/40_tor_control_panel.conf".
Nov 27 12:08... [notice] Including configuration file "/usr/local/etc/torrc.d/50_user.conf".
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:5300' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9040' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9050' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9100' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9101' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9102' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9103' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9104' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9105' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9106' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9107' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9108' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9109' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9110' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9111' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9114' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9115' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9117' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9118' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9122' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9123' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9124' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9125' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9150' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9152' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9173' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9174' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9175' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9176' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9177' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9178' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9179' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9040' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9190' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9191' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9192' for HTTP TunnelPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
'10.137.0.9: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.
Nov 27 12:08... [notice] Opening Socks listener on 127.0.0.1:9050
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Nov 27 12:08... [notice] Opening Socks listener on 127.0.0.1:9100
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 127.0.0.1:9100
Nov 27 12:08... [notice] Opening Socks listener on 127.0.0.1:9101
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 127.0.0.1:9101
Nov 27 12:08... [notice] Opening Socks listener on 127.0.0.1:9102
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 127.0.0.1:9102
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9169
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9169
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9170
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9170
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9171
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9171
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9172
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9172
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9173
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9173
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9174
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9174
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9175
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9175
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9176
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9176
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9177
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9177
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9178
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9178
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9179
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9179
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9180
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9180
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9181
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9181
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9182
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9182
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9183
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9183
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9184
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9184
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9185
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9185
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9186
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9186
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9187
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9187
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9188
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9188
Nov 27 12:08... [notice] Opening Socks listener on 10.137.0.9:9189
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on 10.137.0.9:9189
Nov 27 12:08... [notice] Opening DNS listener on 127.0.0.1:5400
Nov 27 12:08... [notice] Opened DNS listener connection (ready) on 127.0.0.1:5400
Nov 27 12:08... [notice] Opening DNS listener on 10.137.0.9:5300
Nov 27 12:08... [notice] Opened DNS listener connection (ready) on 10.137.0.9:5300
Nov 27 12:08... [notice] Opening Transparent pf/netfilter listener on 127.0.0.1:9041
Nov 27 12:08... [notice] Opened Transparent pf/netfilter listener connection (ready) on 127.0.0.1:9041
Nov 27 12:08... [notice] Opening Transparent pf/netfilter listener on 10.137.0.9:9040
Nov 27 12:08... [notice] Opened Transparent pf/netfilter listener connection (ready) on 10.137.0.9:9040
Nov 27 12:08... [notice] Opening HTTP tunnel listener on 127.0.0.1:9190
Nov 27 12:08... [notice] Opened HTTP tunnel listener connection (ready) on 127.0.0.1:9190
Nov 27 12:08... [notice] Opening HTTP tunnel listener on 127.0.0.1:9191
Nov 27 12:08... [notice] Opened HTTP tunnel listener connection (ready) on 127.0.0.1:9191
Nov 27 12:08... [notice] Opening HTTP tunnel listener on 127.0.0.1:9192
Nov 27 12:08... [notice] Opened HTTP tunnel listener connection (ready) on 127.0.0.1:9192
Nov 27 12:08... [notice] Opening HTTP tunnel listener on 127.0.0.1:9193
Nov 27 12:08... [notice] Opened HTTP tunnel listener connection (ready) on 127.0.0.1:9193
Nov 27 12:08... [notice] Opening HTTP tunnel listener on 127.0.0.1:9194
Nov 27 12:08... [notice] Opened HTTP tunnel listener connection (ready) on 127.0.0.1:9194
Nov 27 12:08... [notice] Opening HTTP tunnel listener on 127.0.0.1:9195
Nov 27 12:08... [notice] Opened HTTP tunnel listener connection (ready) on 127.0.0.1:9195
Nov 27 12:08... [notice] Opening HTTP tunnel listener on 127.0.0.1:9196
Nov 27 12:08... [notice] Opened HTTP tunnel listener connection (ready) on 127.0.0.1:9196
Nov 27 12:08... [notice] Opening HTTP tunnel listener on 127.0.0.1:9197
Nov 27 12:08... [notice] Opened HTTP tunnel listener connection (ready) on 127.0.0.1:9197
Nov 27 12:08... [notice] Opening HTTP tunnel listener on 10.137.0.9:9227
Nov 27 12:08... [notice] Opened HTTP tunnel listener connection (ready) on 10.137.0.9:9227
Nov 27 12:08... [notice] Opening HTTP tunnel listener on 10.137.0.9:9228
Nov 27 12:08... [notice] Opened HTTP tunnel listener connection (ready) on 10.137.0.9:9228
Nov 27 12:08... [notice] Opening HTTP tunnel listener on 10.137.0.9:9229
Nov 27 12:08... [notice] Opened HTTP tunnel listener connection (ready) on 10.137.0.9:9229
Nov 27 12:08... [notice] Opening Control listener on 127.0.0.1:9052
Nov 27 12:08... [notice] Opened Control listener connection (ready) on 127.0.0.1:9052
Nov 27 12:08... [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Nov 27 12:08... [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Nov 27 12:08... [notice] Bootstrapped 0% (starting): Starting
Nov 27 12:08... [notice] Starting with guard context "default"
Nov 27 12:08... [notice] Signaled readiness to systemd
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Received reload signal (hup). Reloading config and resetting internal state.
Nov 27 12:08... [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Nov 27 12:08... [notice] Read configuration file "/etc/tor/torrc".
Nov 27 12:08... [notice] Processing configuration path "/etc/torrc.d/*.conf" at recursion level 1.
Nov 27 12:08... [notice] Including configuration file "/etc/torrc.d/60_network.conf".
Nov 27 12:08... [notice] Including configuration file "/etc/torrc.d/65_gateway.conf".
Nov 27 12:08... [notice] Including configuration file "/etc/torrc.d/65_leak_tests.conf".
Nov 27 12:08... [notice] Including configuration file "/etc/torrc.d/70_workstation.conf".
Nov 27 12:08... [notice] Processing configuration path "/usr/share/tor/tor-service-defaults-torrc.anondist" at recursion level 2.
Nov 27 12:08... [notice] Including configuration file "/usr/share/tor/tor-service-defaults-torrc.anondist".
Nov 27 12:08... [notice] Including configuration file "/etc/torrc.d/95_whonix.conf".
Nov 27 12:08... [notice] Processing configuration path "/usr/local/etc/torrc.d/*.conf" at recursion level 2.
Nov 27 12:08... [notice] Including configuration file "/usr/local/etc/torrc.d/40_tor_control_panel.conf".
Nov 27 12:08... [notice] Including configuration file "/usr/local/etc/torrc.d/50_user.conf".
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:5300' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9040' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9050' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9100' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9101' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9102' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9103' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9185' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9186' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9187' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9188' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] You configured a non-loopback address '10.137.0.9:9189' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 27 12:08... [notice] Opening Socks listener on /run/tor/socks
Nov 27 12:08... [notice] Opened Socks listener connection (ready) on /run/tor/socks
Nov 27 12:08... [notice] Opening Control listener on /run/tor/control
Nov 27 12:08... [notice] Opened Control listener connection (ready) on /run/tor/control
Nov 27 12:08... [notice] Tor 0.4.8.12 opening log file.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Nov 27 12:08... [notice] New control connection opened.
Nov 27 12:08... [notice] New control connection opened.
Nov 27 12:08... [notice] New control connection opened.
Nov 27 12:08... [notice] New control connection opened.
Nov 27 12:08... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
Nov 27 12:09... [notice] New control connection opened.
...

(i trimmed the logs as they contain a lot of duplicated lines)

I deleted all whonix templates and reinstall them using the template manager, this did not solve anything, but at least I can confirm it’s a fresh install and I changed nothing on it.

Any idea?

tanky0u · November 27, 2024, 12:16pm

Perhaps dumb questions, but:

are you on a network with a captive portal?
have you tried Tor Control Panel → Restart Tor?

solene · November 27, 2024, 12:22pm

Sorry, I forgot to give these information.

I tried multiple times to stop / restart tor, I also tried to start it manually to try to get debug logs, without success.

The netvm for sys-whonix is working perfectly fine with all other qubes. There is no tor filtering done too as tor browser works fine in any other qube.

tanky0u · November 27, 2024, 12:26pm

After this forum, also make sure to ask your problem in https://forums.whonix.org

alimirjamali · November 27, 2024, 12:29pm

That line about non-loopback address is kinda odd. Are you sure you have no file at /rw/usrlocal/etc/torrc.d in your sys-whonix?

solene · November 27, 2024, 12:48pm

[gateway user ~]% cat /rw/usrlocal/etc/torrc.d/*                        
# This file is generated by and should ONLY be used by tor-control-panel.
# User configuration should go to /usr/local/etc/torrc.d/50_user.conf, not here. Because:
#    1. This file can be easily overwritten by tor-control-panel.
#    2. Even a single character change in this file may cause error.
# However, deleting this file will be fine since a new plain file will be generated the next time you run tor-control-panel.# /usr/local/etc/torrc.d/50_user.conf
DisableNetwork 0
# Tor user specific configuration file
#
# Add user modifications below this line:
############################################

rustybird · November 27, 2024, 1:36pm

Clearing the ‘private’ volume of sys-whonix to erase all of its data (such as tor state) should help:

$ qvm-shutdown --wait sys-whonix
$ qubesd-query --empty --fail dom0 admin.vm.volume.Clear sys-whonix private

solene · November 27, 2024, 1:56pm

After doing so, I restarted sys-whonix and got this popup

ERROR: check network interfaces Result: network interface eth0 not up!

Recommendation:
Try to manually start Whonix networking. 
sudo systemctl restart networking 
Or reboot.

Debugging information:
Command
sudo --non-interactive cat /sys/class/net/eth0/carrier
failed.

If this error happens only during upgrading or is transient this error can be safely ignored. 
If you know what you are doing, feel free to disable this check. Create a file /etc/systemcheck.d/50_user.conf and add: 
systemcheck_skip_functions+=" check_network_interfaces "

ip a output

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:5e:6c:00 brd ff:ff:ff:ff:ff:ff
    inet 10.137.0.9/32 scope global eth0
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether f6:ef:80:41:25:95 brd ff:ff:ff:ff:ff:ff
    inet 10.137.0.9/32 brd 10.255.255.255 scope global eth1
       valid_lft forever preferred_lft forever

solene · November 27, 2024, 3:30pm

Following the Uninstall/Purge guide and reinstall properly did not fix anything, there is still eth0 down by default too.

Trying sudo ifconfig eth0 up does not solve anything either.

solene · November 27, 2024, 4:02pm

do people have eth0 and eth1 in sys-whonix, are they both up?

alimirjamali · November 27, 2024, 4:08pm

solene · November 27, 2024, 4:11pm

what’s the output of ip r ? It’s empty for me (which is certainly the reason it’s not working!)

alimirjamali · November 27, 2024, 4:14pm

That should be the reason. Routing is fine on my sys-whonix via sys-firewall.

routing

solene · November 27, 2024, 4:20pm

After adding the default route manually, tor connects fine.

The problem now is why sys-whonix starts with eth0 down and without a default route?

alimirjamali · November 27, 2024, 4:21pm

What is its netvm preference?

solene · November 27, 2024, 4:42pm

It’s sys-firewall now (oops, I didn’t want to connect to it, but it got reset after the reinstall ), I tried multiple VPN qubes before.

alimirjamali · November 27, 2024, 4:44pm

My personal template for sys-whonix is somewhat questionable. It has been always upgraded in place instead of installing fresh ones. Maybe it is better to collect more data from the others.

solene · November 27, 2024, 4:44pm

Changing the netvm while showing the logs gives this.




Nov 27 16:43:19 host systemd-udevd[308]: Configuration file /usr/lib/udev/rules.d/80-qubes-usb-reset.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
Nov 27 16:43:19 host kernel: xen_netfront: backend supports XDP headroom
Nov 27 16:43:19 host kernel: vif vif-0: bouncing transmitted data to zeroed pages
Nov 27 16:43:19 host systemd[1]: Starting qubes-network-uplink@eth0.service - Qubes network uplink (eth0) setup...
Nov 27 16:43:19 host setup-ip[31173]: Error: ipv6: IPv6 is disabled on this device.
Nov 27 16:43:19 host systemd[1]: qubes-network-uplink@eth0.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 27 16:43:19 host systemd[1]: qubes-network-uplink@eth0.service: Failed with result 'exit-code'.
Nov 27 16:43:19 host systemd[1]: Failed to start qubes-network-uplink@eth0.service - Qubes network uplink (eth0) setup.
Nov 27 16:43:19 host (udev-worker)[31138]: eth0: Process '/usr/bin/systemctl restart --job-mode=replace qubes-network-uplink@eth0.service' failed with exit code 1.

I enabled ipv6 on sys-net a few days ago and removed it with qvm-features sys-net ipv6 0, maybe I did it wrong?

solene · November 27, 2024, 7:04pm

Mystery solved! There is a Qubes OS bug

Setting qvm-features sys-net ipv6 1 creates troubles in sys-whonix like eth0 not being up, and not having route.

However, setting qvm-features sys-net ipv6 0 does solve nothing, one must use qvm-features --unset sys-net ipv6 to really revert the ipv6 setting.

qubes_username · November 29, 2024, 4:05am

I had the same problem and stuff in this thread fixed it. Here are the exact commands in the exact order, for others who had trouble digesting this:

In dom0 terminal:

$ qvm-shutdown --wait sys-whonix
$ qubesd-query --empty --fail dom0 admin.vm.volume.Clear sys-whonix private
$ qvm-features --unset sys-net ipv6

That got Tor working. I then got a scary looking pop-up that told me to update whonix-gateway-17. I did that, now everything works fine.