05-02-2019 04:09 PM
When using EE 4G data on a mobile or using the SIM as a personal hotspot on a home PC, a website that I regularly use is showing an error message:
Your connection to this site is not secure
I contacted EE technical support who said that they had removed the antivirus and content blocks from my account but this did not have any effect.
I have tried multiple browsers and troubleshooting Chrome by clearing cookies and history, logging out and restarting my mobile device but no change.
Has anyone had a similar problem?
05-02-2019 07:14 PM
What site is it? It's not unusual for some sites to have invalid or out-of-date security certs, This will affect everyone visiting it.
05-02-2019 08:13 PM
You are normally given an option to visit the site (advanced option). The site owner needs to sort out the domain name SSL certificate.
05-02-2019 10:21 PM
05-02-2019 11:17 PM
I can get to that site using IE & FF on a PC & Samsung Internet on my mobile w/out any such warning.
Doesn't "Learn More" lead you to more allowing you to get to the site?
06-02-2019 05:24 PM
Thanks! You're welcome :)! Glad I could be of assistance.
If you really want to get to it, try other browsers. It looks safe.
07-02-2019 11:21 AM
07-02-2019 02:22 PM
I don't believe that as had EE blocked the site you would get a "THIS CONTENT IS LOCKED" message. It is that some browsers are blocking it due to an invalid security cert.
07-02-2019 02:30 PM
If it was the browser it wouldn't work on my dual SIM iphone over Vodafone, @XRaySpeX. It just doesn't work on EE. It's fine on EE with a VPN or another network, it's EE that is the cause here.
09-02-2019 12:10 PM
I have seen other users reporting similar issues with web sites and EE. It seems to be an issue with IPv6 configured on the server but not on the virtual web server, and EE not doing browser fallback to IPv4.
I don't understand why on EE I don't get fallback but on my WiFi I do, and these sites work.
09-02-2019 02:25 PM
@chistery: Where are those browser settings to be found?
09-02-2019 04:23 PM
Thanks, @chistery, that's useful.