Minecraft Connection Timed Out: How to Fix

What does "Connection Timed Out" mean?

The error "io.netty.channel.ConnectTimeoutException: connection timed out" means your Minecraft client tried to reach the server but received no response within 30 seconds. This is always a network issue, not a problem with your world or mods.

Most common causes

1. Firewall blocking the port. The server port (default 25565 TCP for Java Edition) must be open in both the OS firewall and any cloud/VPS security group. On Linux, check with sudo ufw status or iptables -L -n | grep 25565.

2. Port forwarding not configured. If hosting on a home network, forward port 25565 TCP in your router to the local IP of your server machine.

3. Wrong IP or port in the client. Use the public IP, not the local one (192.168.x.x). If the server runs on a non-default port, append it: your.ip:25566.

4. Server process crashed or out of memory. Check the server console or latest.log. If -Xmx exceeds available RAM, the JVM swaps to disk and becomes unresponsive.

5. server-ip set incorrectly. In server.properties, leave server-ip= blank unless you need to bind to a specific interface.

Quick diagnostic commands

# Test if the port is reachable
nc -zv your.server.ip 25565

# Windows equivalent
Test-NetConnection your.server.ip -Port 25565

# Check if the server is reachable at all
ping your.server.ip

If ping works but the port test fails, the firewall is the problem. If both fail, the server may be down or the IP is wrong.

Client-side checks

If other players can connect but you cannot: disconnect any VPN, try a different network (mobile hotspot), flush your DNS cache (ipconfig /flushdns on Windows), and make sure javaw.exe is allowed through Windows Firewall.

Does this error mean my world is corrupted?

No. The timeout happens at the network level before any world data is accessed. Your save files are safe.

Can plugins cause this error?

Not directly. The timeout occurs before plugin code runs. However, a broken plugin can crash the server, which produces the same error from the client side.