Intermittent connection issues loading/changing site- secure connection failed/site can't be reached

[EDIflyer]

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).

I'm using a NR5103E with Firmware Version V1.00(ACBJ.0)b14 - I tried rebooting it but to no effect.

[_duncan_]

I've been intermittently seeing the same issue, with it being particularly noticeable when trying to access Wikipedia and the Tuya API servers.

Not sure if this'll help anyone, but I had it happen while trying to debug it a bit using `openssl s_connect`:

$ openssl s_client -connect en.wikipedia.org:443
CONNECTED(00000003)
4057319F5A730000:error:0A000126:SSL routines:ssl3_read_n:unexpected eof while reading:../ssl/record/rec_layer_s3.c:316:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 325 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

[_duncan_]

Running a few more tests today, I've made a quick script to basically do what I did above but a hundred times, and it's showing SSL connections up to about 30% of the time.

Results from that script:

• en.wikipedia.org: 25-29% failure rate (25, 27, 29, 25 from multiple tests)
• api.tuyaeu.com: 14% failure rate
• www.google.com: 0% failure rate
• duckduckgo.com: 1% failure rate
• www.github.com: 2% failure rate
• royalmail.com: 19% failure rate

[Nameless]

(A prompt for one of Three's staff members of any kind to mention a brief update, even if it's a "There are no changes" message)

My check-in with no changes

[fashric]

Mine has got worse this last few days, after a brief period where it seemed to have got better. Back to having to log into xbox gamepass 10 times before I can actually get connected....

[munk]

Any updates @JonathanB ?

I just had the SSL error again browsing Morrisons. 😞

[dirtydroog]

I've been suffering with this for ages. I'm using a Three Unlimited SIM in a my own router that's had no firmware updates in years. It was never this bad when I originally started using Three.

I also use Cloudflare's sDNS service but it doesn't help.

[dirtydroog]

It's really reproducible when trying to log in to the nsandi.com website

[munk]

I was on nsandi yesterday and got hit at the login page. Thankfully only one reload to get it working but still that's not what you want on a financial website is it?

[torz77]

Welcome to the black hole. A 45 page thread where no one will admit that there is a problem, much less find a solution.

Only 8 days to go before we celebrate our first birthday.

[Midnight54]

I think they're actively trying to get rid of people.  Had an issue past 2 weeks of about 15mbps, now I'm getting 2-5mbps, whilst connection is still 5G on the router and 250m from the mast. Not isolated to me as neighbours and their phones have the issues too, so its 100% the mast and/or area.  Eventually they rang back and said theres a problem and just "do you want to cancel right now" (I'll have to make some arrangements for something else but I'm off work ill too).  Of course still the SSL issue too.  Despite them acknowledging they have network issues too, the network status pages still say there are no reported issues for our postcodes, full on lies, if not fraudulent as people could sign up based on these reports