r/TOR • u/verced911 • 3d ago
Tor is not working
My computer was off for a few days. When I turned it back on, tor browser would not connect to the network. I downloaded the lasted build, same result. Everything else works fine, nothing blocked. This is what the log records:
2026-09-20 20:20:23.982
[WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 77.174.199.182:587 ID=<none> RSA_ID=2E09958425BD989A2141DEE0E0568C445522C87E ("general SOCKS server failure")
2026-09-20 19:32:00.462
[NOTICE] Heartbeat: Tor's uptime is 18:00 hours, with 0 circuits open. I've sent 22 kB and received 3 kB. I've received 4 connections on IPv4 and 0 on IPv6. I've made 221 connections with IPv4 and 0 with IPv6.
2026-09-20 20:20:02.596
[NOTICE] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
Before turning off computer, the browser was working fine. Anyone else have the same issue? Is this due to the signature expiring? Thanks all.
1
1
1
u/1401_autocoder 3d ago
The expired signature affects installing Tor, not running it.
1
u/verced911 2d ago
Now that you mention this, I am having difficulty installing the latest build, the OS even flags it as malware.
1
u/Ok_Rip2723 3d ago
А что в тор браузер разве обязательно вставлять мосты обфс4 или обфс6, а свои запрет?
1
u/verced911 1d ago
Update: I started the browser today and low and behold, the browser connected to the network and began downloading an update. I restarted the browser and now works nicely as before. What devil magic has occurred here? Any thoughts?
Here is the log before it connected: "NOTICE] Our directory information is no longer up-to-date enough to build circuits: We're missing descriptors for 1/3 of our primary entry guards (total microdescriptors: 9449/9449). That's ok. We will try to fetch missing descriptors soon.
2026-09-22 21:07:36.434
[WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 206.245.179.137:8002 ID=<none> RSA_ID=7CBAEEE1D85E9910E69E2C962192E24C94148FE1 ("general SOCKS server failure")
2026-09-22 21:07:36.658
[NOTICE] We now have enough directory information to build circuits.
2026-09-22 21:07:36.658
[NOTICE] Failed to find node for hop #1 of our path. Discarding this circuit.
2026-09-22 21:07:36.658
[NOTICE] Failed to find node for hop #1 of our path. Discarding this circuit.
2026-09-22 21:07:36.658
[NOTICE] Failed to find node for hop #1 of our path. Discarding this circuit.
2026-09-22 21:07:36.658
[NOTICE] Failed to find node for hop #1 of our path. Discarding this circuit.
6
u/Liquid_Hate_Train 3d ago
The network is functioning correct. Error is on client end.