Fretboard closing my connection Cannot access the fretboard on my android via mobile internet?

CountryDave

My phone has been playing up today. Still not working. Will check for updates.
Edit - No updates

Bellycaster

I'm on 3 (Android Phone). Phone did an update couple of days ago. Today I find I can't log in on the phone. I get as far as typing my username, then when I try typing in my password, the browser shuts down and back to home screen.

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.

Dan_Halen

Been having the same problem with 3. Works on WiFi, not on data.

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.

maharg101

TLS negotiation happens independently of the underlying network infrastructure. 3 could only be affecting the TLS if they have broken TLS and are acting as a "man in the middle". This is very, very, very unlikely, and your online banking is not safe if this is the case.

There is evidently something amiss with accessing the site on 3 network, but it is nothing to do with TLS certs.

digitalscream

Just looking around, some folk have reported similar problems accessing sites using Three's network, weirdly geographically-related too, but the general consensus seems to be that it's their adult content filtering systems at fault.

Dan_Halen

digitalscream said:

Just looking around, some folk have reported similar problems accessing sites using Three's network, weirdly geographically-related too, but the general consensus seems to be that it's their adult content filtering systems at fault.

If it’s 3’s content filtering then my wife will be happy. She’d probably prefer to have me looking at porn rather than the classifieds 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.

Dan_Halen

To answer my own question probably no as the issue would likely persist regardless or data or WiFi. I’ll leave it to the experts!

maharg101

Dan_Halen said:

To answer my own question probably no as the issue would likely persist regardless or data or WiFi. I’ll leave it to the experts!

Took the words out of my mouth re TLS  

I think @digitalscream has it correct. Some sort of content filtering on the 3 network is a plausible explanation.

Bellycaster

I've had the problem on Data and Wifi.

Strangefan

I can confirm it's not the three adult filter as mine is off. 

Strangefan

   

PC_Dave

I'm on Three and I have the same issue - should mention that it's on an iPhone.

Mellish

FWIW, I'm using an android mobile but on EE. No issues here 90% of the time  

digitalscream

Any of you who're having the problem - could you try installing a free VPN service on your phone and testing it?

digitalscream

Strangefan said:

I can confirm it's not the three adult filter as mine is off. 

I suspect that the traffic still goes through the content filter, it's just not supposed to block it.

Strangefan

I can connect fine via a VPN.

digitalscream

Strangefan said:

I can connect fine via a VPN.

OK, it's definitely the Three network, then. I suspect there's very little we'll be able to do about it

exocet

I've had this issue for about a week now - it must be linked to 3 network. I have just changed my "adult content" settings as described 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?

maharg101

@exocet ; - traceroute or ping really proves nothing. For the connection to have been closed, it must have already been opened. If it works for your device on non-3 connectivity i.e. WiFi then it cannot be a TLS issue. By its nature, TLS is negotiated _directly_ between your browser and the server. Anything else would constitute a man-in-the-middle attack. If you're on android, and able to install f-droid / termux then you could try a curl as per my previous post and share here (via pastebin).

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.

exocet

Curl from 3.

https://i.imgur.com/S2kjufT.jpg

$                                               $ curl -ssv https://thefretboard.co.uk ;         *   Trying 2a01:7e00::f03c:91ff:fedf:dbfd:443...* Connected to thefretboard.co.uk (2a01:7e00::f03c:91ff:fedf:dbfd) port 443 (#0)

* ALPN, offering h2                             * ALPN, offering http/1.1                       * successfully set certificate verify locations:

*   CAfile: /data/data/com.termux/files/usr/etc/tls/cert.pem

  CApath: /data/data/com.termux/files/usr/etc/tls/certs

* TLSv1.3 (OUT), TLS handshake, Client hello (1):

* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to thefretboard.co.uk:443

$