With iCloud Private Relay Apple has released their proprietary IP anonymization approach. Note that this feature might get accidentally activated after updating to iOS 15 or macOS Monterey.
Please be aware that using this feature will automatically disable the eBlocker advantages for Safari. Other browsers (like Firefox) are not affected.
Therefore we recommend not to enable Apple iCloud Private Relay.
We rather recommend to use Tor or a VPN with eBlocker (adding the VPN config to eBlocker) for IP anonymization. In result you get all advanced eBlocker blocking techniques and IP anonymization of all apps and the OS as well.
Tech background
Apple Private Relay is similar to a VPN that only enables IP anonymization for the Safari browser. All other macOS/iOS traffic is not routed thru the relay - leaving apps and the OS with non anonymized IPs. Apple encrypts the Safari traffic with some proprietary method, so eBlocker is no longer able to decrypt it for unfolding it's own traffic protection. In result you will experience ads, trackers and other unwanted content in Safari again.
😲Uff. This is bad news. Do you have a link with more details that it only works for safari and no other browser or app?
@newbie See the link above (under the word "iCloud Private Relay") or here again: https://support.apple.com/en-us/HT212614
Apple's headline already reads "helps protect your privacy when you browse the web in Safari." - which says exactly what it does... but for sure there are more articles about this on the web.
If unsure please direct your question to an Apple forum, as we can not cover Apple feature implementations/limitations in this forum, unfortunately.
THX!
😀thanks
@random Thanks for all the response - this issue persist with Safarie and Brave as well. Brave is based on a different machine, right?
@rudowin1962 The „issue“ is always encryption eBlocker can not decrypt. It‘s not particularly bound to Apple or a browser. But writing „disable encryption“ will often not show any reaction with Apple users - as they don‘t know Private Relay got enabled and this is encryption taking place (to hide the IP).
Background
If you are using a client based transport encryption (say a VPN, Tor, Apple Private Relay or whatever „IP hiding tech“ build into a browser) the eBlocker can not decrypt this. Hence eBlocker can not protect traffic it can‘t analyze = no eBlocker protection. No good for eBlocker: Client (with encryption) ->eBlocker -> Internet
To solve, eBlocker always needs to be the endpoint of the encrypted tunnel. This is why eBlocker comes with a VPN and Tor Gateway - to handle the encryption as endpoint. Good for eBlocker: Client -> eBlocker (handles encryption VPN/Tor) -> Internet.
And with eBlocker HTTPS enabled, eBlocker will terminate the HTTPS connection (to decrypt the traffic) and re-encrypt it for the client. Good: Client (with eBlocker Certificate) -> eBlocker (handles HTTPS) -> Internet
To make a long story short: Stay away from any client side encryption, otherwise you disable the eBlocker protection.
Hope this helps👍
THX!
@random yes, thank you for any help. I did as advised and I probably messed up. I stopped my Firewall and VPN (Lockdown). I downloaded from NordVPN a file and followed the instructions. That worked well. Afterwards, I run a eBlocker function test and? a ton of red dots. I was unable to fix this - removed the VPN file and went back to the original settings - much more red dots. Rebooted eBlocker - still persist. Ok, I take the blame, I messed somewhere somehow up.
I probably messed up
Yes! Not only your eBlocker - but also by constantly posting to the Announcements Forum. 😕
Would be great if you could stick to your question and stop mixing everyone up by cross-posting elsewhere: https://eblocker.org/community/bugs-features/domain-blocker-ads/#post-6052
I suggest to Factory Reset your eBlocker again and follow the Setup Instructions closely. If you run into questions, please see the first line above the main Forum: „Still questions? For quick help follow the README.“. Easy 👍
THX!