Update Failure with ARK: Survival Ascended - Instance update failure

System Information

Field Value
Operating System Linux - Debian GNU/Linux 13 on x86_64
Product AMP ‘Phobos’ v2.6.4.2 (Mainline)
Virtualization ProxmoxLXC
Application ARK: Survival Ascended
Module GenericModule
Running in Container No
Current State Stopped

Problem Description

Issue

I’m getting an issue when opening an instance, it opens up in a new tab and then gives me an error about the versions not matching.

The specific error is:

The AMP frontend that has been loaded (v2.6.5.2) does not match the backend (v2.6.4.2). Please clear your browser cache (or force reload with CTRL+F5) as well as any upstream proxy caches.

When looking at the status of system. I do see there is a mismatch in the versioning of the tools and the application version.

Application Version 2.6.5.2
Codename Phobos
Tools Version 2.6.4.2
Release Stream Mainline
Build Spec Release
I am trying to start an Ark ASE instance if that makes a difference

Reproduction Steps

  • Open AMP UI
  • Run the upgrade this instance
  • Open a game instance

Run as root: getamp update

OK, that got the versions the same at least. Still having the issue though when opening the Ark instance. I have also tried to perform the update on the instance (via the instances page) and the logs seem to be clean.

—————-Logs———————-
Upgrading instance HouseMareArkSA01
19:11:04
debian: Pulling from cubecoders/ampbase
Digest: sha256:9ecc9d4ec7194eec6097aa364683b778c6a1dc76516a5af2c57f1ac64dbb90dc
Status: Image is up to date for cubecoders/ampbase:debian

docker.io/cubecoders/ampbase:debian

Refreshing instance config for HouseMareArkSA01 with source CubeCoders-AMPTemplates-main
19:11:05
842ad261aa73b83d88570d945a5cd4d1785593257f8cbe06e21d7e46de31cbb5
—————————-

The issue is still present even when trying it in incognito mode.

Maybe to add to this, the call to:

https://redacted/API/ADSModule/Servers/1d9649f2/API/Core/GetModuleInfo returns an old result set it would seem.

Check on the command line what version is reported:

ampinstmgr info ADS01
ampinstmgr info HouseMareArkSA01

If that shows the right versions, then it is a browser cache issue (or other cache issue, eg if you proxy via Cloudflare)

The versions are the latest on both those two commands, however it’s still not getting back the correct response from the API call. This is not a caching issue as I ran a curl on local host and still got the incorrect version in the json payload for ARK

curl -H "Content-Type: application/json" -H "Accept: application/json" --request POST --data '{"SESSIONID":"8fcdc286-54d2-49c9-8f0f-0ac7936d984e"}' http://127.0.0.1:8080/API/ADSModule/Servers/1d9649f2/API/Core/GetModuleInfo

curl response

{"Name":"Generic Module","Author":"CubeCoders Limited","AppName":"ARK: Survival Ascended","SupportsSleep":false,"LoadedPlugins":["GenericModule","FileManagerPlugin","LocalFileBackupPlugin","AnalyticsPlugin","steamcmdplugin"],"AMPVersion":"2.6.4.2","AMPBuild":"20251210.2","ToolsVersion":"2.6.4.2","APIVersion":"2.6.4.2","VersionCodename":"Phobos","Timestamp":"10/12/2025 02:33","BuildSpec":"Mainline","Branding":{"DisplayBranding":false,"PageTitle":"Provider Page Title Not Set","CompanyName":"","WelcomeMessage":"","BrandingMessage":"","ShortBrandingMessage":"PoweredByAMP","URL":"","SupportURL":"","SupportText":"","SubmitTicketURL":"","LogoURL":"","BackgroundURL":"","SplashFrameURL":"","ForgotPasswordURL":"","HostedAnalyticsTag":""},"Analytics":false,"AnalyticsTag":"","FeatureSet":["RunAMP","LTSBuilds","CustomBranding","SSOLogins","Templating","SharedRoles","ControllerTargetMode","Analytics","SelfAssignedInstances"],"InstanceId":"1d9649f2-bb33-4fef-a40b-967b27ceeb5e","InstanceName":"HouseMareArkSA01","FriendlyName":"HouseMareArkSA","EndpointURI":"0.0.0.0:7777","PrimaryEndpoint":"0.0.0.0:7777","ModuleName":"GenericModule","IsRemoteInstance":true,"DisplayBaseURI":"","RequiresFullLoad":false,"AllowRememberMe":true,"BasePort":8081,"IsOIDCEnabled":false,"OIDCProviderFriendlyName":""}

Output of the info commands

[Info/1] AMP Instance Manager v2.6.5.2 built 28/01/2026 16:01
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Instance ID        │ 077a70c2-7448-4759-98d2-a2aecc815145
Module             │ ADS
Instance Name      │ ADS01
Friendly Name      │ ADS01
URL                │ http://127.0.0.1:8080/
Running            │ Yes
Runs in Container  │ No
Runs as Shared     │ No
Start on Boot      │ Yes
AMP Version        │ 2.6.5.2
Release Stream     │ Mainline
Data Path          │ /home/amp/.ampdata/instances/ADS01
[Info/1] AMP Instance Manager v2.6.5.2 built 28/01/2026 16:01
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Instance ID        │ 1d9649f2-bb33-4fef-a40b-967b27ceeb5e
Module             │ GenericModule
Instance Name      │ HouseMareArkSA01
Friendly Name      │ HouseMareArkSA
URL                │ http://127.0.0.1:8081/
Running            │ No
Runs in Container  │ Yes
Runs as Shared     │ No
Start on Boot      │ No
AMP Version        │ 2.6.5.2
Release Stream     │ Mainline
Data Path          │ /home/amp/.ampdata/instances/HouseMareArkSA01

So, Because I can’t post a workaround to this issue until someone else responds, I will just post it here.

On the Ark instance, go to the Run in docker settings. Then toggle that switch and save. The system may want to restart the backend. After that, revert the switch to the original settings and save. It seems that during the move/recreation of the backend, it does get updated.