my.bt.com didn’t send any data.
Solved! Go to Solution.
Same difference. The landing page after logging in will the same whatever route I take to the secure area. I used your link anyway, same error. thanks
As you are using google_chrome_108, delete all bt.com cookies, you can do that without affecting other cookies.
chrome://settings/content/all
Paste that into the address bar.
How do you know/what makes you think I am using that browser?
I am not using Chrome, I am using Brave. I have tried with another browser, Firefox, and this time it fails but in a different way, it now says:
Secure Connection Failed
An error occurred during a connection to my.bt.com.
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
I am sure this a website configuration issue by BT, perhaps the SSL/TLS certificate. If it's not that then it's probably some kind of tracking stuff failing on the site due to privacy protections in my browser. Although I turned that all off and i still get the same. I have no cookies or cache, I clear it entirely every hour.
And for a third version of the error, I tried Safari browser, bog standard installation of browser with no extensions installed.
This is infuriating. I have a bill I need to pay (which failed first time) or they may cut my mobile phone service.
How do you know/what makes you think I am using that browser?
From your post extracted the forum RSS feed at 1800 today.
"Same difference. The landing page after logging in will the same whatever route I take to the secure area. I used your link anyway, same error. thanks"
Posted with device: google_chrome_108
"From the RSS feed at 1800 today." Don't believe everything you read!
I don't like being profiled or my privacy invaded, and thankfully that's incorrect. 🙂
The browser user-agent information is available to anyone, and is used by the web server to present the correct page format.
If you are using a browser add-on which is designed to present an incorrect user-agent, then its not surprising that the web server throws up an error.