AMP Timeout: Rebind to Public IPv4

I am having issues with AMP I need to reach out to customer support. I’ve tried many things to get AMP binded to my public IPv4 and port 8080 however, once I bind it to my public IPv4 and port 8080 it is unreachable. It works on my local IPv4 just fine. My public IPv4 is without port pingable, however once I add it to port 8080 it is inaccessible.

Also I would like to note; AMP was working for a time on the public IPv4 via port 8080 then stopped working the next day. When I launched the AMP web portal it would not connect but the servers would start. In order to resolve that I ultimately attempted to reinstall everything. I have backed up the servers. But now I can run nothing.

OS: Windows 11 Pro

Product Name/Version: (Always use the full version number - not ‘Latest’)
AMP Instance Manager v2.6.0.6 built

Steps to reproduce:

Install AMP Instance Manager
Let it auto-bind to local host
Create Minecraft paper server
Realize you need to connect to public IPv4
Use CMD admin “ampinstmgr rebind”
Rebind Minecraft and ADS01
Run “ampinstmgr stopallinstances”
Run “ampinstmgr repairauth”
Verify changes with “ampinstmgr -t”
Close CMD
Attempt to relaunch AMP
Displays a connection timeout page.

Actions taken to resolve so far:

Open the ports on my firewall correctly.
Port forwarded my router.
Called my ISP to make sure that they are not blocking the port or anything else
Rebinding the amp instance and the servers to the same public IPv4. The amp instance support 8080, and each server to a port greater than 8080.
Checking my network adapter setting via control panel.
Downloaded surfshark to monitor connections.
Reinstalling AMP entirely including the AMP datastore folder located in the cube coders limited file folder.

I cannot circumvent using my public IPv4 to use something like a VPN (in the past I’ve used radmin VPN) because I want console players to be able to connect to Minecraft. Any help would be highly appreciated.

AMP can only bind to interfaces that the host machine “owns”, and cannot bind to your public IP.
AMP does not bind to localhost by default, but 0.0.0.0 (all interfaces).
The auth server is set to http://localhost:8080, because the local instances access the auth server locally, and their own web ports are not exposed.
Tl;DR, the defaults are fine, and there’s some other network issue causing the problem.
To get things back to a regular config, run:
ampinstmgr rebind ADS 0.0.0.0 8080
And
ampinstmgr repairauth standalone http://localhost:8080

From that known state, we should be able to poke around and narrow down the cause, since if AMP is not accessible after being port forwarded while things are bound to 0.0.0.0, then there’s something else amiss.

1 Like

Microsoft Windows [Version 10.0.26100.2605]
(c) Microsoft Corporation. All rights reserved.

C:\Users\HWsServ>ampinstmgr stopallinstances
[Info/1] AMP Instance Manager v2.6.0.6 built 20/11/2024 20:54
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Stopping Instance: ‘ADS01’
[Info/1] Stopping instance ADS01…
[Info/1] Waiting for instance to stop…
[Info/6] Instance ADS01 has stopped.

C:\Users\HWsServ>vampinstmgr rebind ADS 0.0.0.0 8080
‘vampinstmgr’ is not recognized as an internal or external command,
operable program or batch file.

C:\Users\HWsServ>ampinstmgr rebind
[Info/1] AMP Instance Manager v2.6.0.6 built 20/11/2024 20:54
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Please enter value for Instance Name

ADS01

Please enter value for IP Binding

0.0.0.0

Please enter value for Port Number

8080

[Warning/1] WARNING: Rebinding ADS will break logins/management for all instances/controllers that rely on it.
[Error/1] – You will not be able to manage any existing instances if you do this –
[Warning/1] If you are not familiar with how AMP manages authentication and logins, ask for support before doing this.
[Info/1] This prompt is case-sensitive. You should avoid rebinding ADS if at all possible.
Are you sure you want to rebind ADS? You will need to manually reconfigure any managed instances. [Y/N]

Y

[Info/1] Reconfiguring instance ADS01…
[Info/8] Done. Use --ShowInstancesList to see your changes.
[Warning/8] You should now run ampinstmgr repairauth on this system as well as any other AMP targets.

C:\Users\HWsServ>ampinstmgr repairauth
[Info/1] AMP Instance Manager v2.6.0.6 built 20/11/2024 20:54
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Which mode is ADS configured as? ‘standalone’, ‘controller’, ‘target’ or ‘hybrid’? If you do not know, press CTRL+C to abort.

hybrid

What is the URL of your controller/standalone instance? This URL must be accessible from all targets in a multi-target setup.

http://localhost:8080

[Info/8] Reconfiguring Instances…
[Warning/8] Failed to register job process
[Info/8] Done!

C:\Users\HWsServ>

NOTE: No logs were generated (C:\AMPDatastore\Instances\ADS01\AMP_Logs) at the time of the failed job processes

--------- Event log in GUI after rebind ---------
|Timestamp|Source|Category|Message|
|ScarletWolf|Dec 23, 04:34 AM|Authentication|AuthAuditEvents.LoginSuccess||
|ScarletWolf|Dec 23, 04:33 AM|Authentication|AuthAuditEvents.LoginAttempt|Login attempt from
(Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36)|
|ScarletWolf|Dec 23, 04:28 AM|Authentication|AuthAuditEvents.LoginSuccess||
|ScarletWolf|Dec 23, 04:28 AM|Authentication|AuthAuditEvents.LoginAttempt|Login attempt from 127.0.0.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36)|
|ScarletWolf|Dec 23, 04:23 AM|Authentication|AuthAuditEvents.LoginSuccess||
|ScarletWolf|Dec 23, 04:23 AM|Authentication|AuthAuditEvents.LoginAttempt|Login attempt from (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36)|
|null|Dec 23, 04:23 AM|Authentication|AuthAuditEvents.LoginFailure|No such user|
|null|Dec 23, 04:23 AM|Authentication|AuthAuditEvents.LoginAttempt|Login attempt from (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36)|

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.