- Order by phone: 0800 033 8006
- Blog
- Coverage checker
- Store locator
on 10-22-2023 03:21 PM
Is anyone else occasionally getting a 'connection down' error from Chrome (or 'Secure Connection Failed' from Firefox) when changing page - if I hit refresh it works fine. At first I wondered if it was the site I was using but have noticed it on multiple different major websites over the past couple of months and not noticed it from other locations where I don't use Three Broadband so does seem to be related to the router/connection (this is via wired Ethernet too, so not a WiFi problem). I've tried changing DNS server in case that helps but no difference.
It mainly seems to happen when trying to first load a site or (annoyingly) at checkout when a different site is being loaded as part of the checkout process. It certainly doesn't happen everytime but does happen with reasonable frequency. I've also noticed I often get it when trying to pull/push from/to Github too and have to do so a number of times for it to work (browsing the Github website works fine).
on 05-27-2024 10:14 PM
Like I said, the detection of the SSL drop error is dodgy.. relies on a text comparison which isn't necessarily going to stay the same across systems, but it was working for me untill the problem stopped..
I can't reproduce the fault on any platform or software tool here, so I can't find a better way to track the error..
GenFail counts are when the there is a reply, but the status code isn't 200 (or "too many requests)
If you're interested in digging further into this the feel free to DM me and I'll send some other code to try, no point fault finding this on forum.
05-27-2024 05:49 PM - edited 05-27-2024 05:59 PM
Thanks - downloaded - of course I've no idea how to compile it - so guess time to google and download visual studio 😄
Edit : downloaded VS Studio and Net extras, loaded in VS Studio and Built, now running 🙂
05-24-2024 07:19 PM - edited 05-24-2024 07:19 PM
Currently the most commented on thread in this forum section, but the lack of much response from Three or at least transparency on what they're doing to resolve the problem with regular updates is unreal....this must be affecting many many people.....of course some will blame alsorts, such as signal, websites, wifi, phone etc but this fault definitely lies with Three, and it seems to come and go with severity at random (currently not too bad but its still there). Do no Three engineers use their own broadband provider?
on 05-24-2024 09:35 AM
😂Geez! In this case the appear to have an invalid certificate on the support domain.
❯ ./checkssl.sh 'https://support.three.co.uk'
---
Testing: https://support.three.co.uk
---
Attempt 01: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 02: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 03: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 04: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 05: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 06: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 07: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 08: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 09: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 10: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 11: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 12: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 13: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 14: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 15: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 16: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 17: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 18: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 19: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
Attempt 20: Error - SSL: no alternative certificate subject name matches target host name 'support.three.co.uk'
---
SSL Errors: 20/20
---
on 05-24-2024 07:50 PM
Different SSL error to the connection dropped one..
This one is due to the certificate being returned from this URL, not being valid for the URL..
on 05-24-2024 07:55 PM
Cant find any link from three main page that links to this url anymore, so presumably they have dropped it..
on 05-26-2024 06:51 PM
It's linked from the account plan page
on 05-24-2024 07:54 PM
oh I'm aware I just thought it was funny, since we're talking about connection issues
05-23-2024 06:05 PM - edited 05-23-2024 06:10 PM
So after thinking things were going well (no issues for the past few days), I then had issues accessing web.archive.org today. I was getting the usual "unable to provide secure connection" message -
Switching on a VPN fixed the issue as usual.
When I switched the VPN off I then got a different error:
However I had already disabled content filtering previously, about a year ago!
I therefore went into plan settings and indeed the "Allow Adult Content" option was indeed off. I switched it back on, provided a credit card number and received a text confirming it had been set:
I then tried again in a fresh browser - same error - however when I go back into my account the filtering is definitely disabled and adult content is allowed:
I'm not sure what is going on but sadly after getting my hopes up it is definitely not fixed!
At first I thought the script wasn't picking it up as it showed success, but I realised I had just put in "web.archive.org". Changing it to "https://web.archive.org" showed 20/20 errors...
---
Testing: https://web.archive.org
---
Attempt 01: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 02: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 03: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 04: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 05: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 06: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 07: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 08: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 09: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 10: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 11: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 12: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 13: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 14: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 15: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 16: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 17: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 18: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 19: Error - error:0A000419:SSL routines::tlsv1 alert access denied
Attempt 20: Error - error:0A000419:SSL routines::tlsv1 alert access denied
---
SSL Errors: 20/20
---
on 05-23-2024 07:19 PM
This may be due to Threes adult content filter.. I've just tried archive.org and found out they have turned mine back on..
Requesting the http version redirects correctly and returns a correct status code 200, but from the wrong URL..