eBlocker Open Source Forum - Recent Posts https://eblocker.org/community/ Discuss anything regarding eBlocker Open Source en-US Thu, 12 Nov 2026 23:13:57 +0000 wpForo 60 RE: DNS stopped working with active TOR network https://eblocker.org/community/bugs-features/dns-stopped-working-with-active-tor-network/#post-9096 Mon, 09 Nov 2026 16:49:04 +0000 @random looks good today!

thank you for your feedback and help!

 

Jox

]]> JoxWayne https://eblocker.org/community/bugs-features/dns-stopped-working-with-active-tor-network/#post-9096 RE: DNS stopped working with active TOR network https://eblocker.org/community/bugs-features/dns-stopped-working-with-active-tor-network/#post-9095 Mon, 09 Nov 2026 16:45:22 +0000 @joxwayne Tor is working again for me. Give it a try.

THX!

]]> Random https://eblocker.org/community/bugs-features/dns-stopped-working-with-active-tor-network/#post-9095 RE: eBlocker Randomly stops working and no longer responding (potential memory leak?) https://eblocker.org/community/bugs-features/eblocker-randomly-stops-working-and-no-longer-responding-potential-memory-leak/#post-9094 Fri, 06 Nov 2026 06:54:00 +0000 jimmysofat6864 https://eblocker.org/community/bugs-features/eblocker-randomly-stops-working-and-no-longer-responding-potential-memory-leak/#post-9094 RE: DNS stopped working with active TOR network https://eblocker.org/community/bugs-features/dns-stopped-working-with-active-tor-network/#post-9093 Thu, 05 Nov 2026 16:51:03 +0000 @joxwayne I think there was another configuration update yesterday in the Tor network.

The Tor client in eBlockerOS 4.0.3 seems to work again. After a reboot and waiting a few minutes I could get a Tor connection.

Yesterday there was an update in Tor according to the release notes:

Changes in version 0.4.9.16 - 2026-11-04

This is an emergency release affecting only directory authorities. It includes fixes to address the thundering herd caused by the new required protover values introduced in the previous release.

Major features (authority):

- Work around a bug where old clients did not, in fact, correctly handle unparseable microdescriptors in the way that we had hoped that they would. We triggered this bug by omitting TAP keys from microdescriptors. To solve this issue, instead of omitting TAP keys, we replace them with a dummy TAP key. (This is safe, because nothing has used TAP since v2 onion services.)

- New consensus method 38 added for this TAP dummy key.

- Revert back the required protover version for both "Desc" and "Microdesc" from 3 to 2 which is causing <= 0.4.8.x clients to exit(1).

]]> Boris https://eblocker.org/community/bugs-features/dns-stopped-working-with-active-tor-network/#post-9093 RE: DNS stopped working with active TOR network https://eblocker.org/community/bugs-features/dns-stopped-working-with-active-tor-network/#post-9092 Thu, 05 Nov 2026 14:36:32 +0000 JoxWayne https://eblocker.org/community/bugs-features/dns-stopped-working-with-active-tor-network/#post-9092 RE: DNS stopped working with active TOR network https://eblocker.org/community/bugs-features/dns-stopped-working-with-active-tor-network/#post-9091 Thu, 05 Nov 2026 08:41:48 +0000 @joxwayne Currently Tor does not work on eBlockerOS 3 and 4 due to a change in the Tor network. It now requires Tor version 0.4.9.15.

See also this thread: https://eblocker.org/community/bugs-features/tor-fails-on-eblockeros-3-2-3-and-4-0-3-required-desc3-microdesc3-protocols-unsupported-460/

I am currently working on an update.

]]> Boris https://eblocker.org/community/bugs-features/dns-stopped-working-with-active-tor-network/#post-9091 RE: eBlocker Randomly stops working and no longer responding (potential memory leak?) https://eblocker.org/community/bugs-features/eblocker-randomly-stops-working-and-no-longer-responding-potential-memory-leak/#post-9090 Thu, 05 Nov 2026 08:22:09 +0000 @jimmysofat6864 as this "solution" is not officially eBlocker supported, you may join the community discord server 

https://discord.gg/beBJE4ANA

best regards

]]> CalimerO https://eblocker.org/community/bugs-features/eblocker-randomly-stops-working-and-no-longer-responding-potential-memory-leak/#post-9090 RE: eBlocker Randomly stops working and no longer responding (potential memory leak?) https://eblocker.org/community/bugs-features/eblocker-randomly-stops-working-and-no-longer-responding-potential-memory-leak/#post-9089 Thu, 05 Nov 2026 08:16:01 +0000 @jimmysofat6864 In the past two weeks you have reported several "strange behaviors" of your eBlockerOS with issues that no one else has reported in the past 10 years. 

To me, this points to a "messed up" system.

If you are looking for a quick solution, I'd suggest to install a fresh eBlockerOS and start all over rather than trying to revive an obviously bogus setup.

THX!

]]> Random https://eblocker.org/community/bugs-features/eblocker-randomly-stops-working-and-no-longer-responding-potential-memory-leak/#post-9089 RE: eBlocker Randomly stops working and no longer responding (potential memory leak?) https://eblocker.org/community/bugs-features/eblocker-randomly-stops-working-and-no-longer-responding-potential-memory-leak/#post-9088 Wed, 04 Nov 2026 22:38:07 +0000 jimmysofat6864 https://eblocker.org/community/bugs-features/eblocker-randomly-stops-working-and-no-longer-responding-potential-memory-leak/#post-9088 RE: eBlocker Randomly stops working and no longer responding (potential memory leak?) https://eblocker.org/community/bugs-features/eblocker-randomly-stops-working-and-no-longer-responding-potential-memory-leak/#post-9087 Wed, 04 Nov 2026 22:35:27 +0000
I am using the x86-64 disk images from the thread " eBlockerOS 4 beta available for testing". 

I am not using a hypervisor I am running it on a Dell Wyse 5070 mini pc directly.]]> jimmysofat6864 https://eblocker.org/community/bugs-features/eblocker-randomly-stops-working-and-no-longer-responding-potential-memory-leak/#post-9087