This started with my BitWarden going showing an error and going offline showing the following error.
“An error has occurred
NetworkError when attempting to fetch resource.”
When I checked, I could not access my My Start9 or BitWarden on the .onion…I could however access Start9 on my network.
I have: Checked for updates, Rebooted and Rebuilt. I can attach Tor Log, Kernal Log, Screenshots of .onion not working, error etc.
Does the tor log indicate any problem?
It appears so. See below.
Here’s a section of the log I downloaded.
2025-01-06T19:21:39-08:00 Configuration was valid
2025-01-06T19:21:40-08:00 Jan 07 03:21:40.036 [notice] Tor 0.4.8.9 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
2025-01-06T19:21:40-08:00 Jan 07 03:21:40.038 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
2025-01-06T19:21:40-08:00 Jan 07 03:21:40.038 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
2025-01-06T19:21:40-08:00 Jan 07 03:21:40.039 [notice] Read configuration file “/etc/tor/torrc”.
2025-01-06T19:21:40-08:00 Jan 07 03:21:40.044 [warn] You specified a public address ‘0.0.0.0:9050’ for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don’t allow this unless you have a good reason.
2025-01-06T19:21:40-08:00 Jan 07 03:21:40.045 [notice] Opening Socks listener on 0.0.0.0:9050
2025-01-06T19:21:40-08:00 Jan 07 03:21:40.045 [notice] Opened Socks listener connection (ready) on 0.0.0.0:9050
2025-01-06T19:21:40-08:00 Jan 07 03:21:40.045 [notice] Opening Control listener on 127.0.0.1:9051
2025-01-06T19:21:40-08:00 Jan 07 03:21:40.045 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
2025-01-06T19:21:40-08:00 We compiled with OpenSSL 300000b0: OpenSSL 3.0.11 19 Sep 2023 and we are running with OpenSSL 300000b0: 3.0.11. These two versions should be binary compatible.
2025-01-06T19:21:40-08:00 Tor 0.4.8.9 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
2025-01-06T19:21:40-08:00 Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
2025-01-06T19:21:40-08:00 Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
2025-01-06T19:21:40-08:00 Read configuration file “/etc/tor/torrc”.
2025-01-06T19:21:40-08:00 You specified a public address ‘0.0.0.0:9050’ for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don’t allow this unless you have a good reason.
2025-01-06T19:21:40-08:00 Opening Socks listener on 0.0.0.0:9050
2025-01-06T19:21:40-08:00 Opened Socks listener connection (ready) on 0.0.0.0:9050
2025-01-06T19:21:40-08:00 Opening Control listener on 127.0.0.1:9051
2025-01-06T19:21:40-08:00 Opened Control listener connection (ready) on 127.0.0.1:9051
2025-01-06T19:21:40-08:00 Parsing GEOIP IPv4 file /usr/share/tor/geoip.
2025-01-06T19:21:40-08:00 Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
2025-01-06T19:21:41-08:00 Bootstrapped 0% (starting): Starting
2025-01-06T19:21:41-08:00 Started tor@default.service - Anonymizing overlay network for TCP.
2025-01-06T19:21:41-08:00 Starting with guard context “default”
2025-01-06T19:21:41-08:00 Signaled readiness to systemd
2025-01-06T19:21:41-08:00 New control connection opened from 127.0.0.1.
2025-01-06T19:21:42-08:00 Opening Control listener on /run/tor/control
2025-01-06T19:21:42-08:00 Opened Control listener connection (ready) on /run/tor/control
2025-01-06T19:21:42-08:00 Bootstrapped 5% (conn): Connecting to a relay
2025-01-06T19:21:42-08:00 Bootstrapped 10% (conn_done): Connected to a relay
2025-01-06T19:21:42-08:00 Bootstrapped 14% (handshake): Handshaking with a relay
2025-01-06T19:21:42-08:00 Bootstrapped 15% (handshake_done): Handshake with a relay done
2025-01-06T19:21:42-08:00 Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
2025-01-06T19:21:42-08:00 Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
2025-01-06T19:21:42-08:00 Bootstrapped 30% (loading_status): Loading networkstatus consensus
2025-01-06T19:21:43-08:00 I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
2025-01-06T19:21:44-08:00 Bootstrapped 40% (loading_keys): Loading authority key certs
2025-01-06T19:21:44-08:00 The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
2025-01-06T19:21:44-08:00 Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
2025-01-06T19:21:44-08:00 I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7988, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
2025-01-06T19:21:45-08:00 Bootstrapped 50% (loading_descriptors): Loading relay descriptors
2025-01-06T19:21:47-08:00 The current consensus contains exit nodes. Tor can build exit and internal paths.
2025-01-06T19:21:51-08:00 Bootstrapped 55% (loading_descriptors): Loading relay descriptors
2025-01-06T19:21:56-08:00 Bootstrapped 60% (loading_descriptors): Loading relay descriptors
2025-01-06T19:21:57-08:00 Bootstrapped 67% (loading_descriptors): Loading relay descriptors
2025-01-06T19:21:57-08:00 Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
2025-01-06T19:21:57-08:00 Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
2025-01-06T19:21:57-08:00 Bootstrapped 95% (circuit_create): Establishing a Tor circuit
2025-01-06T19:21:58-08:00 Bootstrapped 100% (done): Done
2025-01-06T19:22:10-08:00 Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 108 buildtimes.
2025-01-06T19:37:45-08:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
The tor logs you sent do show that the connection bootstrapped to 100%, keep an eye on the logs and make sure it is not failing and constantly retrying to connect.
If that is what you see, you can reset the tor connection by going to your server’s UI:
System → Manage → Experimental Features → Reset Tor
Try to do this without selecting “Wipe State” first.
You can then check in the Tor logs if the connection is bootstrapping all the way up to 100% and remaining stable.
If it still gives you trouble, you can try selecting the option to “Wipe State”.
Tor in notorious for not being the most reliable. After resetting it a couple times, you might find a stable connection that allows you use it with no trouble.
Your Tor log looks good. After following the instructions provided by @Alvaro , verify that your device can connect to your StartOS server at it’s .onion address, and we’ll go from there.
Completed steps. I cannot connect via the web. Only on LAN.
What OS is the device you are using currently?
Windows 11 now, was windows 10 when it started. Does not work on Android phone either.
Is this Windows 11 PC a device that needs to access Vaultwarden, or other service remotely?
Yes, It’s the primary way we access it. In fact we don’t use it on phones.
Are you able to access your server’s admin dash, using your server’s adjective-noun.local address with a browser?
Yes I can access on the LAN on the Windows 11 computer with Mozillo.
Great! Try it from Edge. If it connects with no warning, you’ll just need to go through the Tor setup here:
https://docs.start9.com/0.3.5.x/device-guides/windows/tor-windows#tor-windows
And then the Bitwarden setup here:
https://docs.start9.com/0.3.5.x/service-guides/vaultwarden/bitwarden-client-setup
I tried Edge and no joy. See this notation on the Edge failure. DNS_PROBE_FINISHED_NXDOMAIN
Okay, you probably made an exception in Firefox. No problem. You just need to start here:
https://docs.start9.com/0.3.5.x/user-manual/trust-ca
Then
https://docs.start9.com/0.3.5.x/user-manual/connecting-lan
I’d recommend for you to get the connect local working first, and then move on to Tor:
My apologies. I’m in on the LAN, I’m not via the web.
I understand. I think we’re on the same page. Proceed as I recommended above.
Ok, I tried to re-upload my root CA and it does not seem to be “taking”. Meaning, I’m not seeing it in the folder after I upload.
What’s wrong?
I even tried renaming it because it was not named as shown. And then re-uploading, nothing…
An aside. I put the Tor browser on my Win. computer a long time ago and for giggles I fired it up and VOILA! I can access through that.
This begs the question. Why do both Edge and Mozillo have an issue?
This doesn’t accomplish your purpose. But what it does tell us is that your server is functioning properly, and properly connected to Tor. The trouble you’re having is with getting Windows 11 to trust your root CA. To resolve this, try re-reading the procedure from start to finish, then go through it again step by step, slowly and meticulously. If you encounter any discrepancies or unexpected results, stop and let us know which specific step you’re having trouble with, so we can provide targeted assistance.
