A failed connection does not identify the cause by itself. The server could be restarting, the address could be wrong, or the server could be reachable while refusing your login. Start by separating a status problem from a joining problem.
Record the problem before changing settings
Write down the address, port, game edition, game version, time of the attempt and the exact error message. If the server has separate Java and Bedrock addresses, record which one you tried. That information is much more useful to an owner than “it does not work.”
Check the public response
Enter the public address in our Minecraft server checker and select the correct edition. Use the owner's explicit port where one is provided.
- The checker responds, but you cannot join: investigate account access, whitelist, version requirements, resource packs or the game-specific error. The status query does not test a complete player login.
- The checker gets no response, but you can play: the server may handle status queries differently, block the checker's connection, or expose a different address. Do not treat the result as proof that gameplay is down.
- Neither works: check the owner's announcements and address, then ask whether other players can connect.
The checker tests from an external service. It cannot establish whether a private LAN server works inside your home. Addresses such as localhost refer to the machine making the request; they are not a way to check your computer from this website.
Read the error message
Unknown host: start with spelling and the hostname supplied by the owner. Avoid adding https:// or a website path. A hostname resolution failure is different from a game login rejection.
Connection timed out: confirm the port and whether the owner reports maintenance. If another person can connect using the same edition and address, share that comparison with the owner.
Incompatible version: compare your client version with the owner's supported versions. A modded server can require a specific pack even when its base Minecraft version matches.
Whitelist or ban message: contact that community through its official support channel. Repeatedly changing addresses will not grant access to a restricted account.
If you own the server
First confirm that the server process has finished starting and inspect the console for startup errors. Test from the server machine, then another device on the local network, then an external connection. Record where the first failure happens. That helps distinguish a startup problem from a network-path problem.
On Paper, server-ip selects the interface to bind to; it is not a field for advertising your public address. A normal setup generally leaves it blank. Check your hosting provider's configuration before changing it. Paper's troubleshooting documentation explains startup and binding failures.
Check the assigned port and the firewall or forwarding rules for your actual setup. Avoid disabling your entire firewall as a shortcut. Hosted panels, containers and home routers have different places where a port must be exposed.
Java works but Bedrock does not
Test the Bedrock address separately. On Geyser setups, a working Java connection does not prove that Bedrock's listener is reachable. Bedrock gameplay uses UDP; current Geyser transport and signaling configurations can also require TCP or HTTPS setup. Follow the instructions for your installed version and hosting method in the Geyser setup guide, rather than copying an old forwarding recipe.
Send a useful support message
Include your edition and version, device, address and port, exact error, approximate time and whether anyone else can connect. Include the public status result, but explain that it was a status check. Never include passwords, access tokens or hosting-panel credentials.
Once the address is working, follow our Java and Bedrock joining guide. Owners preparing a new server can use the Paper server setup guide and verify the public address before sharing their listing.
