Can't connect errors

Server is green on the panel but players can't join. Each error message has a specific meaning — this guide translates the cryptic ones, splits "your fault" from "their fault," and walks the fixes.

First checks (do these before anything else)

1. Is the server actually online? Open the dashboard — status pill should be green. If grey/red, see Server won't start.
2. Are you using the right address? Copy it from Server Address on the dashboard. Not from an old email, not from memory.
3. Does it work for anyone? If you can connect but a friend can't, it's almost always client-side or ISP routing. If nobody can, it's almost always server-side.

"Can't reach server"

Generic catch-all from the Minecraft client. Usually means the IP / port the client sent its connection request to never replied. Causes, ranked:

• Typo in the address. Most common. play.myserver.com:25565 with a stray space, period or different port. Re-paste from the panel.
• Wrong port. Default is 25565 for Java, 19132 for Bedrock/Geyser. The panel may have allocated a non-standard one. Check the dashboard.
• Server stopped between attempts. Refresh the panel; sometimes a crash isn't reflected in the dashboard immediately.
• DNS not yet propagated. If you set up a custom domain in the last hour or two, give it time. Try the raw IP from the panel to confirm.

"Connection timed out"

The client sent a TCP SYN, the server never replied. Three suspects:

• Network firewall on the player's side. Some workplace / school / hotel networks block Minecraft's port range. Try from a different connection (mobile hotspot) to confirm.
• ISP routing problem. Rare but real. Have the affected player run tracert (Windows) or traceroute (Mac/Linux) to your server's IP. If hops stop early or jump from their ISP to nowhere, it's routing.
• Geolocation blocking — if you've added IP-blocking via a plugin or firewall rule, double-check the player's country isn't denied.

tracert play.myserver.com         # Windows
traceroute play.myserver.com      # Mac/Linux

"Connection refused"

Different from timeout — the server did reply, but said "go away." Causes:

• Server crashed or stopped but the IP still resolves to the node. Restart from the dashboard.
• Port mismatch. Connecting to :25565 when the panel allocated something else. Use the address from the dashboard verbatim.
• Service suspended for unpaid invoice. Check the Billing Panel.

"Outdated server" / "Outdated client"

Minecraft client and server protocol versions don't match. Two flavours:

• "Outdated server" — your client is newer than the server. Either downgrade your launcher profile to the server's version, or update the server. See Changing version.
• "Outdated client" — your client is older. Update your launcher profile.

Find the server's version: dashboard → console → type version.

"You are not white-listed"

Means exactly what it says — the whitelist is on and the joining player isn't on it. Three sub-cases:

• Whitelist is on but shouldn't be. Run whitelist off in the console.
• Player should be whitelisted but typed name wrong. Re-add with whitelist add <ExactName>.
• Server is in offline mode — UUIDs don't match the online whitelist. See The offline-mode gotcha.

"You are banned from this server"

Player is on the banlist. List bans with banlist, unban with pardon <Name> from the console.

If the player insists they were never banned: check banned-ips.json — sometimes a shared IP catches an innocent. Edit the file (server stopped first) and remove the offending entry.

"Server is full"

You've hit max-players in server.properties. Two fixes:

• Bump max-players higher and restart.
• Or grant the joining player bypassesPlayerLimit: true in ops.json.

If the server is empty but still says "full", check that max-players isn't accidentally 0 or -1.

"Bad login" / "Failed to verify username"

Mojang's auth servers couldn't verify the joining account. Causes:

• Mojang services down — check status.mojang.com.
• Player is signed in to a different Microsoft account in their launcher.
• Player is using a cracked / pirated client. PulsarServers runs servers in online-mode=true by default; cracked clients fail auth.

"This server is running [X], you have [Y]"

Modded only. The client's modpack doesn't match the server's. Either:

• Player downloads/installs the exact same pack and version.
• Or you re-install the version the player has on the server.

For private packs (CurseForge upload), share the export with players directly. For public ones (ATM, FTB, Prominence), point them at the matching CurseForge page.

"Flying is not enabled on this server"

Vanilla anti-cheat kicks players moving suspiciously. Common false-positive triggers:

• Elytra rocket boosts at world height.
• Modded jetpacks / flight rings.
• Anti-cheat plugins set too strict.

In server.properties, set allow-flight=true. If you're using a separate anti-cheat plugin, tune its flight check instead.

"Internal Exception: ..."

Net-level error. The most common variants:

• io.netty.handler.timeout.ReadTimeoutException — client took too long to respond. Usually the player's connection.
• java.net.SocketException: Connection reset — TCP connection dropped. Could be either end's ISP.
• End of stream — client closed cleanly without saying goodbye. Often modded clients exiting via the X button.

Single players hitting these = their connection. Many players at once = check the server's status, restart if needed.

Bedrock players can't connect

Bedrock clients use a different protocol entirely. They can only connect if you've installed Geyser (translates Bedrock ↔ Java) — see Adding plugins. Once Geyser is in, share the address shown by /geyser version with your Bedrock friends; the port is usually 19132.

Still stuck? Open a ticket with the exact error text, the affected player's country, and the last 50 lines of your console.