Since I've been using eblocker, the NYTimes App on my iPad (iOS 13), doesn't show pictures anymore. The https certificate from eblocker is installed. I already added the NYTimes app as trustworthy app in the preferences of the https-section and added the domains "Et.nytimes.com" and "NYTimes.com" to the exception list, but this didn't help
I just instalked the NYT app on iOS 13.4 - and it works without problemes. All imagrs are loadung,
Could you please point to an article where images don‘t load.
THX!
It's everywhere, starting on the front page. See screenshots:
Only exceptions for my NYTimes-app are ‘nyt.com’ and ‘nytimes.com’. No problem here.
iPad 5, iOS 13.4.1 and eBlocker (original) with eOS 2.4.5
Rob
The strange thing is: I also got the NYTimes App on my iPhone and I have no problems at all there. Same with the app "Weather Pro": On my iPad all the temperatures for the day are cut off, on my iPhone everything is normal. I don't use any adblocker on my iPad besides Eblocker.
So if I get you right: You have two iOS devices, both are enabled for eBlocker? Only one is showing a "strange behavior" and the other one is just working fine?
If that's the case, the one with the "strange behavior" is not installed correctly.
Are you sure you've also trusted the certificate (under iOS: General->Info->Certificate Trust Settings the eBlocker certificate needs to be enabled)? I suspect this is not the case with one of the devices.
@benne: You are totally right, there is a problem on my iPad with the certificate. For whatever reason, the certificate is installed, but I always get the error message "certificate could not be successfully checked". It's strange, because i'm sure I already installed it successfully before, the eblocker controlbar was there, but now it's gone. Anything I can do?
@hellb Try to delete cert on ipad, reboot ipad, reinstall cert, make sure to grant as root cert (as discussed above).
@benne I did exactly as you said, but the problem is still there. Certificate is activated as root as you can see in the screenshot.
When I interpret it right, the certificate you are trying to use is invalid since 07.03.2020.
In the admin console under https -> certificate -> renew it, download it again and import it on your device.
and check, if it is for 2 or 3 years, as it was a problem in another thread, when it was 3 years valid.
regards
Sven
@calimero Usually the date of cert generation is part of the cert name. So I guess the cert is valid.
@hellb Did you follow the work-around for iOS/macOS linked above the forum? Could you please make a screenshot of the certificates on iPhone and iPad under „General>Profile“ - as the one attached. BTW: all cert infos are public anyhow, so no worries about disclosing the info here.
@random Thanks for your help, I installed the cert just like in the ios/macos link, and now the certificate is okay. But: the nytimes.com still didn't show pictures afterwards (even after a reboot). But I added nyt.com to the exception list for that app as Rob Franssen said- and voilà this helped: I can see the pictures now. Great!
But another problem is still here: in the "Weather Pro" App I cannot add new cities, I get a SSL error now (see screenhot) (I activated the exception for "Weather Pro" in the eblocker settings)
@hellb Seems ipad is not recognizing eBlocker‘s cert. Therefore you‘ll experiencing issues all the time. I‘d recommend to turn off https support for the device. Or dig further for the source of error...
With https disabled your device will still be protected by DNS blocker, but no controlbar - just the dashboard.
But to answer your question: define an app under settings/https/trusted apps and add domain exceptions here. Then weather pro will probably work.
@random in the settings it says "Certificate is there" now and https is supported. So it should recognise it.
"Weather Pro" btw is already part of the trusted apps by default...
@hellb Are you seeing the eBlocker icon on websites that use https in Safari (on that strange behaving iPad)
So it should recognise it.
Buddy, it‘s software. Software is buggy. Even - or especially - with Apple. Don‘t trust what should be going, but verify what‘s going on. That might help better... 😉