Is AMP supported on Debian 13, and can we migrate safely from Debian 10?

Technical Support
1

OS Name/Version:
Debian 10 (Buster)

Product Name/Version:
AMP – ADS and Minecraft modules
Versions currently in use:

ADS: 2.6.3.0  
Minecraft instances: 2.5.0.10 / 2.5.0.12 / 2.6.0.6 / 2.6.3.0  
Release Stream: Mainline

Problem Description:
We are planning to migrate our full AMP installation from Debian 10/Buster to Debian 13/Trixie.
The official documentation still lists Debian 10 as supported, but Debian 10 is already end of life.
We would like to confirm whether AMP is tested and supported on Debian 13, and whether we can safely migrate all existing instances to the new OS.
We also want to confirm whether an additional licence purchase is required for the new server.

Steps to reproduce:
Step 1
Review official install guide at:
https://cubecoders.com/AMP/Install
(Only Debian 10 is listed as supported)

Step 2
Check current instance versions using:

ampinstmgr --ShowInstancesList

Step 3
Review migration guide:
https://discourse.cubecoders.com/t/configuration-with-application-deployment-how-to-migrate-amp-and-all-instances-to-new-server/19514
Plan to follow this procedure for migration from Debian 10 → Debian 13.

Actions taken to resolve so far:

  • Checked official documentation and release notes

  • Confirmed all existing instances are running on Mainline release stream

  • Reviewed migration steps from the forum

  • Searched Discourse for Debian 13 compatibility posts (none found)

  • Collected instance details and AMP versions for verification

2

AMP itself is fine on Debian 13. Couple of extra/changed packages required, but otherwise fine.

Most of the docker images have been changed to Debian 13, and they work fine too.

However, some servers do have issues with Debian 13, either because dependency packages have been deprecated or because Debian 13 has newer libraries that the servers can’t work with.

What instances are you migrating?

1 Like
3

BTW, the installation page says “Debian 10 or newer”.

And you won’t need a new licence to migrate.

4

Thanks, that’s very helpful.

We don’t use Docker — all instances run natively (tmux) and show “Runs in Container: No”.

Planned migration target: Debian 13 (Trixie). Instances to move:

  • ADS – 2.6.3.0 (Mainline)

  • Minecraft – 2.5.0.10 / 2.5.0.12 / 2.6.0.6 (x3) / 2.6.3.0 (x2), all Mainline

A couple of follow-ups:

  1. Since we’re non-Docker, are there any extra/changed packages you recommend installing on Debian 13 (eg. specific libssl/libicu/libstdc++/mono-runtime variants) to avoid startup/runtime issues?

  2. For Minecraft specifically, are there known incompatibilities on Debian 13 we should watch for (GLIBC/Java/OpenJDK versions, deprecated libs, etc.)?

Also thanks for confirming licence transfer is fine.

5

If you are installing fresh, the getamp install script will handle it for you.

If you are upgrading in place, after moving to Debian 13, run as root: getamp debian13upgrade

You will also need if upgrading in place to update your apt repos (Adoptium, Docker etc). You will also need to update the repo for CubeCoders: getamp addRepo will do that, but you should remove the old one too.

Minecraft will be fine. Assuming you are using the Adoptium repo for Java, Java will be fine (after updating the apt repo).

Though the minimum AMP version is now 2.6.2.8. You should update everything to the latest - no point having different versions, particularly versions that have API changes. There are also security issues in .NET 8 that affect previous versions.

1 Like
6

Thanks, this helps a lot.

Here are the extra details you asked for, along with our planned migration strategy.
We don’t use Docker — all instances run natively under tmux.

Current environment details

Java version (Adoptium/Temurin):

openjdk 21.0.5 (Temurin)

AMP install path:

/usr/bin/ampinstmgr → /opt/cubecoders/amp/

Apt repos:

/etc/apt/sources.list.d/ is empty

(So only default Debian repos are active right now.)

AMP systemd unit file:
(Standard service definition; nothing customised.)

tmux version:

tmux 2.8

Kernel:

4.19.x (Debian 10 stock kernel)

Size of .ampdata (migration payload):

~64 GB

Migration plan we intend to follow (Debian 10 → Debian 13)

Please confirm if this looks correct:

On the old Debian 10 server

  1. Upgrade AMP + all instances to meet the 2.6.2.8 minimum.

  2. ampinstmgr stopall

  3. systemctl stop ampinstmgr

  4. Backup the entire /home/amp/.ampdata folder.

On the new Debian 13 server

  1. Fresh install using getamp.sh.

  2. Run:

    getamp debian13upgrade

    to apply the Debian 13 package adjustments.

  3. Update all apt repos:

    • Add new Temurin repo

    • Add updated CubeCoders repo (getamp addRepo)

    • Remove any old Cubecoders repo file

  4. Stop ampinstmgr service.

  5. Replace .ampdata with our backup.

  6. Run:

    ampinstmgr fixperms

  7. Start the service again.

  8. As amp user, run:

    ampinstmgr reactivateall
ampinstmgr startall

We’ll also update Java from the new Adoptium repo before starting Minecraft servers.

Instances being migrated

  • ADS – 2.6.3.0

  • Minecraft – 2.5.0.10 / 2.5.0.12 / 2.6.0.6 (x3) / 2.6.3.0 (x2)

All are on the Mainline stream.

Please let me know if this migration workflow looks right, or if we should adjust anything before moving 64 GB of instances to the new Debian 13 server.

Thanks again for your guidance — really appreciate the help.

7

This reads like you are using AI - please don’t. Lots of excess verbiage…

As I said, if you are installing the new OS and AMP from scratch, all you need to do is install AMP, stop it, replace .ampdata, fix ownership if you didn’t use the amp user, reactivate the licence, start AMP. Simples

1 Like
8

Understood — I only used AI to format the details neatly.

I added the full steps mainly so others in the same situation can follow them. A major hosting company running AMP game server nodes is shutting down their Virtuozzo-based containers and asking customers to migrate to new servers, so many AMP users on that platform will be moving at the same time. Having the full process written out could help anyone else migrating from older Debian versions.

Thanks again for your guidance — the simplified steps you shared make our own migration much easier.

9

This post essentially covers the same thing, though a bit less shorthand xD: Migrating instances to a new machine - #8 by ThePotatoKing

1 Like
10

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