WSAETIMEDOUT (10060)
Windows connection attempt timed out
Seen in Windows applications (Winsock), "Socket Error # 10060"
Windows sent a connection request and got no reply at all before the timeout, so the traffic is most likely being dropped.
Common causes
- A firewall or cloud security group silently drops traffic to that port.
- The host is offline, or the address or port in the configuration is wrong.
- A proxy is required on this network and the app connects directly.
How to fix it
- Test the port from the same machine with `Test-NetConnection host -Port 443` in PowerShell.
- Allow the port on the server's firewall and any security group or network ACL in between.
- Confirm the hostname resolves to the current address and that proxy settings are correct.
Got a different message? Paste it into the error explainer.
Related errors
- ECONNREFUSED · Connection refused
- ETIMEDOUT · Connection timed out
- WSAECONNREFUSED (10061) · Windows connection refused
- Destination port unreachable. · The target rejected the packet with port unreachable
- ECONNRESET · Connection reset by peer
- EHOSTUNREACH · No route to host
- getaddrinfo ENOTFOUND · The hostname doesn't exist in DNS
- getaddrinfo EAI_AGAIN · Temporary DNS failure
- ENETUNREACH · Network is unreachable
- Broken pipe · Wrote to a connection or pipe that was already closed
- Software caused connection abort · Your own system aborted the connection
- Request timed out. · Ping got no reply