Topic starter 03/11/2026 9:37 a.m.
I tested Tor on eBlockerOS 3.2.3, 4.0.3 and two existing 4.1.0 test VMs on 3 November 2026.
After installing all offered updates, 3.2.3 (Tor 0.4.5.16) and 4.0.3 (Tor 0.4.7.16) both fail. The Tor service exits because the network requires Desc=3 Microdesc=3, which these versions do not support. On both systems, the dashboard nevertheless shows “Connected.”
The two eBlockerOS 4.1.0 VMs have Tor 0.4.9.11. Both reached 100% bootstrap, and an HTTPS request to torstatus.greensec.de through their Tor SOCKS socket returned HTTP 200. I have not yet tested traffic from a separate device routed through eBlocker.
The reproduction steps and the 4.1.0 follow-up are in GitHub issue #460.
Best regards
Sven