Minecraft "Connection Timed Out" Error — Complete Fix Guide 2026

The most common cause. If you're using Aternos or Minehut, the server auto-shuts down when no players are online. You need someone to start it before connecting.

Test it: Visit mcsrvstat.us and enter your server IP. If it shows "offline" — the server isn't running, not a connection issue on your end.

Fix: Log in to the server panel (Aternos/Minehut/OliveerF) and start the server manually. If using OliveerF, servers stay on 24/7 — check if the server was accidentally stopped in the dashboard.

Typos in the server address are surprisingly common. The format for Minecraft Java servers is ip:port (e.g., play.myserver.com:25565). If the port is 25565 (default), you can omit it.

Common mistakes:

• Mixing up 0 (zero) and O (letter O)
• Using a space before/after the colon: ip : port → ip:port
• Using a comma instead of colon: ip,25565 → ip:25565
• Wrong port number (server uses 19132 for Bedrock, not 25565)

Fix: Copy-paste the address directly from the server panel. Never type it manually if avoidable.

If you're self-hosting, Windows Firewall or iptables might block port 25565 inbound. Other players will get "connection timed out" even though the server is running.

Windows fix:

# Run PowerShell as Administrator:
New-NetFirewallRule -DisplayName "Minecraft Server" -Direction Inbound -Protocol TCP -LocalPort 25565 -Action Allow
New-NetFirewallRule -DisplayName "Minecraft Server UDP" -Direction Inbound -Protocol UDP -LocalPort 25565 -Action Allow

Or via GUI: Windows Defender Firewall → Advanced Settings → Inbound Rules → New Rule → Port → TCP → 25565 → Allow.

Linux (UFW) fix:

sudo ufw allow 25565/tcp
sudo ufw allow 25565/udp
sudo ufw reload

For players outside your home network to connect, your router must forward external port 25565 to your computer's internal IP. Without this, the connection "times out" at the router level.

Step by step:

1. Find your internal IP: run ipconfig (Windows) → IPv4 Address (e.g., 192.168.1.105)
2. Log into your router at 192.168.1.1 or 192.168.0.1
3. Find "Port Forwarding" section (sometimes under Advanced or NAT)
4. Add rule: External port 25565 → Internal IP 192.168.1.105 → Port 25565 → Protocol TCP+UDP
5. Save and restart router

Test it: Use canyouseeme.org — enter port 25565 while the server is running. If it says "Success" the port is open.

Some antivirus programs (Windows Defender, Avast, Kaspersky) flag Java server processes as suspicious and block the network connection silently.

Test: Temporarily disable antivirus and try to connect. If it works, add an exclusion.

Windows Defender exclusion:

# Add Java to Windows Defender exclusions:
# Settings → Windows Security → Virus & Threat Protection
# → Manage Settings → Exclusions → Add exclusion → File
# Navigate to: C:\Program Files\Eclipse Adoptium\jdk-21\bin\java.exe

VPNs and proxies route your traffic through different servers. The Minecraft server might block your VPN's IP (common with VPN blacklists), or the VPN might not support game traffic on port 25565.

Fix: Disconnect VPN completely, then try to connect to the Minecraft server. If it works, the VPN was the cause. Some VPN clients allow split-tunneling — you can exclude Java/Minecraft from the VPN tunnel.

If the server address is a domain (e.g., play.myserver.com), DNS might fail to resolve it. Try using the raw IP address instead to confirm this is the cause.

# Test DNS resolution (Command Prompt or Terminal):
nslookup play.myserver.com
# Should return an IP address. If it doesn't — DNS issue.

# Quick fix: use Google DNS
# Windows: Settings → Network → IPv4 → DNS: 8.8.8.8 / 8.8.4.4
# Or flush DNS cache:
ipconfig /flushdns

Sometimes your connection is fine, but the server itself crashed or ran out of RAM. A crashed server appears "timed out" to players — it accepts no new TCP connections.

How to check: Log in to your server panel. If the server shows as "stopped" or "crashed", check the console logs for errors. Common culprits:

• java.lang.OutOfMemoryError — need more RAM or reduce view distance
• Plugin incompatibility errors — disable recently added plugins
• Corrupt chunk — generate a new world or run chunk repair

Fix: Restart the server from the panel. If it keeps crashing, check latest.log in /logs/ and search the error message.