AMP Controller caches wrong Target IP even after changing "Target URL"

[EpicLPer]

Operating System

Ubuntu 22.04.4 LTS

AMP Version and Build Date

2.6.4.2 - 20251210.2

AMP Release Stream

Mainline

I confirm that

• I have searched for an existing bug report for this issue.
• I am using the latest available version of AMP.
• my operating system is up-to-date.

Intended Action

Trying to manage a Target from the Controller via the "Manage" button

Expected Behaviour

Manage website opening

Actual Behaviour

Page doesn't load, browser console shows Unable to manage instance AMPServer1 - Failed to setup API.

Reproduction

These are condensed down steps how I've set up an AMP server in my homelab which later got moved to its own firewall zone.

1. Install new AMP Target on internal network
2. Authenticate with AMP Controller via the internal hostname/IP
3. After initial configuration move Target to new firewall zone/VLAN (aka. the Target gets a new IP afterwards), or change the IP/hostname of the target
4. Edit the "Target URL" on the Controller to the new IP/Hostname/External Address

The Target is still visible on the Controller and can be refreshed without issues, even Instances on the Target can be created and managed without issues.
But clicking "Manage" on the Target shows this in the browser logs:
Unable to manage instance AMPServer1 - Failed to setup API.
The AMP Controller logs show the following error: 21:01:33 RIM for AMPServer1 - Failure to make API call to ADS01: No route to host (10.0.0.35:8080)

This means the Controller still has the old IP cached despite everything else already using the now new and correct Target URL. This gets fixed once the "ADS01" instance on the Controller gets stopped and started once.

[p0t4t0sandwich]

Did you try clearing your browser cache before restarting the Controller? Could be that your browser cached the URL and it's not the Controller's backend at fault.

Not to say the Controller isn't holding the wrong address in memory, but it would rule out a browser-cache scenario.

[EpicLPer]

Did you try clearing your browser cache before restarting the Controller? Could be that your browser cached the URL and it's not the Controller's backend at fault.

Not to say the Controller isn't holding the wrong address in memory, but it would rule out a browser-cache scenario.

I did do Ctrl + Shift + R a few times, but not a full browser close/reopening. However it did work after restarting the Controller with the same browser still open and only refreshing once, my bet is it wasn't the browser but can't be 100% sure 😅