Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Net/http: TLS handshake timeout #68

Open
djakielski opened this issue Mar 15, 2020 · 6 comments
Open

Net/http: TLS handshake timeout #68

djakielski opened this issue Mar 15, 2020 · 6 comments

Comments

@djakielski
Copy link

Most of the time, i got a few error messages with TLS handshake timeout like this

Error: Post https://api.uptimerobot.com/v2/getMonitors: net/http: TLS handshake timeout
Error: Post https://api.uptimerobot.com/v2/getPSPs: net/http: TLS handshake timeout
Error: Post https://api.uptimerobot.com/v2/getMonitors: net/http: TLS handshake timeout
Error: Post https://api.uptimerobot.com/v2/getMonitors: net/http: TLS handshake timeout
Error: dial tcp :0: connect: can't assign requested address
Error: Post https://api.uptimerobot.com/v2/getAlertContacts: net/http: TLS handshake timeout

Some time it works correcty. But most of the time it dosen't. When i try to call a request against the api, i got successfull responses.

My environment:

  • Mac OS
  • Terraform v0.12.23
  • Uptimerobot Provider latest release

Do you have any idea, why this could happend?

@drubin
Copy link
Contributor

drubin commented Mar 17, 2020

Error: dial tcp :0: connect: can't assign requested address this seems like a DNS issue.

Does this happen all the time or only sometimes?

@djakielski
Copy link
Author

djakielski commented Mar 17, 2020

It does most of the time. I also thought to dns, but when i tried it with curl, i got an response.

Maybe to much api request on the same time?

@drubin
Copy link
Contributor

drubin commented Mar 17, 2020

we are using it pretty extensively and we don't come up with this error, maybe its related to ipv6?

@djakielski
Copy link
Author

Same code, same remote state, execute on windows 10 works very well. I try get more information with the debug mode, but the only message i got was

Post https://api.uptimerobot.com/v2/getAlertContacts: net/http: TLS handshake timeout

@louy
Copy link
Owner

louy commented Jun 16, 2020

Seems like an issue with your network from the looks of it. Has it been resolved?

If not, can you try running a curl against the same url a few times and see if you get the same error?

@zackkrida
Copy link

Also seeing this problem intermittently 😢

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants