Dear community,
Since the update at the end of January 24 I have had the following problem: Normally the Eblocker was accessible in my network at x.x.x.116. The FritzBox is located at x.x.x.1. After the update, the FritzBox could no longer be reached because the eBlocker was now suddenly running on .1. At the same time, adverts were no longer blocked, regardless of the device. I first carried out a reset and then set the IP address of the eBlocker back to .116. No success. Then I created a completely new security certificate and installed it on all devices. No success. Since then, the eBlocker has been running and regularly downloads its updates, but it is not working.
Can someone from the community perhaps give me a tip on what else I could try?
Best regards, Torsten
@torsten-b Please share all info asked here: https://eblocker.org/community/announcements/before-posting-here-please-read/#post-117
Just for your background: In case you are using Automatic Network Mode, eBlocker will appear with two IP addresses in the router's overview. With it's real address and with the IP address of the router (.1 in your case). This is normal and I fear your observation that the IP has changed is incorrect. See here: https://eblocker.org/en/docs/my-router-is-showing-different-ip-addresses-for-the-eblocker/
I'm happy to dig to the real cause of trouble once you provide the info. And btw: I highly doubt your issue is related to the update at all. This is probably just a coincidence in time.
THX!
@random Thank you for answering!
Here we go:
Hardware you use for running eBlockerOS
RPi4 2 GB
eBlockerOS version as well as filter lists version
3.1.0, Filter: 2024-04-14-09-15-04
eBlocker network mode (auto, individual or expert)
expert (no IPv6)
eBlocker network settings (IP, mask, gateway)
IP: 192.168.16.115
mask: 255.255.255.0
gateway: 192.168.16.1
Which devices runs DHCP server? Router/external, eBlocker or client fixed IP?
Router
IPv6 disabled for client/network?
disabled
eBlocker DNS firewall settings
DNS firewall: on
DNS-Server: 192.168.16.1
Client network settings (IP, mask, DNS, gateway)
div. devices.
Whether eBlocker’s https integration is enabled for client
Client browser and OS version (i.e. FireFox 80.1 running on macOS 13.4)
div. browsers (f.e. Safari IpadOS 17, FireFox 124.0.2, Windows 10 64)
Additional non default Blockers enabled? (like DuckDuckGo, Consent-Blocker, custom lists etc.)
No.
HTTPS Auto Trust App enabled?
Yes.
Best regards, Torsten
@torsten-b If your router is the DHCP sever it will not set eBlocker as the gateway but the router's IP. Hence, all traffic is by-passing eBlocker. That's what you see in the Function Test you've shared.
For eBlocker to work eBlocker's IP needs to be set as gateway in all clients, so eBlockerOS gets all IP packets for inspection/filtering.
I'd suggest to enable eBlocker's DHCP and you gonna be fine. Please check the Setup Instruction for details.
THX!
@Random Thank you! After de-activating the DHCP of the FritzBox, the eBlocker is acting fine again. Only the eBlocker-bar is not visible on several websites. But that's okay.
I use an FTTH-Internet-port with 560 MB removed link I think the eBlocker cannot handle this speed, right?
Greetings, Torsten
Only the eBlocker-bar is not visible on several websites. But that's okay.
If the eBlocker icon is not shown this might be a sign that the eBlocker certificate is not install correctly in the client and/or browser. Please perform a Function Test. If it shows all green - all is good.
I use an FTTH-Internet-port with 560 MB removed link I think the eBlocker cannot handle this speed, right?
eBlockerOS is a piece of software that can handle any speed as long as the underlying hardware is capable of it. Running 560 Mbit/s inbound and outbound on a 1.000 Mbit/s interface wont fully fit... but you wont feel any difference with or without eBlockerOS on a Raspi 4 anyhow.
Nevertheless, there are PCs with 2.500 Mbit/s and higher interfaces capable of running eBlockerOS.
Just a last hint: As long as I can think, a factory reset was never necessary to fix issues. It's usually much easier - and I'm happy to help.
THX!