Since today my eBlocker does not work and, more worsen, obviously did something so that I can not reach the internet even when I unplug the eBlocker from my Fritzbox. I assume, eBlocker performed tonight the update to version 2.10. As well I can not contact my eBlocker via ssh on its IPv4 address in my WLAN: Connection refused at port 22. I am really at the end of my cababilities. I do not really know, where to begin and which steps to go.
If I klick on an URI I get the following message in the browser:
Error
Sorry, an error has occurred.
Details:
ERR_ICAP_FAILURE W05vIEVycm9yIERldGFpbF0= [No Error]
If this error persists, please try the following:
- Empty the browser cache
- Restart the browser
- Restart the computer
- Restart the eBlocker
- Consult eBlocker manual and FAQ
- Contact eBlocker support
Addendum: When in a browser I enter the IPv4 address of my eBlocker in order to load the frontend a plain window appears. And when in Terminal I ping -c 4 the IPv4 address it responds normally. So obviously the machine is speakeable. But doesn't work proberly.
What can I do in order to find what causes this problem and how to solve it?
SSH is not open by default on the eBlocker images, so if you have manually opened (and modified) the base system of eblocker and you are no longer able to get into the eBlocker settings to do anything, the only way for you is to write a clean eBlocker image to a new sd card and start from scratch.
If you are still able to get into the settings, verify if you have the latest release 2.10.3 already received.
When you have problems in your network, even when the eblocker is off, this could only mean two things
1) your eBlocker was DHCP server or
2) you screwed your network yourself anywhere else...
So the easiest way is to fix your network without eblocker first and then start eblocker from a fresh image without modifying it by yourself.
Regards
SSH is not open by default on the eBlocker images, [...]
Oops. I remember.
write a clean eBlocker image to a new sd card and start from scratch.
I'll do it.
If you are still able to get into the settings,
Unfortunately, I am not.
When you have problems in your network, even when the eblocker is off, this could only mean two things1) your eBlocker was DHCP server
If I remember right, eBlocker was the DHCP server, because I have read, when performing an eBlocker with a Fritzbox 7490 the eBlocker has to manage the addresses in the network, right?
So the easiest way is to fix your network without eblocker
Those machines in my network they never have used eBlocker services work properly as ever before. Only the machines they have been using eBlocker service are affected by the current issue.
then start eblocker from a fresh image without modifying it by yourself.
I'll do so. But that overnight the eBlocker has been stopped working without any information to one of the machines they are using its service is uncomfortably.
Nevertheless, thank you for your help!
With 7490, it is best practice to you the eBlocker as DHCP for it to function properly with al your devices
But when you tell, that machines, which are NOT using the eBlocker, are still working (??!), eBlocker is not the only DHCP in your network?
The only bug we had until now with the update 2.10.2 was a problem with the eBlocker VM Image, which has been fixed by Boris in version 2.10.3
Another strange thing is the ip address change of Rudi's Raspberry in another thread.
So it may be possible a bug which has mixed up network settings, but that's just a thought of mine
Good luck
Another strange thing is the ip address change of Rudi's Raspberry in another thread.
Hmm. My eBlocker can not being connected via its IPv4 address known until now. Maybe the same issue as at Rudi?
@facebita I know this issue only with the white cube, but to clear it up, if you can attach a monitor via hdmi, you will see the output and maybe post it here?
f you can attach a monitor via hdmi
Unfortunately I do not own an appropriate cable. 🙁
Could I find a meaningful logfile, when insert the SD card of my eBlocker/Raspberry into a SC card reader that is connected with my Mac?
@facebita Regarding logfiles this is beyond my knowledge, but maybe @bpr can support here?
Nevertheless, even if the logfiles point to an error, I fear solving the issue remotely is practically impossible. Sorry for the bad news.
My recommendation would be to reinstall eBlockerOS on a new(!) SD card as usually the cause for update issues is a broken/dying SD card (as lot's of data is being written during an update).
You can import an existing backup config (if you have made one) to ease setup. And you can re-use your donor key with the same email as initially used. Easy 👍
Hope this helps and good luck. 🍀
THX!
@facebita Sorry for the late response:
Logfiles, which the eBlocker diag itself exports to diagnose file like
and for apt
would be a beginning. Maybe you can join discord so we can get in direct contact?
For checking the sd card you should try "H2testw 1.4" from heise, for checking the health of your card.
Regards
@calimero I really appreciate you try supporting. But I‘m not sure what you intent with your last post. 🤔
Finding the logs in the OS is not everyones cup of tea - and worse: As said above, even if you see some errors - they are not helpful as we can‘t fix this remotely if eBlocker is not booting up. From my perspective it‘s a waste of precious user time - which can easily result in user frustration. 😖
I feel we should rather support in the literal sense of the word: helping our users to find a quick solution or work around.
@facebita If you are looking for a quick solution, please check my post above. In case you are a tech nerd and rather want to spend time with logfiles then consider @Calimero‘s support.
From my end I‘ll not intervene in this case any longer. Good luck.
THX!
@calimero […]
Finding the logs in the OS is not everyones cup of tea […] it […] can easily result in user frustration.
Don't afraid. I appreciate such support, even when I then find my limits.
I feel we should rather support in the literal sense of the word: helping our users to find a quick solution or work around.
Basically you're absolutely right. But someone - e.g. I - would like to try getting a lit bit more understanding what is beyond the canvas.
@facebita Well, I fear this "support" is not very helpful as you can not even read the SD card with your macOS. Since macOS does not support EXT2 filesystem out of the box. Again: We can not help you fixing your eBlocker even with the logs... Sorry!😥
If you really feel like helping @facebita, please send us your SD card! Then we can check what's going on and improve. But be advised: The SD may contain private data (as the last domains visited etc). Up to you. Please find the address in the imprint.
Last: I'm not sure what you are expecting "beyond the canvas" - we are not hiding anything. This project is open to everyone and you are invited to join the team. But it might become a little nerdy and technical at some point 😉
THX!
it might become a little nerdy and technical at some point
That is what I meant with "beyond the canvas". 😉
Hello all,
I have the same error here. Since when is not known, but probably also since last week.
The e-blocker worked until then. It was not manipulated (ssh etc.), but ran as intended.
So it can only have been an update.
"ERR_ICAP_FAILURE W05vIEVycm9yIERldGFpbF0= [No Error]"
The error points to squid.
Greetings
Addendum from syslog (I have mounted the card under Linux)..
eblocker squid[885]: Squid Parent: (squid-1) process 887 started
There is no entry under /var/log/squid.
reboot_after_update Log:
Sat Jan 7 07:01:25 CET 2023