Ive set up the Server for 3 players, 2 (i’m one if this two) can connect, but the third player can’t connect to the Server, at the Server List there is always an big X and the message, that he cant connect. The mods are the same we all use, there are no diffent mods on the launcher. can you please help me?
@CubeCoders-Bot can you give this user a hand diagnosing their connectivity issue? They’re probably home hosting so walk them through checking they can connect on their local network before taking a look at port forwarding. Assume the user is not particularly technical and will need clear instructions and to be prompted for further details.
Alrighty, seems we’ve got someone who can’t connect to your Minecraft server. Let’s start by testing if this player can connect locally on the same network before going full Sherlock on port forwarding.
First, Christian, is the player who can’t connect on the same local network/Wi-Fi as the server right now? If yes, have them manually type the local IP of the server into the Minecraft “Direct Connect” option instead of the server list. You can find the server’s local IP by running ifconfig (Linux nerd stuff) or checking your AMP interface under network settings.
Let me know if they can connect locally, and then we’ll go from there.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Hey, I forgot to write some addition to it - I’ve got an Server at another Hoster, there the third player can easily connect to it.
The players are all across the county, there is no other local player at my place. at first i’ve used nitrado, where the connection was ok, but after i set up the server at hostinger yesterday the connection (with the same mods & savegame, but also with a new world) is not possible
Ah, gotcha! So it’s not a local setup, and it worked fine on Nitrado but got grumpy once you switched to Hostinger. This narrows it down to something server-side—for starters, networky issues, firewall rules, or AMP settings.
First thing we’ll do is check if the server is properly listening for connections. Head to AMP and right-click the instance, then select “View Logs.” Look for anything suspicious that mentions failed connections or bindings. Let me know what you find!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Alright, if the logs aren’t showing any tantrums about failed connections, let’s double-check the server’s port configuration. From AMP, search for “Ports” in the top-right search bar and see what port your Minecraft server is using. By default, it’s typically 25565.
Next, ensure that the port is forwarded on Hostinger’s side, and if there’s a firewall, it’s set to allow incoming connections to that port. Hostinger should let you configure this somewhere in their control panel.
Give that a quick check and holler back!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Hmm, if there’s no apparent firewall control in Hostinger, it might have some restricted network policies in place by default. Let’s try testing the server’s actual connectivity to see if it’s reachable by players at all.
You’ll want to use an online tool like CanYouSeeMe.org or any port checker to verify if port 25565 is open and accessible. Use the server’s public IP and the Minecraft port.
Give that a shot and let me know if it’s all green lights—or if it’s frowning at us.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Perfect, the port being open means the world (er, server) can see you!
At this stage, we need to check if the connection issue might still be specific to the player. Can the third player, the one who can’t connect, try directly adding your server to their list with the IP and port (like your-ip-address:25565)?
If they tried that already but still bupkis, do they get any specific error message (e.g., timeout, or some cryptic Minecraft stuff)? Let’s stalk this error a bit more.
This post was produced by an AI controlled by CubeCoders Limited - Feedback