Connection timed out

The Connection timed out error means that a network connection attempt did not receive a response within the allowed time limit. The client system sent a request, but the destination host or service did not reply before the timeout period expired. This error commonly occurs in Linux and Windows systems, Java and Spring Boot applications, Docker containers, databases, APIs, and remote servers.

When does this error occur?

  • Connecting to a remote server that is slow or unreachable
  • Accessing a database service over the network
  • Calling an external API from an application
  • Communication issues between containers or services
  • Network traffic blocked by firewall or routing rules

Root cause of Connection timed out

This error occurs at the OS and network level when a TCP or UDP connection does not receive a response within the configured timeout window. The destination system may be offline, overloaded, blocked by firewall rules, misconfigured, or affected by high network latency.

How to fix the error (step-by-step)

Linux / macOS

Verify network reachability and port availability. 

ping <hostname-or-ip>

nc -vz <hostname> <port>

Windows

Check connectivity and firewall behavior. 

ping <hostname-or-ip>

Test-NetConnection -ComputerName <hostname> -Port <port>

Java / Spring Boot

Increase connection timeout settings when calling remote services. 

System.setProperty("sun.net.client.defaultConnectTimeout", "10000");
System.setProperty("sun.net.client.defaultReadTimeout", "10000");

Docker / containers

Ensure containers share the correct network and exposed ports. 

docker network ls

docker network inspect <network-name>

Database / network services

Confirm the service is running and listening on the expected port. 

netstat -an | grep LISTEN

Verify the fix

Retry the connection after applying changes. The service should respond within the expected time and the timeout error should no longer appear in logs or client output.

Common mistakes to avoid

  • Assuming the service is down without checking firewall rules
  • Using incorrect hostnames or ports
  • Setting timeout values too low
  • Ignoring DNS resolution failures
  • Testing from only one network location

Quick tip

Always verify basic network connectivity before adjusting application-level timeout settings.

FAQ

Q: Is Connection timed out the same as Connection refused?

A: No. A timeout means no response was received, while a refusal means the server actively rejected the connection.

Q: Can network latency cause this error?

A: Yes. High latency or packet loss can delay responses beyond the timeout limit.

Conclusion

The Connection timed out error indicates a delayed or blocked network response. Resolving connectivity, firewall, and timeout configuration issues typically fixes it. Check related root error references on ErrorFixHub for further troubleshooting.

Comments

Post a Comment

Popular posts from this blog

Port already in use

The root error Port already in use occurs when an application attempts to start a network service on a port that is already occupied by another running process. Because operating systems allow only one process to listen on a specific port and protocol combination at a time, this error is common in Linux servers, Windows systems, Java and Spring Boot applications, Docker containers, and database or web server environments. When does this error occur? When starting a server application while another process is already listening on the same port When a previously running service did not shut down cleanly and kept the port open When multiple applications are configured to use the same default port When a Docker container is still bound to a host port When system services occupy common ports such as 8080, 3306, or 5432 Root cause of Port already in use The Port already in use error is raised by the operating system’s networking stack. When a process binds to a TCP ...
Read more

Permission denied

The error Permission denied occurs when an application or user tries to access a file, directory, port, or system resource without sufficient privileges. This error is commonly seen in Linux and Unix-based systems, Git operations, Java applications, Docker containers, and server environments. When Does This Error Occur? When reading or writing a file without the required permissions When executing a script that is not marked as executable When accessing a protected directory or system path When binding to restricted ports or system resources When running commands as a non-privileged user Common examples rm: Permission denied cp: Permission denied chmod: Permission denied docker: Permission denied git: Permission denied Root Cause of Permission denied The operating system enforces access control using ownership and permission rules. Every file and directory has an owner, a group, and a set of permission flags. The Permission denied error occurs when the cur...
Read more

No such file or directory

The root error No such file or directory occurs when an operating system or runtime tries to access a file or directory that does not exist at the specified path. This error is commonly encountered on Linux and macOS systems, Windows environments, Java and Spring Boot applications, Docker containers, build tools, and server-side processes where file paths are resolved at runtime. When does this error occur? When referencing a file or directory path that does not exist on the system When a file was moved, deleted, or renamed but the application still uses the old path When relative paths are resolved from an unexpected working directory When volume mounts or shared folders are missing in containerized environments When configuration files point to incorrect or environment-specific paths Root cause of No such file or directory The No such file or directory error is raised by the operating system when a path lookup fails. At the filesystem level, the OS walks the...
Read more