The "Connection timed out" error in Minecraft means the client sent a connection request but the server never responded. The client waits (typically 30 seconds), then gives up. Unlike "Connection refused" (where the server actively rejects the connection), a timeout means the request never reached a running service at all.
How the connection works
When you click "Join Server" in Minecraft, your client sends a TCP SYN packet to the server's IP and port. The server should respond with a SYN-ACK, completing the handshake. If that response never arrives, the client eventually times out. The problem is somewhere between your computer and the server process.
Common causes
- Server is offline or crashed. The most common cause. If the server process is not running, nothing is listening on the port.
- Wrong IP address or port. A typo in the server address, or using the wrong port number. The default Java port is 25565.
- Firewall blocking the port. A firewall on the server, on the network, or on your own machine is dropping packets before they reach the server process.
- Server is overloaded. When CPU or RAM is maxed out, the server may not be able to accept new connections even though the process is technically running.
- DNS not resolving. If you use a domain name instead of an IP, the DNS record may be wrong, expired or not propagated yet.
- ISP or network blocking the port. Some ISPs, schools and corporate networks block gaming ports. This is especially common on public WiFi.
Step-by-step troubleshooting
1. Verify the server is running
Log into your hosting panel and check. Is the server showing as "Running"? Check the console for crash messages. If it crashed, look at the last few lines of the log to see why, then restart it.
2. Double-check the IP and port
Compare the address in your Minecraft client with the one shown in your hosting panel. Check for typos. If your server uses a non-default port (anything other than 25565), make sure the port is included in the address as ip:port.
3. Check firewall rules
If you self-host, verify that your firewall allows incoming TCP traffic on your Minecraft port. On Linux, check with sudo iptables -L -n or sudo ufw status. On Windows, check Windows Defender Firewall. Hosted servers normally have the port opened automatically.
4. Look at server logs for crashes
Check logs/latest.log for errors. Common crash causes include: out of memory (look for "java.lang.OutOfMemoryError"), corrupt world data, incompatible plugins or running the wrong Java version.
5. Test from a different network
Try connecting from your phone's mobile data, or ask a friend on a different ISP to try. If it works from another network but not yours, the problem is your local network or ISP, not the server.
6. Check if the server is full
If max-players in server.properties has been reached and you do not have a reserved slot, the server may not accept your connection. Check the player count in the server list before joining.
7. Test DNS resolution
If you use a domain, run nslookup yourdomain.com or dig yourdomain.com in your terminal. The returned IP should match your server's actual IP. If using an SRV record, verify both the SRV and the A record are correct.
What is the difference between "timed out" and "refused"?
"Connection timed out" means no response at all. The server might be offline, the IP might be wrong, or a firewall is dropping packets. "Connection refused" means something at that IP actively rejected the connection. The machine is reachable but nothing is listening on that port, or the port is explicitly blocked. "Refused" is actually more helpful because it confirms the IP is correct.
What ports does Minecraft use?
Java Edition uses TCP port 25565 by default. Bedrock Edition uses UDP port 19132. If you run a Geyser proxy for cross-play, you need both. Always check which edition your players use and make sure the corresponding port is open.
When should I contact my hosting provider?
Contact your host when: the server shows as running but nobody can connect, you have verified the IP and port are correct, you have tested from multiple networks, and the server logs show no crash. This suggests a network or node-level issue that only the host can diagnose.
Avoid timeout headaches with reliable HostValues Minecraft hosting. Automatic crash recovery, DDoS protection and 24/7 monitoring keep your server reachable.
