Product Name/Version: (Always use the full version number - not ‘Latest’)
Problem Description:
after update Currently running version 2.5.1 - 20240705.1 no longer possible to open Instances Manage
[10:19:46] [ADS:admin Activity/14] : Managed remote instance hardcore01 at http://127.0.0.1:8083/
[10:19:46] [Auth:admin Activity/14] : Authentication token for admin requested by ManageInstance on behalf of admin
AMP System user: Already exists
Instance Manager: Already installed
HTTPS setup: No
Install Docker: No
Install 32-bit libraries: Yes
Install Java: Yes
Ready to install AMP. Press ENTER to continue or CTRL+C to cancel.
*Step 2
ampinstmgr quickstart
[Info] An ADS instance has already been created! Starting that instead of re-running quickstart…
[Info] Starting Instance: ‘ADS01’
Can’t find custom attr constructor image: /opt/cubecoders/amp/plugins/ADSModule.dll mtoken: 0x0a00001e due to: Could not load file or assembly ‘SQLite-net, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’ or one of its dependencies.
[Info] Waiting
Step 3
ampinstmgr repair
[Info] AMP Instance Manager v2.4.6.6 built 05/10/2023 11:57
[Info] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info] No instances to import.
*Step 4
ampinstmgr upgradeall
[Info] AMP Instance Manager v2.4.6.6 built 05/10/2023 11:57
[Info] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info] Stopping Instance: ‘ADS01’
[Info] Stopping instance ADS01…
[Info] Requesting soft-stop…
[Info] Waiting for instance to stop…
[Info] Instance was shut down gracefully.
[Info] Instance ADS01 has stopped.
[Info] Upgrading instance ADS01
[Info] Upgrade successful
Can’t find custom attr constructor image: /opt/cubecoders/amp/plugins/ADSModule.dll mtoken: 0x0a00001e due to: Could not load file or assembly ‘SQLite-net, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’ or one of its dependencies.
[Info] Waiting for AMP instance to start…
[Notice] AMP instance ADS01 is now running.
(Reading database … 292018 files and directories currently installed.)
Preparing to unpack …/ampinstmgr_2.5.1_amd64.deb …
Unpacking ampinstmgr (2.5.1) over (2.4.6.6) …
Setting up ampinstmgr (2.5.1) …
CubeCoders AMP amp@ve763 ~ ampinstmgr upgradeall
[Info/1] AMP Instance Manager v2.5.1 built 05/07/2024 13:01
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Stopping instance ADS01…
[Info/1] Requesting soft-stop…
[Info/1] Waiting for instance to stop…
[Info/1] Instance was shut down gracefully.
[Info/1] Instance ADS01 has stopped.
[Info/1] Stopping instance hardcore01…
[Info/1] Requesting soft-stop…
[Info/1] Waiting for instance to stop…
[Info/8] Instance was shut down gracefully.
[Info/8] Instance hardcore01 has stopped.
[Info/8] Upgrading instance ADS01
[Info/7] Upgrade successful
[Info/7] Upgrading instance java01
[Info/7] Upgrade successful
[Info/7] Upgrading instance S7days01
[Info/7] Upgrade successful
[Info/7] Upgrading instance Eco01
[Info/7] Upgrade successful
[Info/7] Upgrading instance starserver01
[Info/7] Upgrade successful
[Info/7] Upgrading instance snow01
[Info/7] Upgrade successful
[Info/7] Upgrading instance thomasjava01
[Info/7] Upgrade successful
[Info/7] Upgrading instance ts3bot01
[Info/7] Upgrade successful
[Info/7] Upgrading instance hardcore01
[Info/7] Upgrade successful
[Info/7] Upgrading instance minetest01
[Info/7] Upgrade successful
[Info/7] Waiting for AMP instance to start…
[Notice/6] AMP instance ADS01 is now running.
[Info/6] Waiting for AMP instance to start…
[Notice/5] AMP instance hardcore01 is now running.
I’m having the same problem on Windows. Tried every type of update, tried removing and installing again. When pressing Manage it flashes and nothing happens on all instances
after that the web interface was automatically moved to another port by the system
[Info/5] You can browse to this instance at http://x.x.x.x:8082/
[Info/5] Instance started in new session. Run ‘ampinstmgr View ADS01’ to view this instances live output.
After your first solution not working I shutdown the machine. I now started it again to try your second solution and before doing anything I simply tried to manage an instance just to see and it’s working… Nothing like the old “have you tried to turn it off and on again”