Minecraft connection troubleshooter: find your next step

Read the version requested by the server. On JetRift, use Java 26.3 or Bedrock 26.60 exactly. Java and Bedrock version numbers are not interchangeable. Other hosts can support different releases. Restart a launcher after adding a Java installation and verify the version on the title screen.

If a phone has automatically updated beyond the supported Bedrock release, check the host’s compatibility notice. Reinstalling random APKs or disabling authentication is not a version fix.

Copy the hostname and port from the dashboard, check service status and let a starting world finish. Bedrock normally uses UDP 19132; Java uses TCP and may use a different port. A successful Java status ping does not prove Bedrock works.

Try another trusted network if possible. If all players fail, ask the owner to check the server. If only one network fails, investigate that connection. On a self-hosted setup, test on the server computer, then the LAN, then outside the home. Forward only the needed game port and keep the firewall enabled.

Quit Minecraft and the launcher, sign back into the official account and reopen the game. Bedrock needs Microsoft/Xbox sign-in and multiplayer permissions. A child account may need its family organizer to allow multiplayer. Check official service status if multiple players suddenly fail.

Keep authentication enabled on the server. Never send another person your account password, session token or recovery code.

Send your exact server-visible name to the owner. JetRift Bedrock names begin with a dot and replace spaces with underscores. The owner can check Players and the whitelist. Java and Bedrock accounts are separate, even if the names look similar. An actual ban requires the owner’s review.

Remove spaces, https:// and URL paths. Java takes a hostname, optionally with its port. Bedrock has separate address and port fields. Confirm the spelling and current address with the owner. If a new custom domain is involved, check its DNS records before changing your device’s DNS configuration.

Check that the server is ready and the destination port is correct. A manually stopped or failed server may need to be started from the dashboard. For self-hosting, confirm the server listens on the intended interface and port, then test locally before changing router rules. Do not expose an admin or RCON port to make Minecraft joinable.

Save the complete message and time. Try the supported game release without client extensions. Ask the owner to inspect logs for the same connection attempt. A reset or EOF by itself does not establish whether the problem is an account, protocol, server crash or network interruption.