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

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 NodeArc Free Beta, an inactive server can sleep when nobody is playing. A real join attempt starts it and may place the player in a short waiting screen while the backend becomes ready. A server-list ping alone does not wake it.

2. Confirm the address and edition

Copy the custom address exactly, for example myworld.nodearc.net. NodeArc servers are for 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.

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

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.

When to ask for support

Open a Discord support ticket after checking the address, Java Edition, server status and version. Include the custom address, the approximate time, the visible client error and relevant console lines. Do not include passwords, tokens or panel credentials.