How to Fix "Connection Timed Out" on a Minecraft Java Edition Server
"Connection timed out" means your game sent a request to the server address and nothing answered in time. The usual cause is that the server is offline or asleep. After that, check for a wrong address or port, a blocked port on a self-hosted server, CGNAT on the host's internet connection, or a router problem. A full server or a whitelist usually gives a different message, so rule those out last.
How to tell which problem you have
Work through these checks in order.
- Is the server running? Ask the owner, or open the host's control panel. Many free hosts stop a server when nobody is online. Some start it again when someone joins, and the first join attempt can time out while the server boots. Wait a minute and try again.
- Is the address exactly right? Copy it from the host instead of typing it. Check for a missing port. If the server uses a port other than 25565, the address needs it on the end, like
play.example.net:25570. - Can anyone else join? If a friend on a different network can join and you can't, the problem is on your side (your network, firewall, or ISP). If nobody can join, the problem is the server or the host's network.
- Is the server self-hosted? If it runs on someone's own PC, port forwarding, the PC firewall, and CGNAT are the likely causes.
Fixes, in order of likelihood
1. The server is offline or asleep
- Start the server from the control panel, or ask the owner to.
- If the host wakes servers on join, try once, wait about a minute, then refresh the server list and join again.
- Check the server console for a crash or a "Done" line. A server that crashed on startup will never answer.
2. Wrong address or port
- Remove the server from your list and add it again with a freshly copied address.
- Make sure there are no spaces before or after the address.
- If the owner gave you an IP and a port separately, join them with a colon:
203.0.113.10:25565.
3. Firewall or port forwarding (self-hosted servers)
- On the host PC, allow Java (
java.exeorjavaw.exeon Windows) through the firewall for both private and public networks. - In the router, forward TCP port 25565 (or your custom port) to the host PC's local IP address. Give that PC a reserved local IP so the rule keeps working after a reboot.
- Use an online open-port checker while the server is running. If it reports the port closed, the forward or firewall rule is not working.
- Friends must join using the host's public IP, not an address that starts with 192.168, 10., or 172.16 to 172.31. Those only work inside the same home network.
4. CGNAT
Some ISPs put many customers behind one shared public IP. This is called carrier-grade NAT (CGNAT). With CGNAT, port forwarding on your router does nothing, because the ISP's equipment sits in front of it.
To check: compare the WAN IP shown in your router with the IP shown on a "what is my IP" website. If they differ, or the router's WAN IP starts with 100.64 to 100.127, you are probably behind CGNAT. Your options are to ask the ISP for a public IP, use a tunnel service, or use a hosted server. See our guide on playing without port forwarding.
5. ISP or router trouble
- Restart the router and the PC.
- Turn off any VPN on the joining PC, then try again. Some VPNs block game ports.
- Some school, work, and public Wi-Fi networks block game traffic. Try a phone hotspot to test.
6. Server full, or whitelist confusion
A full server shows a message saying the server is full, and a whitelist shows "You are not whitelisted on this server!" If you see one of those instead of a timeout, the connection is working and the owner needs to raise the player limit or add your exact username.
Troubleshooting quick reference
| What you see | Most likely cause | First thing to try |
|---|---|---|
| Timeout for everyone | Server offline or asleep | Start the server, wait a minute |
| Timeout only for you | Your network, VPN, or firewall | Try a hotspot, disable VPN |
| Timeout only for friends outside the house | Port forward, firewall, or CGNAT | Open-port check, compare WAN IP |
| "Cannot resolve hostname" | Typo or new DNS record | Re-copy the address, try the IP |
| "Outdated server/client" | Version mismatch | See our version mismatch guide |
Where Shulkerboxes fits (and doesn't)
Shulkerboxes is free server hosting for Minecraft: Java Edition friend groups, so nobody has to port forward and CGNAT on a home connection does not matter. A server wakes up when a friend joins and is ready in about a minute. If your first join attempt doesn't get in, wait a minute and join again. It is invite-only with a waitlist, in the US, and it is free because gameplay is recorded and de-identified into AI training datasets (how that works). If your group needs mods, plugins, or Bedrock, pick a host that says it supports them.
Have an invite code? Enter it on the home page. No invite yet? Join the waitlist and we will save you a spot.
FAQ
Why does my server work on LAN but time out for friends?
LAN uses your local network. Friends outside need a forwarded port, an open firewall, and a public IP that isn't behind CGNAT.
Does "Connection timed out" mean I'm banned?
No. A ban shows a ban message. A timeout means no answer reached your game.
What is the default Java Edition server port?
25565, over TCP. If the server uses another port, add it to the address after a colon.
Why does the server time out on the first try and then work?
Some hosts start a sleeping server when the first join arrives. The first attempt times out while it boots. The next one works.
Sources
- Error messages ("You are not whitelisted on this server!", "Cannot resolve hostname", "Outdated client/server"): https://minecraft.wiki/w/Tutorial:Playing_on_servers
- Full-server behaviour (max-players): https://minecraft.wiki/w/Server.properties
- Default port 25565: https://minecraft.wiki/w/Server.properties
- CGNAT shared address range 100.64.0.0/10: https://www.rfc-editor.org/rfc/rfc6598