AMP Instance Manager Not Working After Update

OS Name/Version: Windows11 Pro

Product Name/Version: AMP PRO 2.6.0.6 20241120.1

Problem Description:

Cannot open Instance Manager GUI

Steps to reproduce:

Open Instance Manager
Get Error Message

Actions taken to resolve so far:
I logged into the instance manager(IM) and ran the update to the latest version. After running the update I was able to log in to the GUI but all of my instances were gone. I then went to the discord to receive support. After some assistance I was able to restore the instances JSON and the instances are all running in the background correctly. However I could no longer open the Instance Manager GUI. It seems to be in “Recovery Mode”, saying that AMP is not currently running. I confirmed in the services that it is in fact running and restarted the service to confirm. At this point I did a uninstall and reinstall of the instance manager. Still the same issue remains.

Follow this update guide here:

Sorry should have specified. This was posted in the discord and I followed the steps listed. Still having the issue.

Check that ampinstmgr version in CMD prints out v2.6.0.6
Then if that looks fine, you can start the ADS with ampinstmgr start ADS01

version confirmed and the ADS01 is already running it’s just like the GUI can’t see it

Run ampinstmgr lastlog ADS01 and see if the ADS’s port has changed away from 8080.
If you ran ampinstmgr repair in the process of updating the ports might just be a tad off
(that page you see is just cached browser page that shows when the browser doesn’t connect to the ADS)

Looks like it is 8084 for some reason. Can I change that or do I need to port forward the new port?

You should be able to run:
ampinstmgr stopall
then
ampinstmgr rebind ADS01 0.0.0.0 8080
Ignore the part where it says that you’ll need to fix auth, since you’re rebinding to return things to their expected default

THANK YOU!! That was driving me crazy. I’m in and the Instances are all fixed.

Also a note incase someone else has this problem I had to run the cmd in admin, otherwise it errors out.

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