in MacOS terminal with arp -a the box appears with IP 192.168.1.2 (the formerly given permanent IP address), but the web interface of the box (settings) is not reachable with Firefox or Safari any longer, as a change to "automatic" IP (DHCP) is needed
Please be more verbose about your environment: check this first.
Sounds if you had access to the interface before as you say "formerly given permanent IP address". So what has caused the change? Power interrupt? SD card removed? etc.
The more precise you talk about the circumstances the better we can help.
THX!
Hi,
sorry for being incomplete with my infos. Here come some more - I hope suitable:
The change occurred after a power interrupt. In fact, the power supply is broke.
- Hardware for running eBlockerOS: White cube "eBlocker Pro" bought in 2016
- eBlockerOS version as well as filter lists version: OS 2.4.8, filter lists ? - the latest until September 18, 2020 if automatically updated by the eblocker network (?)
- https integration: yes (but not sure)
- Client and clientOS: MacbookPro (MBP) with macOS 10.15.7
- Exact way: type http://192.168.1.2 (the permanent IP address of eblocker) via WiFi between MBP and a dLink-Router (DHCP), eblocker connected by ethernet-cable to dLink-Router
- Alternative way: MBP (network) configured as DHCP with manual address (e.g., 192.168.1.10), eblocker connected to MBP by ethernet-cable, type http://192.168.1.2
In Terminal the arp -a does not show the eblocker, but just the request "192.168.1.2" ("incomplete")
@thomasr Tried http://192.168.1.2:3000 to access the settings interface?
Have you tried the macOS App to discover eBlocker in case it has a different IP? https://eblocker.org/community/announcements/ios-app-to-ease-eblocker-installation-now-in-store/#post-1348
LEDs of eBlocker LAN port are blinking, I assume? Otherwise it must be a hardware issue.
@random yes, I've tried, no success, neither by MBP nor iPhone - although the LEDs of eBlocker LAN port are blinking ...
@thomasr I can only suspect that your eBlocker‘s IP is in a different subnet (i.e. 129.168.0.2) so it can‘t be reached or the device is broken.
Have you tried reaching settings using the emergency IP https://eblocker.github.io/help/en-us/360004554034.html (see last paragraph)?
@bpr any other ideas?
@thomasr if you are a diy guy, you can open the case and install a micro SD with the M2+ image from the download page to see if the board is working still... - BUT this image probably wont run stable in production - on some boards. We‘ll come up with a stable image in the next few weeks...
Hi @thomasr,
You could try to let the eBlocker write an eblocker-status.html file on a USB thumb drive. The process is described here:
https://eblocker.github.io/help/en-us/360006072193.html
I followed the instructions to create the eblocker certificate running for 24 months instead of 36. The initial generation and activations go fine (Mac, iPhone, iPad), but the validity of the certificate seems to "evade" somehow very quickly, sometime within hours after a successful activation, i.e. https support stops and again the certificate process has to be repeated. Having done this now for a while on all clients, sometimes several times a day, sucks 😉 - is there anything I could do (or am doing wrong?)
@thomasr Have you updated to eOS 2.5? If not, please do do.
if you are looking at the HTTPS test in dashboard: give it time to run - up to 2min. No need to reinstall cert but just lean back!
THX!
well, do you mean "wait for up to 2 min before pressing the "test" button?
even if I do, the result has always been the same - see screen shot attached ...
@thomasr Sorry I thought you meant the dashboard tile „HTTPS“ which shows the correct certificate status after a while of testing only. Impatient users get easily confused here.
To get an overview: Go to dashboard ( http://eblocker.box). In the tile „Status“ click „Function Test“. Post results here.
THX
here you are 🙂
after having renewed the certificate, it's all fine - only that by itself the https-support stops and requires renewal of the certificate ...
@thomasr Are you on eOS 2.5.x? If not, please upgrade.
On eOS 2.5: If - after 2min wait - the dashboard shows under HTTPs that the certificate is not properly installed, it is not installed properly 😉
It's important to follow the certificate wizard step by step - reading every word.
I'm not on macOS so I can't help in detail, sorry. But thousands of macOS user's have made it successfully - so it's just a matter of taking it easy and following the instructions closely.
THX.