I Cannot Connect to My Server: A Step-by-Step Diagnosis
Eliminate causes in order to find out whether the problem is the server, the address, the version, or the player's own network.
Before you start
- Access to your panel account
- The server's IP and port (on the 'Address' card in the panel)
- The exact error message the failing player sees
All Guides
The biggest time sink in connection problems is changing settings at random. The order below goes deliberately from cheapest to most expensive: each step definitively rules out one cause, so by step five you know for certain where the problem is not.
Is the server actually running?
The service must show as running in the panel, and the last console lines should contain something like 'Done (x.xxxs)! For help, type help'. If the console is still generating the world, the server is not accepting connections yet; on first boot this can take a few minutes.
Copy the address exactly from the panel
Copy the IP and port straight from the panel and try that. If you use a domain, set it aside for this step: the goal is to separate a DNS problem from a server problem. If the IP works but the domain does not, the problem is DNS.
Compare the versions
Does the player's client version match the server's? The 'Outdated client' or 'Outdated server' error says exactly this. If you want mixed versions to connect, you need the ViaVersion plugin.
Read the error text
Minecraft's error messages are more informative than people assume; the table below lists the most common ones and what they actually mean.
Try from another network
If you can connect but one player cannot, the problem is most likely on their side: school and office firewalls and some mobile carriers block game ports. Ask them to try over mobile data (or the other way round, over Wi-Fi).
| Error text | What it really means | What to do |
|---|---|---|
| Connection refused | The address is right but nothing listens on that port | Verify the server is running and the port matches the panel |
| Connection timed out | Packets never arrive, or no reply comes back | Check the address and the player's network restrictions |
| Unknown host | The domain cannot be resolved | Check the DNS record and propagation time |
| Outdated client / server | Version mismatch | Align versions or install ViaVersion |
| io.netty.channel... | The connection dropped mid-way | Inspect server memory (OOM) and console errors |
| You are not whitelisted | Whitelist is on and the player is not on it | Run whitelist add <player> |
Frequently Asked Questions
The server shows offline in my list but I can join
The status shown in the server list comes from a separate 'status ping' request, and some networks block that while the game connection still works. If you can join, there is no problem; refreshing the list usually fixes the display.
It worked yesterday but not today
Check two things first: the service may have expired (the panel will show it as suspended), and your game may have auto-updated. Those two explain the large majority of 'I changed nothing' cases.
Was this guide helpful?
Feedback goes straight to the team that maintains this guide.

