It looks like you're new here. If you want to get involved, click one of these buttons!
Subscribe to our Patreon, and get image uploads with no ads on the site!
Base theme by DesignModo & ported to Powered by Vanilla by Chris Ireland, modified by the "theFB" team.
Comments
Edit - No updates
I can log in on work phone EE, and on Laptop.
Edit: The problem doesn't occur if I use Chrome, just when I use the Google search box on the homepage (I thought that was the Chrome search). Still don't understand why it suddenly started doing that as I'd used that method for months before without it happening.
Interestingly, it stopped working over the weekend when I was down south then started working again as I travelled north back to Scotland. Then stopped working again this evening :-)
Presumably an issue with 3 and their certs? Not sure if I’m presenting an invalid cert via 3… or if 3 fails to validate the TFB one? My understanding of TLS is pretty weak.
Tried other browsers, reset settings, clock settings etc.
There is evidently something amiss with accessing the site on 3 network, but it is nothing to do with TLS certs.
Trading feedback here
Although, to be serious, I’d probably expect an error or simply a timeout from content filtering. Be interesting to run some captures or something but not sure an iPhone is the best tool for the job
No chance of a TLS version issue following an update? Again, don’t totally understand it beyond 1.0 being deprecated in the recent past.
I think @digitalscream has it correct. Some sort of content filtering on the 3 network is a plausible explanation.
Trading feedback here
http://support.three.co.uk/SRVS/CGI-BIN/WEBISAPI.DLL?Command=New,Kb=Mobile,Ts=Mobile,T=Article,varset_cat=internetapps,varset_subcat=3582,Case=obj(16080)
Makes no difference unless the change is not invoked immediately on the 3 network.
I can Tracert from my phone to www.thefretboard.co.uk so I guess the issue is SSL / TLS related?
The most likely explanation is that the 3-network filtering is dropping the connection for some reason unknown to us. Ideally we'd have the ability to run tcpdump on an affected mobile (requires a rooted device) and on the server end to view what is happening on a packet by packet level. But given that the vast of majority of affected users are on 3 network, we may have to accept that the problem is on that network, and not with anything else.
Trading feedback here
https://i.imgur.com/S2kjufT.jpg