First find out whether the problem is the server or your side. Paste the address into our server status checker: if it says the server is online, the server is fine and the problem is between you and it.
If you are a player
- Check the address and port. A typo or a missing
:portis the most common cause. Copy it from the server's page instead of typing it. - “Outdated client” / “Outdated server”. Your game version doesn't match. Change the version in the launcher. Our server pages list the versions we could log in with.
- “Failed to verify username”. Your login session ran out. Close Minecraft and the launcher, sign in again and retry.
- “Connection timed out”. The server is not reachable from your network. School, work and some public networks block game ports; try another network or a phone hotspot to test.
- “You are not whitelisted” or “banned”. Only the server staff can change this; ask on their Discord.
- Mods missing. Modded servers need the same mods. The server page shows the mod loader and mods we detected.
- Bedrock: make sure you entered the port in the separate Port field, not after the address.
If you run the server
- Is it running? Look at the console for errors at startup.
- Port closed. Open TCP
25565(Java) or UDP19132(Bedrock) in the firewall and in your host's panel. server-ipset wrong. Inserver.propertiesleaveserver-ip=empty unless your host tells you otherwise.enable-status=falsehides the server from the multiplayer list and from server lists. Set it totrue.- Domain not pointing to the server. Check the A record, or the SRV record if you use a port other than 25565. See server IP and port explained.
- Behind a proxy (BungeeCord, Velocity)? Players connect to the proxy's address and port, not to the backend servers.
After a change, check again with the status checker; results are kept for one minute.