ISP difficulties (1 Viewer)

egg_

nerd/hippy
Supporter
Since 1999
Joined
Nov 15, 1999
Messages
14,396
Location
Where dogs wear hats and birds fly backwards
Have a weird thing going on here. Can't connect to various URLs, but only on Apple devices.

Examples:
https://asana.com

Also some work stuff, which is a problem. Google is ok, FB is ok, Wikipedia is ok

Ping works ok, curl does not. Can connect ok on Android and Windows. Can connect using the apple devices if I go via a phone hotspot over the mobile network

ISP guys are trying to be helpful but so far none of them have figured it out. @pete any ideas? Isn't there another network guy here too? @ernesto maybe? Or @rettucs?
 
This is what curl was showing me btw in case anyone is interested:

[datapipelines (T313412)]$ curl -v <url>
* Trying 151.101.193.187...
* TCP_NODELAY set
* Connected to asana.com (151.101.193.187) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to asana.com:443
* Closing connection 0
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to asana.com:443
[datapipelines (T313412)]$
 
This is what curl was showing me btw in case anyone is interested:

[datapipelines (T313412)]$ curl -v <url>
* Trying 151.101.193.187...
* TCP_NODELAY set
* Connected to asana.com (151.101.193.187) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to asana.com:443
* Closing connection 0
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to asana.com:443
[datapipelines (T313412)]$
i can't remember the option to enable it but i'm guessing if you ran that in verbose mode (-V?) you'd see more detail about the SSL cert mismatch that caused CURL to fail. There's another option (that i also can't remember right now) to tell CURL to ignore those errors.
 
That's the output from verbose mode. I actually had piddled about with parental controls about 18 months ago during The Worst Lockdown when one of the kids was staying up half the night falling into youtube rabbit holes, but ended up turning it off cos it was blocking stuff unpredictably. I guess the ISP must have turned it back on centrally but accident
 
That's the output from verbose mode. I actually had piddled about with parental controls about 18 months ago during The Worst Lockdown when one of the kids was staying up half the night falling into youtube rabbit holes, but ended up turning it off cos it was blocking stuff unpredictably. I guess the ISP must have turned it back on centrally but accident
ha i didn't even notice your -v

i recall seeing more detail when troubleshooting api calls over a proxy doing ssl inspection a while back
 

Users who are viewing this thread

Warning! This thread is more than 3 years ago old.
It's likely that no further discussion is required, in which case we recommend starting a new thread. If however you feel your response is required you can still do so.

21 Day Calendar

Alasdair Roberts/Harry Gorski-Brown
The Cobblestone
77 King St N, Smithfield, Dublin, D07 TP22, Ireland
Back
Top