Fix "Connection timed out" when joining a Minecraft server

A timeout means nothing answered your client at all. Work down this checklist in order and you will find which of the five usual causes you have.

6 min read · Updated Oct 21, 2026 · By GuavaHost Team

First, the single most useful distinction in Minecraft networking:

"Refused" means a machine answered on that address and told your client there is nothing listening on that port. That is usually a wrong port number. "Timed out" means no answer at all, which points at a server that is not running, an address that goes nowhere, or a firewall quietly dropping the traffic instead of replying. The two need different fixes, so read the message carefully before you start.

Step 1: Is the server actually online?

Sign in at customer.guavahost.com, open My servers and click Manage on your server. Look at the coloured status next to the server name.

• Online means the game is up and should accept players.
• Starting means it is still booting. A large modded server or a freshly uploaded world can sit here for several minutes, and players who try during that window get a timeout.
• Offline means nothing is listening. Press Start and watch the Console tab.

If it goes to Starting and falls back to Offline, you have a startup problem rather than a connection problem. Why your server says Starting or is stuck offline walks through reading the console for the real reason.

A server that is Online but still times out for everyone is worth telling us about, because that is unusual.

Step 2: Check the address, character by character

Take the address from the panel rather than from a chat message. Open the server page and copy the value next to Address at the top, or Server address in the Ports & network card on the Overview tab, using the copy button.

Then compare it with what the player typed. The mistakes we see most:

• A missing port. If your server does not use Minecraft's default port, a bare IP will not reach it.
• A space at the start or end, picked up by copying out of Discord.
• A full stop at the end of a sentence, pasted along with the address.
• The RCON or query port instead of the game port. Those answer nothing a Minecraft client understands.

Finding your server IP and port shows exactly which field to copy and what to hand out. If you use a domain name, also check that the DNS record still points at the current IP: Address, IP and port: what to give your players covers hostnames and SRV records.

Step 3: Rule out an allowlist

A whitelist does not cause a timeout, but it is worth checking, because reported symptoms are rarely precise. A whitelisted server rejects the player with a clear message like "You are not white-listed on this server!" instead.

If that is the message your players get, Allowlists and whitelists shows how to add names in the right order so you do not lock yourself out.

Step 4: Narrow it to one player

Have one person try at a time rather than the whole group at once. The result tells you which side to work on.

Step 5: The player's own network

When it is one person, the cause is almost always something between their computer and the internet.

1. A local firewall or antivirus. Windows Defender Firewall and third party security suites both block Java from making outbound connections sometimes, usually after a Java update changes the executable's path. Allowing javaw.exe for the launcher's Java fixes it.
2. A VPN. Turn it off and retry. Some VPN exit nodes block game ports entirely.
3. A school, office or hotel network. These very often allow only web traffic on ports 80 and 443, and drop everything else silently, which produces exactly this timeout. There is usually no way around it from the player's side.
4. Mobile data and hotspots. Carrier-grade NAT (where many customers share one public address) does not usually stop outgoing connections, but mobile networks sometimes block uncommon ports.
5. Router or modem trouble. A restart of both is worth doing early.

When a firewall or network blocks your game port goes through each of these with a quick test for each, including the honest cases where a network simply cannot be used.

One thing you do not need: port forwarding. That applies to a server running on your own computer at home, not a hosted one.

Step 6: "Took too long to log in"

This one is a cousin rather than the same error. The client reached your server and started the handshake, but the login did not complete in time. Common reasons:

• Mojang and Microsoft authentication servers are slow or having an outage. Your server has to check the player's account with them, and if that check hangs, the login stalls.
• Your server is badly overloaded and the main thread cannot finish the join. If TPS (ticks per second, the server's heartbeat) is already poor, joins are among the first things to suffer.
• A plugin doing slow work during login, such as a permissions or economy plugin waiting on a database.
• A proxy in front of the server with mismatched forwarding settings.

Waiting a few minutes genuinely is the answer when authentication is the problem.

Step 7: Read the console while they try

This is the fastest diagnostic of the lot. Open the Console tab, keep it visible, and have the player attempt to join.

• A line appears naming the player or their IP. The connection reached your server, so the problem is after that point, not a timeout at all. Read what the line says.
• Nothing appears at all. The traffic never arrived. The address is wrong, the port is wrong, or something between the two is dropping it.

That single test splits the problem in half, and it is what our team will ask you to do first anyway.

Common questions

What is the difference between timed out and connection refused?

Timed out means nothing replied to your client at all, so the address goes nowhere, the server is not running, or a firewall is silently dropping the traffic. Refused means a machine did answer and told your client that nothing is listening on that port, which almost always means the port number is wrong.

Do I need to port forward a GuavaHost server?

No. Port forwarding is for a server running on a computer at home behind your own router. A hosted server already has a public address and open ports, so there is nothing on your router to change.

Why can I join but my friend gets a timeout?

Because the server is clearly reachable, so the difference is on their side. The usual culprits are a local firewall blocking Java, a VPN, or a restricted network such as a school, office or hotel connection that only permits web traffic.

My server says Online but nobody can connect. What now?

Check that the address you handed out matches the one in the panel exactly, including the port, then watch the Console tab while someone tries to join. If no line at all appears for their attempt, the traffic is not arriving and the address is the thing to fix.

Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.

• minecraft
• java
• connection
• timeout
• troubleshooting

Host a Minecraft Java server From $3.99/mo, with instant setup and DDoS protection.

Still need help? Our team is online 24/7 to answer questions.

Contact support