There is a know issue on iOS devices:
If HTTPS is not activated for the device and the "eBlocker Function Test" is started in the dashboard, it may indicate a failure (showing a red cross).
Fortunately it's not a failure of the eBlocker but a bug in the self-test routines. So please ignore this "failure". Your eBlocker just works fine 😉 😎
THX!
It seems to be a browser cache problem. The test passes after clearing the browser cache.
The test sends a request to http://ads.domainblockercheck.eblocker.com/_check_/domain-blocker. If the domain blocker works, a blocking response is returned and the test is OK. But if the request gets through, the web server at eblocker.com now returns a permanent redirect to eblocker.org. The browser then remembers the redirect and does not check the URL again in following tests.
We need to migrate all these test URLs to eblocker.org, too.