A connection attempt failed because the connected party did not properly respond after a period of time
The connection timed out
Seen in .NET (SocketException 10060), Python on Windows (WinError 10060), Windows apps
Windows got no answer to the TCP connection attempt (WSAETIMEDOUT, 10060), usually because packets are silently dropped.
Common causes
- A firewall, security group or ISP filter drops traffic to the port.
- The host is down or the IP address is wrong.
- A proxy is required on this network but not configured.
How to fix it
- Check the port answers: Test-NetConnection host -Port 443.
- Check firewall rules on both ends and in the cloud provider.
- Configure the proxy if the network requires one.
Got a different message? Paste it into the error explainer.
Related errors
- requests.exceptions.ConnectTimeout · Python couldn't open the connection in time
- ConnectionRefusedError: [Errno 111] Connection refused · Nothing is listening on that port
- java.net.ConnectException: Connection refused · Nothing is listening on that port
- dial tcp: i/o timeout · Go couldn't connect in time
- No connection could be made because the target machine actively refused it · Nothing is listening on that port
- [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed · Python couldn't verify the server's certificate
- certificate verify failed: Hostname mismatch, certificate is not valid for · The certificate doesn't cover this hostname
- Max retries exceeded with url · requests gave up connecting to the URL
- socket.gaierror: [Errno -2] Name or service not known · Python couldn't resolve the hostname
- socket.gaierror: [Errno -3] Temporary failure in name resolution · Python couldn't reach a DNS resolver
- requests.exceptions.ReadTimeout · The server took too long to respond
- http.client.RemoteDisconnected: Remote end closed connection without response · The server closed the connection without replying