Minecraft Can’t Connect to Server: Fix It in the Right Order

Run the two checks that prevent wasted work

1. Check the official service status first. For account, authentication, or Realms problems, confirm the current Minecraft and Microsoft/Xbox service status instead of reinstalling. During a confirmed incident, wait for the official update rather than changing your setup.
2. Try a second known-good server. If one server fails but a well-known public server connects, the fault is that server (offline, restarting, full, whitelisted, or on a different version), not your client or network.

Match edition and version before blaming the network

• Confirm you are on the same edition the server runs. Java Edition and Bedrock Edition are not cross-compatible on standard servers, so a Bedrock client cannot join a Java-only address without a bridge the server explicitly supports.
• Match the exact version. An “Outdated client” message means you must update, and “Outdated server” means the server has not upgraded yet; pick the version the server owner specifies rather than the newest release.
• Match any required modpack or loader. A modded server usually rejects a vanilla client or a different modpack version with a connection or handshake failure that looks like an outage.

Confirm the address and access rules

• Re-enter the exact server address and port from the owner or status page. A single wrong character, a stale IP, or a missing port produces a timeout that mimics downtime.
• Ask whether the server is whitelisted, full, or in maintenance. A whitelist rejection, a full player slot, or a scheduled restart all read as a failed join even when the server is healthy.
• For a Realms invite, confirm the invite is still active and that your account was added, because expired or removed access looks identical to a connection error.

Isolate your own network last

1. Test another network if it is safe and available, such as switching a device between Wi-Fi and a phone hotspot. If the same server connects elsewhere, focus on the original router, ISP path, VPN, proxy, or a school/work filter.
2. Restart the router and the Minecraft launcher only after the service, server, version, and address checks are clear. Restarting first often hides which layer actually failed.
3. Change one firewall or security rule at a time, and restore normal protection immediately after a controlled test. Do not leave the firewall or antivirus disabled for general browsing.

Avoid fixes that create bigger problems

• Do not download a third-party “connection fixer”, unofficial launcher, or account “unlocker”. Use the official Minecraft download and launcher only.
• Never enter your Microsoft or Minecraft password, recovery code, or two-step verification code on a server-list, mod, or “fix” site. Real sign-in happens only through the official Microsoft flow.
• Do not reinstall repeatedly before checking status and a second server; a reinstall cannot fix a server outage, a whitelist rule, or a version mismatch.