I’ve installed StartOS on as a VM in my TrueNAS scale machine. It was syncing the blockchain up to about 30%, when it suddenly stopped making progress. I tried many things to debug, and eventually deleted the OS and reinstalled from scratch, since it worked the first time. I continued to get the same behavior in the Tor logs, with the service getting to 5%, receiving some sort of interrupt, and restarting. I’ve spent hours on google to no avail. Since the configuration is relatively locked down, I’m wondering if I’ve hit on some corner case? Or is my ISP being naughty? Tor Browser seems to work fine on my PC.
systemd[1]: Starting tor@default.service - Anonymizing overlay network for TCP...
tor[10316]: Jul 11 23:53:52.359 [notice] Tor 0.4.7.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.>
tor[10316]: Jul 11 23:53:52.359 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https:/>
tor[10316]: Jul 11 23:53:52.359 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
tor[10316]: Jul 11 23:53:52.359 [notice] Read configuration file "/etc/tor/torrc".
tor[10316]: Configuration was valid
tor[10317]: Jul 11 23:53:52.438 [notice] Tor 0.4.7.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.>
tor[10317]: Jul 11 23:53:52.438 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https:/>
tor[10317]: Jul 11 23:53:52.438 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
tor[10317]: Jul 11 23:53:52.438 [notice] Read configuration file "/etc/tor/torrc".
tor[10317]: Jul 11 23:53:52.439 [warn] You specified a public address '0.0.0.0:9050' for SocksPort. Other people>
tor[10317]: Jul 11 23:53:52.439 [notice] Opening Socks listener on 0.0.0.0:9050
tor[10317]: Jul 11 23:53:52.439 [notice] Opened Socks listener connection (ready) on 0.0.0.0:9050
tor[10317]: Jul 11 23:53:52.439 [notice] Opening Control listener on 127.0.0.1:9051
tor[10317]: Jul 11 23:53:52.439 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Tor[10317]: We compiled with OpenSSL 101010ef: OpenSSL 1.1.1n 15 Mar 2022 and we are running with OpenSSL 10101>
Tor[10317]: Tor 0.4.7.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.>
Tor[10317]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/s>
Tor[10317]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Tor[10317]: Read configuration file "/etc/tor/torrc".
Tor[10317]: You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find>
Tor[10317]: Opening Socks listener on 0.0.0.0:9050
Tor[10317]: Opened Socks listener connection (ready) on 0.0.0.0:9050
Tor[10317]: Opening Control listener on 127.0.0.1:9051
Tor[10317]: Opened Control listener connection (ready) on 127.0.0.1:9051
Tor[10317]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Tor[10317]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Tor[10317]: Bootstrapped 0% (starting): Starting
systemd[1]: Started tor@default.service - Anonymizing overlay network for TCP.
Tor[10317]: Starting with guard context "default"
Tor[10317]: Signaled readiness to systemd\
Tor[10317]: New control connection opened from 127.0.0.1.
Tor[10317]: Opening Control listener on /run/tor/control
Tor[10317]: Opened Control listener connection (ready) on /run/tor/control
Tor[10317]: Bootstrapped 5% (conn): Connecting to a relay
Tor[10317]: Interrupt: exiting cleanly.
systemd[1]: Stopping tor@default.service - Anonymizing overlay network for TCP...
systemd[1]: tor@default.service: Deactivated successfully.
systemd[1]: Stopped tor@default.service - Anonymizing overlay network for TCP.
systemd[1]: Starting tor@default.service - Anonymizing overlay network for TCP...