@CubeCoders-Bot can you help this user with their connectivity issue please. Check if they’re home hosting, try another device on the same network, guide them through checking their internal IP and firewall rules, etc.
Alrighty! Let’s troubleshoot why your Minecraft server isn’t cooperating with your connection attempts.
First things first: Are you hosting this server on your home network? If yes, your client needs to use the internal LAN IP address to connect if you’re on the same network as the server. Let’s double-check:
On the machine running AMP, run ipconfig (search for it in the Windows terminal) and look for the IPv4 Address in the output. It’ll look something like 192.168.x.x or 10.x.x.x. Use that in Minecraft instead of any public IP or hostname.
Let me know if it’s still playing hard to get!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
still no luck after the response. tried to join on the same network and server still isn’t showing its online. I have previously had this server up and running before and have played on it. I shut it down and havn’t been on it in a couple weeks. I’ve already port forwarded and unblocked firewalls
Alright, if it’s still not showing as online… it’s firewall-checking time! AMP manages all that jazz automatically, but sometimes Windows Firewall or other security software throws a tantrum.
Head to your AMP’s ADS instance.
Right-click your Minecraft instance, then “View Logs”.
Check for any errors or red flags there about binding to ports or network issues.
If all seems fine in the logs, it’s worth trying this:
Search for “Firewall” in AMP’s UI top-right, and ensure the right ports (default for Minecraft: 25565) are open.
Holler back with log highlights, or let me know if you’re unclear on any of that!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
If the logs are squeaky clean, ports are listening, but the server is still AWOL in Minecraft, let’s check one more thing—a potential IP binding issue. Sometimes, the server binds to an IP that your client isn’t looking at.
In AMP:
Go to the Minecraft instance settings.
Search “Bind IP” in the top-right.
If it’s blank, that’s good—it binds to all interfaces. But if there’s an IP set, match it to your server’s internal IP (192.168.x.x, etc.).
Try connecting again after confirming/changing this. If things are still stubborn, we might have to go full tech-sleuthing! Keep me posted.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Alright, this server is being extra difficult, huh? Since we’ve ruled out ports, bindings, and basic setup, let’s eliminate one more sneaky culprit—your client and local network.
Try this:
Test connecting from another device on the same network. (Preferably with a fresh Minecraft install.)
Ping the server’s private IP (192.168.x.x) to confirm it’s reachable on the network:
On your PC, open cmd and type ping 192.168.x.x (replace with the server’s local IP). Let me know if there’s any response.
If the ping fails, it’s definitely a network communication/blockage issue. Let’s sort what’s jamming things!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Ah, there it is—if your ping says “connection timed out,” then something on the network is throwing down the denial hammer. Here’s what could be up:
Windows Firewall Settings:
On the server machine, search for “Firewall” in Windows.
Go to “Advanced Settings,” and ensure inbound/outbound rules for your Minecraft’s port (default: 25565) are explicitly allowed.
Network Isolation:
If you’re on something funky like a guest Wi-Fi network, sometimes it restricts devices from talking to each other. Ensure both machines are on the same main network (and not on “Public”-type profiles).
Fix those, and let me know how it rolls! If it times out the same way, something bigger might be blocking AMP’s networking access, like a router setting. Let’s not go there just yet, though. Keep me updated!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
This post was produced by an AI controlled by CubeCoders Limited - 
Since we’ve ruled out ports, bindings, and basic setup, let’s eliminate one more sneaky culprit—your client and local network.
