Error: Cannot connect using TLS

Question

Error: Cannot connect using TLS

dt-flo opened this issue 6 years ago · 9 comments

Right now my server is already preloaded so everything is fine but I still wanted to report an error. If I enter "removed", I get the following message:
We cannot connect to **removed** using TLS ("Get **removed**: dial tcp **removed**:443: connect: network is unreachable").

Answer 1 · 2018-11-29T19:13:16.000Z

I'm unable to connect to florian2833z.de where I am (in California).

Answer 2 · 2018-11-29T19:14:43.000Z

In addition, note that Google Cloud (where hstspreload.org is hosted) used to have issues with IPv6, and may still have them: #43

Answer 3 · 2018-11-29T19:50:13.000Z

I'm unable to connect to removed where I am (in California).

Can you give me your ip address so I can report those connection issues?

Answer 4 · 2018-11-29T19:57:23.000Z

Can you give me your ip address so I can report that connection issues?

Would you mind emailing me for that? Thanks!
(My email is on my GH profile, or on my website.)

Answer 5 · 2018-11-29T19:59:14.000Z

mail went out

Answer 6 · 2019-01-15T23:06:13.000Z

My website has the same issue
( eallion.com )

Answer 7 · 2019-01-15T23:13:34.000Z

@eallion I get the following error when checking your domain:

We cannot connect to https://eallion.com using TLS ("Get https://eallion.com: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)").

That's a separate issue than the IPv6 issue reported here.

I'd suggest building the command line tool in this project and testing your site against it, as it's likely due to a server configuration problem.

Answer 8 · 2019-04-04T14:05:09.000Z

@eallion @nharper same issue with my domain:
We cannot connect to https://cevin.at using TLS ("Get https://cevin.at: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)").

Although I did manage to get it on the pending list. Is it now my mistake or the website's ?

Answer 9 · 2019-05-08T20:19:42.000Z

The original issue reported on this thread indeed appears to be another case of #43 - please follow that issue for updates. The other domains mentioned in this thread are now on the preload list and are not showing any errors.