How to fix “Can't connect to server” in Minecraft.

Last reviewed: 25 September 2026. Start with the checks below. A failed connection is not a reason to reset your world or change server files.

1. Check whether the server is started

Open the panel Console and confirm the server finished starting. A process that is downloading files, generating a world or stopped after a crash cannot accept players. Read the latest console lines for a clear “Done” message or a meaningful error.

On the ChunkArc Free Beta, an inactive server can pause when nobody is playing. You can start it from the panel, or simply join its custom address: a real player connection starts it automatically. The first connection may take a moment while Minecraft boots.

2. Confirm the address and edition

Copy the custom address exactly, for example myworld.chunkarc.net. This checklist covers Minecraft Java Edition. Bedrock Edition cannot join a Java server unless a separate compatible cross-play setup has been deliberately configured.

3. Match the game version

Use a client version the server supports. Minecraft usually reports an outdated or incompatible client when versions do not match. Check the chosen server version in the panel instead of changing random client settings.

Do not use a Snapshot or Preview client unless the owner deliberately runs the matching build. The official Minecraft multiplayer guidance also recommends using a current release and matching the edition to the server before troubleshooting the network.

4. Check mods, plugins and whitelist rules

Fabric worlds often require matching client mods and dependencies. A missing or wrong version can reject a player during login. On a Paper or Purpur server, check that plugins are not blocking access. If a whitelist is enabled, add the exact Minecraft username.

5. Use the console error as evidence

If startup stopped after adding a plugin, use the plugin not loading troubleshooting guide to check compatibility and dependencies before changing network settings.

Ask the owner to inspect the server console at the time of the failed join. A version mismatch, authentication error, whitelist rejection or mod problem produces different messages and needs a different fix. Avoid restarting repeatedly because it can hide the useful first error.

6. What does the error actually say?

Unknown host: the client could not resolve the name. Copy the Java address from Manage again, without https:// or a panel URL. If the same address works for a friend, check your device's DNS or network before changing the server.

Connection refused: check whether Manage shows the server running and whether the console completed startup. Confirm the address and any port shown for that server. If those match and it still refuses, send the error time to support; changing the world or plugins is not the first step.

Connection timed out: wait for a Free server to wake and finish starting, then try once more. If the server is already running, a timeout can also happen along the network path between the player and server. Ask a friend on a different connection to try the same address. If one network works and another does not, include that result in the ticket instead of repeatedly restarting the server.

Outdated client/server or incompatible version: compare the client's version with the version the owner selected in Manage. Avoid Snapshot or Preview clients unless the server uses the matching build.

Failed to verify username, whitelist or a disconnect during login: keep the full message and ask the owner to check the console at that time. Sign in with the Java account that owns the game; for a whitelist, the owner must use the exact Java username. A mod or plugin can also reject a login, but the message alone does not identify which one. Do not disable security or authentication to make a player join.

7. Join the server in the supported way

This checklist covers Minecraft Java connections. For a Bedrock server, use a Bedrock client and the exact address and UDP port shown in ChunkArc Manage. A Bedrock client cannot join a Java server unless that server has a compatible crossplay setup.

If one friend can join but another cannot, compare their Minecraft edition, version, installed Fabric mods and exact username first. That difference is more useful than restarting a server that is already accepting a working connection.

When to ask for support

Open a Discord support ticket after checking the address, Java Edition, server status and version. Include the address, the time and timezone, the full client error, whether anyone else can join, and relevant console lines from that attempt. Say whether another network changes the result. Redact player IPs and never include passwords, tokens or panel credentials.

Sources used for the client checks

See Minecraft Help: joining a Java server and its multiplayer troubleshooting guide. Those are general client checks; the address, server state and console for your ChunkArc world are in Manage.