Linux firefox user here. The extension has worked for me until the past month. I’ve been trying to reset the connection to from my server to the extension, and now it won’t let me paste tor address into the extension as I have previously done. I can only access my passwords by LAN now.
Any thoughts would be hugely appreciated.
Hi, has anything changed in the past month with your setup by any chance? Sometimes something like an update can potentially break a previous connection.
I’d like you to check the Tor Logs of your server to see if there is any information in there that could lead us to the cause of this.
You can reach it by going to System -> Tor Logs.
You’re looking for it to say Bootstrapped 100% (done): Done
If you haven’t already, you might want to take a look at the Linux section at the bottom of This Guide as there are specific instructions on how to go about the client setup that might need to be repeated
Thanks for your replies Okin. The only thing that has changed is a new router I installed AFAIK.
In regard to the Tor logs, it definitely doesn’t read as you suggested.
2025-12-01T20:28:17+13: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-12-01T20:28:17+13:00 Opening Socks listener on 0.0.0.0:9050
2025-12-01T20:28:17+13:00 Opened Socks listener connection (ready) on 0.0.0.0:9050
2025-12-01T20:28:17+13:00 Opening Control listener on 127.0.0.1:9051
2025-12-01T20:28:17+13:00 Opened Control listener connection (ready) on 127.0.0.1:9051
2025-12-01T20:28:17+13:00 Parsing GEOIP IPv4 file /usr/share/tor/geoip.
2025-12-01T20:28:17+13:00 Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
2025-12-01T20:28:17+13:00 Bootstrapped 0% (starting): Starting
2025-12-01T20:28:17+13:00 Starting with guard context “default”
2025-12-01T20:28:17+13:00 Signaled readiness to systemd
2025-12-01T20:28:17+13:00 Started tor@default.service - Anonymizing overlay network for TCP.
2025-12-01T20:28:17+13:00 New control connection opened from 127.0.0.1.
2025-12-01T20:28:18+13:00 Opening Control listener on /run/tor/control
2025-12-01T20:28:18+13:00 Opened Control listener connection (ready) on /run/tor/control
2025-12-01T20:28:18+13:00 Bootstrapped 5% (conn): Connecting to a relay
2025-12-01T20:28:19+13:00 Bootstrapped 10% (conn_done): Connected to a relay
2025-12-01T20:28:20+13:00 Bootstrapped 14% (handshake): Handshaking with a relay
2025-12-01T20:28:23+13:00 Bootstrapped 15% (handshake_done): Handshake with a relay done
2025-12-01T20:28:23+13:00 Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
2025-12-01T20:28:23+13:00 Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
2025-12-01T20:28:24+13:00 Bootstrapped 30% (loading_status): Loading networkstatus consensus
2025-12-01T20:28:27+13:00 I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
2025-12-01T20:28:27+13:00 Bootstrapped 40% (loading_keys): Loading authority key certs
2025-12-01T20:28:28+13:00 The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
2025-12-01T20:28:28+13:00 Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
2025-12-01T20:28:28+13:00 I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/9112, 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-12-01T20:28:28+13:00 I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/9112, 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-12-01T20:28:30+13:00 Bootstrapped 50% (loading_descriptors): Loading relay descriptors
2025-12-01T20:28:33+13:00 The current consensus contains exit nodes. Tor can build exit and internal paths.
2025-12-01T20:28:34+13:00 Bootstrapped 55% (loading_descriptors): Loading relay descriptors
2025-12-01T20:28:46+13:00 Bootstrapped 62% (loading_descriptors): Loading relay descriptors
2025-12-01T20:28:47+13:00 Bootstrapped 69% (loading_descriptors): Loading relay descriptors
2025-12-01T20:28:47+13:00 Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
2025-12-01T20:28:47+13:00 Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
2025-12-01T20:28:47+13:00 Bootstrapped 95% (circuit_create): Establishing a Tor circuit
2025-12-01T20:28:49+13:00 Bootstrapped 100% (done): Done
2025-12-01T20:29:01+13:00 Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 193 buildtimes.
2025-12-01T20:54:44+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-01T21:16:36+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-01T21:25:00+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-01T21:25:51+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-01T21:41:12+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-01T21:49:29+13:00 Received http status code 404 (“Not found”) from server 185.189.115.54:9002 while fetching “/tor/keys/fp/14C131DFC5C6F93646BE72FA1401C02A8DF2E8B4”.
2025-12-01T22:36:47+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-01T22:37:33+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-01T22:37:52+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-01T23:05:58+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-01T23:06:25+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-01T23:50:30+13:00 Received http status code 404 (“Not found”) from server 185.189.115.54:9002 while fetching “/tor/keys/fp/14C131DFC5C6F93646BE72FA1401C02A8DF2E8B4”.
2025-12-02T00:39:37+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T00:43:51+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T00:45:54+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T00:50:30+13:00 Received http status code 404 (“Not found”) from server 185.189.115.54:9002 while fetching “/tor/keys/fp/14C131DFC5C6F93646BE72FA1401C02A8DF2E8B4”.
2025-12-02T01:34:02+13:00 Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes.
2025-12-02T01:53:40+13:00 Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 115 buildtimes.
2025-12-02T02:19:46+13:00 Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 121 buildtimes.
2025-12-02T02:27:59+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T02:28:18+13:00 Heartbeat: Tor’s uptime is 6:00 hours, with 121 circuits open. I’ve sent 36.37 MB and received 34.14 MB. I’ve received 764 connections on IPv4 and 0 on IPv6. I’ve made 725 connections with IPv4 and 0 with IPv6.
2025-12-02T02:28:18+13:00 While bootstrapping, fetched this many bytes: 698480 (consensus network-status fetch); 12293 (authority cert fetch); 13572907 (microdescriptor fetch)
2025-12-02T02:28:18+13:00 While not bootstrapping, fetched this many bytes: 35908 (consensus network-status fetch); 189 (authority cert fetch); 162506 (microdescriptor fetch)
2025-12-02T02:28:18+13:00 Average packaged cell fullness: 73.327%. TLS write overhead: 3%
2025-12-02T02:28:18+13:00 Heartbeat: Our onion services received 102 v3 INTRODUCE2 cells and attempted to launch 105 rendezvous circuits.
2025-12-02T02:33:30+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T02:47:32+13:00 Received http status code 404 (“Not found”) from server 185.189.115.54:9002 while fetching “/tor/keys/fp/14C131DFC5C6F93646BE72FA1401C02A8DF2E8B4”.
2025-12-02T02:47:41+13:00 Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 250 buildtimes.
2025-12-02T02:55:44+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T04:19:13+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T04:19:48+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T04:36:01+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T04:38:13+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T04:44:57+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T05:51:46+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
2025-12-02T06:19:57+13:00 Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
I’ve flicked through the guide you linked, and I think I’ve got all that working!
Cheers!
Hi Pontoon, this is a known bug and we have to wait for an update to the Bitwarden StartOS package for a fix. See the github issue here: [bug]: Latest Bitwarden Clients Force Secure Connections · Issue #58 · Start9Labs/vaultwarden-startos · GitHub
In the meantime, user Zighy reports this as a workaround on Android:
Just an update on how I solved this issue on my android device using the Bitwarden app password manager:
- Configure Orbot to give tor VPN access to Bitwarden application
- I used https://{vaultwarden_tor_url}.onion as self-hosted URL connection
- On StartOS I downloaded the Root CA certificate from the “System” menu
- I installed the certificate as a user trusted CA certificate on my android device (Settings → Security → Encryption & credentials → Install a certificate)
Now I can login again to my self-hosted server
You guys are legends, I followed Zighy’s guide to get my phone set up, and will use LAN in the meantime for my PC. Cheers!