Alrighty, let’s tackle your port forwarding issue! Since you’ve confirmed the server works locally but fails over different networks, it’s likely the port isn’t open to the outside world. Let’s confirm AMP’s got this set up properly.
First, check in the AMP web interface:
Search for “Networking” in the top-right search bar.
Find the port number being used by your Minecraft server under “Server Port.”
Cross-reference the port with your router’s port forwarding rules—ensure the port is open and pointing to the local IP of your server machine.
Let me know if you’re stuck at any step.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Alright, let’s dig deeper. In AMP’s web interface, go to “Support” → “Diagnostics” and hit “Copy Data to Clipboard.” Paste the output here so I can see if it’s picking up anything weird, like a blocked port or misconfigured setting.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Alright, all good from the AMPs-side process so far. But, one eyebrow-raising thing: AMP’s “IP Binding” seems locked to 127.0.0.1 (localhost). You’ll want to adjust that since this blocks external access entirely.
Try this:
In the AMP web interface, search for “Webserver IP Binding”.
Change the setting from 127.0.0.1 to 0.0.0.0 (listening on all interfaces).
Save and restart the instance from within AMP.
This’ll open it up for external connections. Let me know where this takes you!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Alrighty, let’s rule out a stuck firewall rule next. In AMP, search “Firewall Rules” and check if the port for your Minecraft server is listed as open. Make sure it’s showing both TCP/UDP protocols if needed.
If it’s missing, you’ll need to add it there—AMP handles its own firewall rules. Let me know what you find!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Ah, no—leave the “Server IP” box blank in AMP’s Minecraft settings! That box is meant for scenarios with multiple network adapters/IPs, and filling it will restrict connections.
For Firewall Rules: Depending on the AMP instance type, it may not appear directly in the search. Instead:
Check your router’s port forwarding settings and ensure the rule is directing traffic from public <Your Public IP>:25565 to 192.168.1.101:25565.
Confirm AMP isn’t clashing by rechecking your diagnostics: open “Support” → “Diagnostics” and see if Firewall failures are listed under networking.
Still no go? Post any specific AMP log errors here as text. We’ll catch that sneaky culprit.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
This post was produced by an AI controlled by CubeCoders Limited - 
