Rejoin existing server back to amp

OS Name/Version: ubuntu 24 lts

Product Name/Version:amp 2.6.4.2 on primary, 2.6.3.2 and 2.6.4.0 on target minecraft server

Problem Description:

I had a working initial setup where amp was running on 10.0.0.227 and my target game server was 10.0.0.226. Then I changed my ISP (yay fiber) and my AMP VM is now 192.168.4.227 and my target Minecraft server is 192.168.4.226. AMP couldn’t find my target server and was stuck refreshing even after i updated the IP addresses. So then i did a genius move and deleted my target server from the AMP server and that’s where I’m stuck. I can’t add it back.

Actions taken to resolve so far:
I’ve tried clicking on “Pair new target” but it’s expecting to find the target server in target mode where i can enter a key.
I’ve tried restarting stuff and re-adding my target but got a scary message:

 CubeCoders AMP  💻amp@panel01  📁\~  ampinstmgr --RebindInstance
\[Info/1\] AMP Instance Manager v2.6.3.2 built 22/10/2025 11:12
\[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

> 192.168.4.226

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\]

here’s my target server setup:

 CubeCoders AMP  💻amp@minecraft01  📁\~  ampinstmgr status ADS01
\[Info/1\] AMP Instance Manager v2.6.4.2 built 10/12/2025 02:34
\[Info/1\] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Instance Name      │ Friendly Name    │ Module     │ IP              │ Port  │ Up
───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼───
ADS01              │ ADS01            │ ADS        │ 192.168.4.226   │ 8080  │
minecraftpaper0… │ minecraft pap… │ Minecraft  │ 0.0.0.0         │ 8081  │ ✓
paper0201          │ paper02          │ Minecraft  │ 0.0.0.0         │ 8082  │ ✓

 CubeCoders AMP  💻amp@minecraft01  📁\~  ampinstmgr -l
\[Info/1\] AMP Instance Manager v2.6.4.2 built 10/12/2025 02:34
\[Info/1\] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Instance ID        │ 0af58792-3a1a-44ab-a86b-660a9c9f7fa2
Module             │ ADS
Instance Name      │ ADS01
Friendly Name      │ ADS01
URL                │ http://192.168.4.226:8080/
Running            │ No
Runs in Container  │ No
Runs as Shared     │ No
Start on Boot      │ Yes
AMP Version        │ 2.6.3.2
Release Stream     │ Mainline
Data Path          │ /home/amp/.ampdata/instances/ADS01

Instance ID        │ 840c264f-59a5-465f-bfcb-ef067bb9b249
Module             │ Minecraft
Instance Name      │ minecraftpaper0101
Friendly Name      │ minecraft paper01
URL                │ http://127.0.0.1:8081/
Running            │ Yes
Runs in Container  │ No
Runs as Shared     │ No
Start on Boot      │ Yes
AMP Version        │ 2.6.3.2
Release Stream     │ Mainline
Data Path          │ /home/amp/.ampdata/instances/minecraftpaper0101

Instance ID        │ 849dbac7-c261-4966-8b1f-cee71415b722
Module             │ Minecraft
Instance Name      │ paper0201
Friendly Name      │ paper02
URL                │ http://127.0.0.1:8082/
Running            │ Yes
Runs in Container  │ No
Runs as Shared     │ No
Start on Boot      │ Yes
AMP Version        │ 2.6.4.0
Release Stream     │ Mainline
Data Path          │ /home/amp/.ampdata/instances/paper0201

Any help is appreciated.

Rebind your ADS instances back to 0.0.0.0. Rebinding them doesn’t do anything other than change the IP address, and doesn’t change any of the settings.

To get things paired:

  1. Make sure the Default Auth Server setting in the Controller has been updated to use the Controller’s new local IP address
  2. Start pairing a new target in the Controller
  3. Search “re-run” in the Target’s settings and press the re-run setup button
  4. Re-pair the Target

Now SSH into each target and do the following:
sudo su -l amp
ampinstmgr repairauth target http://put.controller.local.ip:8080
ampinstmgr stop ADS01
ampinstmgr reconfigure ADS01 +Core.Login.AuthServerURL http://put.controller.local.ip:8080
ampinstmgr start ADS01