Hello again,
the problem that my eBlocker is sometimes not reachable under its IP address after 5 minutes, sometimes after 30 minutes or sometimes after half a day, as I have now found out, only occurs in the following cases:
- after activation of eBlocker Mobile, or
- after activation of HTTPS support
(whether I activate one or the other or both).
I don't believe that my eBlocker hardware is defective because everything else is working fine.
Does anyone else have an idea how I can further isolate the cause of the error?
Could the diagnostic protocol help here?
I first have to remove the eblocker then from the Powersupply and start it again.
This is very annoying and frustrating.
If nobody has an idea anymore, I will probably buy a new Raspberry. But I am relatively sure that this will not help.
________________
raspberry Pi 3, eblocker OS Version: 2.5.6
client 1: iMAC, 27 ", middle 2015, OS X: 10.15.7, IPv6 disabled
client 2: ipad, IOS, I have no idea how to disable IPv6
Router: Fritzbox 6591 Cable, IPv6 disabled, but in the Network shows IPv6 Adresses for the Clients
eblocker: Network mode: Individuell
Supplement
Router: Fritzbox 6591 Cable, IPv6 disabled, but in the Network shows IPv6 Adresses for the Clients
In the fritzbox the network connections of my
raspberry Pi (eblocker) : shows 1 IPv6 adress
Client 1 (iMAC): shows no IPv6 adress
Client 2 (ipad): shows 4 IPv6 adresses
The Raspberry Pi "Portfreigabe" also contains an IPv6 address, but this differs from the IPv6 address of the Raspberry Pi under network connections. The Test of the "Portfreigabe" was successful.
I already have a domain from a Dynamic DNS provider for my dynamic IP address. (selfhost). the Test was successful.
The installation of the certificate in the keychain was successful, and also the import of the certificates in the Browsers (Safari, Firefox).
When the eblocker is not longer accessible traceroute (www. eblocker.com) shows the message: Unknown Host.
I noticed that sometimes it is not possible to connect via VPN from the dashboard or in the settings, even though the correct (UDP) settings are set in "IP Anonymization>VPN Network". A few hours later it suddenly works again. (NordVPN)
...if this could somehow be important
@zwergkralle THX for the good description!
I suspect some of your external DNS servers (probably manually set) are slow/unreachable some times.
For a test, next time Internet in unreachable: traceroute 1.1.1.1
Also: ping <eBlocker‘s IP> to check whether eBlocker is responding/alive still.
Traceroute will show if just the DNS is not resolving or even the routing fails.
If the routing works, you‘ll see the different router IPs the packets are taking to reach 1.1.1.1. Then switch DNS firewall off and make sure your router‘s IP address is set as DNS in eBlocker individual network mode. So, settings>network>individ. mode, DNS: <router‘s IP>
THX!
@Zwergkralle:
The behavior described could indicate a problem with the lease time of your router
@haseimschnee Not sure how you come to this conclusion.
If eBlocker in in Individual Network Mode (as @zwergkralle stated) the router‘s DHCP needs to be turned off. So there is not „lease time“ for eBlocker unless configuration is a complete nightmare 🧟♂️😉
Maybe a misunderstanding?
THX!
it seems to be one of my problems...I had to delete 2 DNS Servers that was unreachable.
A few minutes ago eBlocker was not accessible again and I have done the tests.
result of traceroute 1.1.1.1: I have seen the different router IPs the packets are taken to reach 1.1.1.1
result of Ping Test: 10 packets transmitted, 10 packets received, 0.0% packet loss
I'm not sure what to do now, bcause I don't understand this:
Then switch DNS firewall off and make sure your router‘s IP address is set as DNS in eBlocker individual network mode. So, settings>network>individ. mode, DNS: <router‘s IP>
After I have changed from the factory default settings to the individual network mode, this was my individual network settings (also after activating eblocker using as DNS Firewall):
IP-Adresse (eBlocker)
192.168.178.44
Netzwerkmaske
255......
Gateway/Router
192.168.178.1 (= my Fritzbox 6591 Cable)
Were these not the right settings?
What is the correct setting when I switch now DNS Firewall "off" in the eBlocker. There is not entry in individual mode with "DNS". Can you please explain this to me again?
Thx.
result of traceroute 1.1.1.1: I have seen the different router IPs the packets are taken to reach 1.1.1.1
Please post results of traceroute. (when error occurs, and also for comparison when everything works).
Regarding your question:
Just switch off eBlocker’s DNS firewall (settings>dns firewall> Switch to off). Never mind about the rest I‘ve posted. Unless you didn‘t touch the settings in Individual Network Mode you should be fine.
One last question: You state eBlocker is unreachable. I thought the Internet is unreachable and have misinterpreted your post. Could you please go more into detail here (i.e. which URLs are unreachable).
Above „ping“ shows at least your eBlocker is still alive...
In case you‘ve added individual blocker lists: switch all off besides eBlocker provided. Maybe it‘s a memory issue on Raspi 3?
THX!
result of traceroute when everything works:
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 72 byte packets
1 eblocker.box (192.168.178.44) 2.522 ms 2.315 ms 2.164 ms
2 10.8.2.1 (10.8.2.1) 60.919 ms 62.588 ms 62.022 ms
3 31.171.152.9 (31.171.152.9) 62.411 ms 61.867 ms 64.128 ms
4 80.78.69.229 (80.78.69.229) 62.443 ms 62.923 ms 59.997 ms
5 * * *
6 79.171.52.17 (79.171.52.17) 61.998 ms 61.860 ms 61.628 ms
7 ae7-100-ucr1.atm.cw.net (195.2.20.109) 76.128 ms 77.116 ms 74.910 ms
8 195.2.21.57 (195.2.21.57) 77.976 ms 75.892 ms 78.308 ms
9 ae-7.bar2.sofia2.level3.net (4.68.70.13) 102.673 ms 110.262 ms 105.461 ms
10 ae-1-3116.ear4.frankfurt1.level3.net (4.69.210.62) 104.287 ms 104.280 ms 102.182 ms
11 195.122.183.210 (195.122.183.210) 103.696 ms 101.167 ms 101.709 ms
12 one.one.one.one (1.1.1.1) 103.400 ms 102.843 ms 100.247 ms
result of tracerout from yesterday as the error occurs: see the Sreenshot
Sorry for the vague description:
If the error occurs, the URL of the eblocker is not accessible (192,68.178.44)
Then I'm not able to reach the eBlocker Settings, and also the eblocker Dashboard.
When I try to go to a searchengine like google or startpage, these url's are also unreachable.
Yesterday evening we looked apple TV, and suddenly the streaming stoped as the error occurs.
But now I have understand, that the Ping test shows, that the eblocker is ok. But I don't understand why I can't reach it.
As I began with the eblocker 2 or three weeks ago, I only used the DNS Servers 1.1.1.1 and 9.9.9.9
But then the Error occurs with this this configuration. So I tried to set more DNS Servers.At the moment I use 3 additional DNS.
How many DNS are recommended?
What do you think with "Maybe it‘s a memory issue on Raspi 3". Do you think its a Problem of the SD Card that I use or a Problem of the raspberrys RAM?
So you think it would be advisable to try a new Raspberry? Are there any recommendations as to which variant is best suited (Raspi 3 or 4, how much RAM...)
Thx.
I've tried two versions of the Pi 3+, each with a new SD card, but my problems haven't resolved.
After reading these many posts, I followed the recommendation and ordered Pi version 4 with 4 GB. I will definitely share my experience. An American wrote a comment on Amazon that this device is very good, but not for novices (Neulinge wörtlich) and he's right.
Hi @zwergkralle,
when I look at the ping times in your added PDF file, then it is obvious, that you have "network" issues.. They are too high.
When you power off the eBlocker, what are then the ping times?
My guess, they were at normal "highspeed" (under 100ms) and everything is working fine.
So I think, your Raspi3 is the troublemaker in that case.
Regards
Sven
I have tryed a traceroute under well working conditions how the picture shows. But if there is no access to the box, trace isn't possible. Conformation of your experiance!
I have a VPN profile running as an indication. The runtimes are very different for each test.
Gateway/Router
192.168.178.1 (= my Fritzbox 6591 Cable)
Are you sure this is the setting in eBlocker Individual Network mode?
Reason why I‘m asking: In none of your traceroutes the fritzbox‘s IP (as stated above) is shown.
Are you using a VPN configured in eBlocker for your client? Then your VPN provider has issues! Bad timings @calimerO commented are pointing to this as well.
Disable VPN in eBlocker. Post traceroute and we take it from there.
And please leave the VPN disabled - and I foresee eBlocker will be „accessible again“ - even after waiting for days...
BTW: which VPN provider are you using?
@willifly Are you also using VPN in eBlocker? Which VPN provider? As you both share the same experience I feel you might have the same problematic VPN provider causing this all...
THX!
yes, I`m sure, but i had chosen VPN.
Here the new results with disabled VPN. At the Moment the error doesn't occure:
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 72 byte packets
1 eblocker.box (192.168.178.44) 2.567 ms 2.979 ms 1.490 ms
2 fritz.box (192.168.178.1) 3.257 ms 3.040 ms 3.874 ms
3 ip5b4376fe.dynamic.kabel-deutschland.de (91.67.118.254) 12.741 ms 10.341 ms 10.064 ms
4 ip5886d82e.static.kabel-deutschland.de (88.134.216.46) 10.376 ms 10.367 ms 12.060 ms
5 ip5886c3f7.static.kabel-deutschland.de (88.134.195.247) 16.163 ms 17.643 ms 12.393 ms
6 145.254.3.82 (145.254.3.82) 15.001 ms 19.748 ms 18.859 ms
7 145.254.2.195 (145.254.2.195) 18.878 ms 17.618 ms 17.143 ms
8 de-cix-frankfurt.as13335.net (80.81.194.180) 128.140 ms 27.528 ms 27.907 ms
9 one.one.one.one (1.1.1.1) 15.210 ms 11.754 ms 11.524 ms
I'm using NordVPN with the UDP Settings.
I give feedback if the problem occurs with VPN switched off.
thx for Confirm my experience
here the Ping test with disabled VPN, when the error not occures:
„Ping“ wurde gestartet …
PING 192.168.178.44 (192.168.178.44): 56 data bytes
64 bytes from 192.168.178.44: icmp_seq=0 ttl=64 time=2.218 ms
64 bytes from 192.168.178.44: icmp_seq=1 ttl=64 time=0.797 ms
64 bytes from 192.168.178.44: icmp_seq=2 ttl=64 time=0.922 ms
64 bytes from 192.168.178.44: icmp_seq=3 ttl=64 time=0.728 ms
64 bytes from 192.168.178.44: icmp_seq=4 ttl=64 time=0.971 ms
64 bytes from 192.168.178.44: icmp_seq=5 ttl=64 time=0.955 ms
64 bytes from 192.168.178.44: icmp_seq=6 ttl=64 time=0.923 ms
64 bytes from 192.168.178.44: icmp_seq=7 ttl=64 time=0.976 ms
64 bytes from 192.168.178.44: icmp_seq=8 ttl=64 time=0.836 ms
64 bytes from 192.168.178.44: icmp_seq=9 ttl=64 time=0.935 ms
--- 192.168.178.44 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.728/1.026/2.218/0.405 ms
Thx@all
yes, I`m sure, but i had chosen VPN.
Wonderful! I interpret this as "Yes I always had VPN enabled when the error occurred".
Thanks for finally telling this, as it's CORE to your issues. I'll add this VPN question to the READ ME as this is super important. Please do not re-enable VPN to verify that this is the cause.
Could your please be clear about "access to eBlocker" or "access to Internet" failed when error occurred.
@willifly Same thing? VPN enabled? Provider? Then disable VPN as well and wait if problem occurs again (which I doubt)?
Yes, I'm sure means that 192.168.178.1 (= my Fritzbox 6591 Cable) is the correct setting in the individual network mode.
But: I'm not sure that VPN was always enabled when the error occurred.
so I observe and give feedback.
both failed. When error occured, I had no access to eblocker and was not able to have access to internet.
THx!
I’m sorry to give you this feedback:
A few seconds ago the error occured again, with VPN disabled:
Traceroute:
„Traceroute“ wurde gestartet …
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 72 byte packets
1 192.168.178.44 (192.168.178.44) 2.525 ms 2.288 ms 3.154 ms
2 192.168.178.1 (192.168.178.1) 3.255 ms 4.520 ms 4.097 ms
3 ip5b4376fe.dynamic.kabel-deutschland.de (91.67.118.254) 12.104 ms 15.478 ms 9.117 ms
4 ip5886d82e.static.kabel-deutschland.de (88.134.216.46) 11.564 ms 11.932 ms 9.248 ms
5 ip5886c3f7.static.kabel-deutschland.de (88.134.195.247) 21.004 ms 14.606 ms 11.140 ms
6 145.254.3.82 (145.254.3.82) 15.725 ms 18.003 ms 16.034 ms
7 145.254.2.195 (145.254.2.195) 16.985 ms * 20.225 ms
8 de-cix-frankfurt.as13335.net (80.81.194.180) 19.135 ms 18.508 ms 22.193 ms
9 one.one.one.one (1.1.1.1) 19.259 ms 14.961 ms 14.822 ms
Ping:
PING 192.168.178.44 (192.168.178.44): 56 data bytes
64 bytes from 192.168.178.44: icmp_seq=0 ttl=64 time=3.011 ms
64 bytes from 192.168.178.44: icmp_seq=1 ttl=64 time=1.051 ms
64 bytes from 192.168.178.44: icmp_seq=2 ttl=64 time=1.016 ms
64 bytes from 192.168.178.44: icmp_seq=3 ttl=64 time=0.906 ms
64 bytes from 192.168.178.44: icmp_seq=4 ttl=64 time=0.959 ms
64 bytes from 192.168.178.44: icmp_seq=5 ttl=64 time=0.921 ms
64 bytes from 192.168.178.44: icmp_seq=6 ttl=64 time=0.913 ms
64 bytes from 192.168.178.44: icmp_seq=7 ttl=64 time=0.841 ms
64 bytes from 192.168.178.44: icmp_seq=8 ttl=64 time=0.971 ms
64 bytes from 192.168.178.44: icmp_seq=9 ttl=64 time=0.790 ms
--- 192.168.178.44 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.790/1.138/3.011/0.629 ms
But at the moment I have no access to the eBlocker.
I had access to the Internet: That means I was able to send this posting and using DeepL.
I wasn't not able to open macwelt.de, startpage.com,...for example
And a few seconds later there was no more access to the Internet so I had to boot the eblocker again...
I had no access to eblocker
How did you try to access eBlocker (settings or dashboard, via IP or eblocker.box)? Exact URL please!
THX!
via IP:
http://192.168.178.44/settings/#!/login and .....#!/auth
http://192.168.178.44:3000/dashboard/#!/main
please note my additions in the last posting regarding internet access
it is possible that your PI3 have a problem 🤨
Is there a problem with the powersupply from your PI 🤔
We can only see this in the diagnostic file.
See the picture...
regards
PIO78
@pio78 @zwergkralle Please do not share diagnosis reports in the public forum as they may contain sensitive information. (see the READ ME too!)
If diag report is required, we‘ll ask for it and provide email contact.
In this particular case we‘ve nailed the issue down to VPN already. Either the VPN provider is unreliable or there is a bug with eBlocker’s VPN support which shows up on the long run only / or with some specific providers.
Unfortunately we have no access to VPN providers for testing (besides some free VPNs). But maybe affected users (@zwergkralle @willifly would like to contribute helping by sponsoring an account/access...)
THX!
Your problems are similar to mine, but more on that later. I used sd cards: Scandisk Ultra 16GB microSDHC memory card A1 ,Class 10, U1; Samsung memory card MicroSDXC 128GB EVO Plus UHS-I Grade 1 Class 10. The big one, because I no longer had any smaller ones. I ordered a new Pi 4 with 4 GB and a SanDisk Extreme micro SDHC A1 UHS-I U3 memory card 32GB. Because the question arose about the power supply unit, I use the original and recommended power supply units.
In summary, I have overcome my concerns about disabling DHCP in the router. I believed my problems came from the combination. So I chose the individual mode and followed the installation instructions. Everything went perfectly.
This morning my night mare. Nothing worked anymore (see pictures). Hard reset and everything worked again. There is no notice in the event report. That the box could not be reached after some hours (Internet was always available) I had more often with this configuration (Pi3 + automatic and individual mode). Yes, I use a VPN profile (CyberGhost for GER). Now it is the optimal config for my conditions (SW 2.5.6 and Fritzbox 7490), but after a certain time the box is "dead", at least it does not offer DHCP.
What information can I provide? My old problems have at least vanished into thin air.
thx, yesterday I ordered an Raspberry Pi 4,
I give a feedback after commissioning.
Now I generated a diagnostic file with my Raspi 3. Which E-Mail adress is the right one for mailing it.
Are you sure, that the VPN is the reason for the problem. I ask this because yesterday I gave the Feedback, that the error also occurs when VPN is disabled.
Next Weekend i try a different VPN File from NordVPN.
I also had sometimes the message "Die Stromzufuhr zum eblocker wurde unterbrochen", but much less often than the error occurred and the eblocker was not accessible.
My SD Card: xlyne Photo Professional microSDHC Class 10 1 Speicherkarte + Adapter 8GB, original Raspberry Power Suply 5,1V 3 A
Next Weekend I start a new trial with Raspi 4, 2GB RAM, SanDisk Ultra 32GB. I am curious about the result
Two hours later the same problem.........
I forgot which program I use to install the SD card: Etcher 1.5.58
And I checked the power supply: Output 2.5 A
I used with my iMac: balenaEtcher V 1.5.110
I used it a few minutes ago for install the Image to the new sd Card for the Raspi 4.
There was an Errormessage at the beginning. But it had no effects to the Image Writing.
Writing and Verifying was without errors.
To have a consistent environment:
- please refrain from using VPN on ALL clients (best: remove the VPN profiles completely).
- If error occurs, then do a traceroute to 1.1.1.1 from your client and please post screenshot of results.
- If you still can access eBlocker's interface, save a diagnosis report. If you can't, disconnect from power, count to 10, reconnect, then save diagnosis report.
- Send diagnosis report (ONLY after the error occurred, as said above!!) to support at eBlocker.org
Background: we have a couple of thousand eBlockers running nicely without any problem. But maybe there is a bug with some VPN providers / other VPN issues under very odd circumstances (which I'm guessing due to the traceroutes you've posted). That's why we need traceroutes without VPN (and I'd guess the error does not occur anymore). We need to drill down first, get a consistent environment and then look at the diagnosis.
There was an Errormessage at the beginning.
The screenshot shows some Apple iCloud stuff. Nothing to do with eBlocker! Sorry, this is just eBlocker support, not Apple 😉
THX for your cooperation!
I had deleted the VPN Profile in eBlocker
a few minutes later the error occurs again:
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 72 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * *traceroute: sendto: No route to host
traceroute: wrote 1.1.1.1 72 chars, ret=-1
*
traceroute: sendto: No route to host
8 traceroute: wrote 1.1.1.1 72 chars, ret=-1
*traceroute: sendto: No route to host
traceroute: wrote 1.1.1.1 72 chars, ret=-1
*traceroute: sendto: No route to host
traceroute: wrote 1.1.1.1 72 chars, ret=-1
*
9 *traceroute: sendto: No route to host
traceroute: wrote 1.1.1.1 72 chars, ret=-1
*traceroute: sendto: No route to host
traceroute: wrote 1.1.1.1 72 chars, ret=-1
*
Diagnostic report mailed.
@zwergkralle Very strange. Did you try to ping eBlocker's IP too?
Are the LEDs of eBlocker's LAN port lit/flashing when it fails?
THX!
ping test after error occures:
„Ping“ wurde gestartet …
PING 192.168.178.44 (192.168.178.44): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
ping: sendto: Host is down
Request timeout for icmp_seq 7
ping: sendto: Host is down
Request timeout for icmp_seq 8
--- 192.168.178.44 ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss
About LED I give you Feedback when the error occures again...
My last installation on a new sc-card there was also a failer as the box tryed to update. But a hard reset later and it was running well. I have all OS runnung but my MAC is a Hackintosh on a NUC and can't updatet to the last iOS. So is switched of. El Capitan is my version.
I think the eBlocker is good and I will fight my way through. For me, my network is often a book with seven seals. Maybe we can manage that too. Had tried other approaches and this is the best so far.
Still waiting for my new Pi 4-)
A question about the VPN profile. With my provider I can choose between VPN and VPN UDP. What kind of profiles have you tested so far?
When I activated VPN it said "at least one device is also using these profiles" I have no idea what that means. VPN was turned on on multiple devices. I can enable five devices with my provider. But the blocker should only count as one device? Does anyone here have any idea?
With my provider I can choose between VPN and VPN UDP. What kind of profiles have you tested so far?
I'd run the profile that works and can't recommend either one out of my head.
When I activated VPN it said "at least one device is also using these profiles" I have no idea what that means
Me neither. Please post screenshot as I don't know where you are at.
But the blocker should only count as one device?
Yes, I guess it only counts as one device.
Back to the original topic? Is your eBlocker running smoothly now? I've missed the cure. Please help to help others 😉
THX!
Yes, everything has been going well since noon, despite the VPN. But first I deleted the profile and wait. Will also use the PI 4 when I get it. Then I will test again with different VPN profiles. Thanks for the feedback!
I have just created and activated a new VPN profile. There is the message with arrow in the picture.
As soon as I have installed the new VPN profile, I have no access to the box, but Internet works. See image
If there is any connection here, I will continue testing. Are there any recommendations for VPN? Cyberghost is described in the manual as I did.
One thing, after hard reset the language was set to english but before to german.
@willifly Could your please remove the VPN profile again. Please leave the eBlocker running for a couple of days without VPN to make sure cause for the experienced issues is the VPN.
If (one day in future) you re-enable VPN, make sure to enable the "ping to VPN provider" or "ping to eBlocker" option. Reason: If your VPN connection goes down, eBlocker will try to re-establish the connection when "ping is enabled". Otherwise you will have "no internet" as eBlocker routes the traffic into "nirvana" (the dead VPN connection). I'd bet this is the cause of the issues, but it's strange you can't reach eBlocker's interface anymore (might be a bug) 🤔
THX!
@random Ok and WILCO. Give you an info after some days.
To understand, if the profile is installed but not used by any device, can this effect also occur?
To understand, if the profile is installed but not used by any device, can this effect also occur?
We don't know yet. So better remove the profile... 😉
THX so much for your support!
Yesterday the behaviour of eBlocker was quite strange. The GUI showed that https support is enabled. In the dashboard, however, the message that it is not activated. In the message box a message that https support can be activated. All this even though I had not disabled https support. Also the look of the dashboard was different than I had originally set it. In eBlocker the message that the device is active, in the dashboard the message that eblocker is not active for this client (iMAC)However, the eblocker seemed to be available all the time, so the error did not occur anymore. Now that the Raspi 4 has arrived, I will put it into operation this weekend.
In the dashboard, however, the message that it is not activated.
The test can run up to 2min. Just sit back and relax. Then it will show „green“.
Also the look of the dashboard was different than I had originally set it.
Dashboard is device depended. Different device = different dashboard.
dashboard the message that eblocker is not active for this client (iMAC)
Screenshots of both please.
BTW: most clients have two network interfaces: wired and wireless. Each interface is a different device from eBlocker‘s perspective. I‘d guess you might got mixed up here.
I‘m happy about all your (typical first time user‘s) observations. And yes, we know there is room for improvement. Thanks for mentioning this again.
Here in this thread it would be great to stick to the topic. Not to mix it even more with off topic „observations“. I‘ve tried to give clear guidelines what to test and it would be very helpful to stick to the plan 😉
THX!
@random:
Thank you very much for the hint. On my iMac the WLAN actually turned itself on.
I was not able to make screenshots because Raspi wasn't available again.
Because the problems with my Raspberry 3 could not be solved after 3 a long time and a lot of support I start as announced with a Raspi 4.
So I will not get back to you on this topic until the same problems occur on the new Raspi.
Sorry if my observations have caused confusion here.
Thx for Support.
Jo, since VPN remouved and rebootet, the eblocker can no longer be reached at ever shorter intervals. The only difference to the pure installation was a blocker list, which was recommended in the forum. Here again the last status in the picture. I have now replaced the Pi with version 4 with 4 Gb and everything has been stable since yesterday, installed without extras after individual configuration, so that the BOX does DHCP. Will share my experiences.
Next step depending on a few days:
1. Insert add. blocker list
2. Evaluate VPN profiles
@randlom
You were both right.
The problem was my Raspi 3.
After installation configuration of the Raspi 4, everything runs without problems at first go (since 2 days), also with Nord (VPN)
THX
@all
I could have saved the support team a lot of time and myself a lot of nerves if I had listened to their advice and bought a new Raspberry.
So the takeaway: if you run into problems on Raspi 3, get a Raspi 4.
I consider this thread closed then 😉 😊
I had similar issues with four different raspi 3+ systems with 1 Gb ram, not using VPN. I tried various configs and different network environments but basically the systems became unresponsive after I turned on https and waited for a while. Causing more traffic seems to shorten the time until eBlocker becomes unresponsive. Using a raspi 4 with 2 Gb works without issues.
I read that eBlocker runs on raspi 2 and 3 systems as well, is that not right?
I read that eBlocker runs on raspi 2 and 3 systems as well, is that not right?
In theory all Raspis run the same software. That‘s nothing specific to eBlockerOS but advertised by the Raspberry Pi manufacturer.
With the core eBlocker team we briefly testrun eOS on Raspi 3 too. But for longtime / production tests I‘m not sure if anyone ever did this. I‘m on Raspi 4 for example and have no Raspi 3.
If you feel like joining the eBlocker team for testing - especially on Raspi 3 - you are very welcome 🤗
I‘ll check back with @benne and @bpr if we should add a note to the download area that Raspi 3 might cause issues...
Could you please specify which Raspi 3 model‘s you‘ve tested already.
Nevertheless we are working on a bugfix release - which still shows issue - but we hope to release in the next few... maybe this fixes Raspi 3 issues too...?
Testers, please move forward 🤩 🤗
Could you please specify which Raspi 3 model‘s you‘ve tested already.
I tested four Raspberry Pi 3 Modell B+ with 1 Gb RAM, original power supplies and SanDisk microSDs.
The Router is a FritzBox 6490 with ipv6 disabled, I prefer expert mode but I also tested automatic mode. There's no VPN.
I'm happy to test the Systems again as soon as an update is available.
eBlocker seems like a great network filter, I used pihole before (which I also liked, especially the stats and administration) but the added functionality of eBlocker made me curious.