1 minute ago, RazorX said:

thank you for helping me, i have no idea why it's acting up, i have it fully port forwarded and working online with crafty4 and with crafty4 stopped and this started i just cannot get minecraft to see my server at all, whether that's using my dns address or local port.

also i did have it set to 8080 and just incase that was the issue i changed it to 8082 but that changed nothing.

You’re just missing the Minecraft port :) At the bottom of that page click on the button like “Add another Path, Port, …” and then set it to Port, with value 25565 in host, container, and default. Use TCP as the protocol. Like this:

1 hour ago, MitchTalmadge said:

You’re just missing the Minecraft port :) At the bottom of that page click on the button like “Add another Path, Port, …” and then set it to Port, with value 25565 in host, container, and default. Use TCP as the protocol. Like this:

ok will do, i didn't know i needed to add it on this as it wasn't part of the default config, i believe it was on crafty4, i will give that a try thanks.

I have just installed and got AMP up and running. Even got it externalised through Traefik for managing the instances.

After adding my first server and then applying the Ports to the Docker Container, I get 502 ERROR when trying to access using the domain via Traefik,

Any thoughts?

2 hours ago, MrLinford said:

I have just installed and got AMP up and running. Even got it externalised through Traefik for managing the instances.

After adding my first server and then applying the Ports to the Docker Container, I get 502 ERROR when trying to access using the domain via Traefik,

Any thoughts?

FIXED: Had to add a label for Traefik to use port 8080. It was picking the first TCP port in numeric order:

`traefik.http.services.amp.loadbalancer.server.port`

This may be specific to AMP, and not the docker, but is there a way to prevent an instance from overwriting its .kvp files on update? Specifically the "GenericModule.kvp" file is overwritten with a generic version.

For context I changed the "WakeupMode" value to "OnUDPPacket" so the Steam query port doesn't prevent my Valheim server from sleeping. If I stop the server, update this value, then start the server it sticks. If the instance is updated e.g., when the game updates, it wipes it out.

13 hours ago, Zilonis said:

This may be specific to AMP, and not the docker, but is there a way to prevent an instance from overwriting its .kvp files on update? Specifically the "GenericModule.kvp" file is overwritten with a generic version.

For context I changed the "WakeupMode" value to "OnUDPPacket" so the Steam query port doesn't prevent my Valheim server from sleeping. If I stop the server, update this value, then start the server it sticks. If the instance is updated e.g., when the game updates, it wipes it out.

That's a good question! I am not sure. I will say that the container doesn't do anything specific regarding kvp files so this must be default AMP behavior. I tried to find a Wakeup Mode setting in the Valheim config on the UI and I don't see it, I wonder why that was not included in the UI. Maybe it was forgotten? Anyway, I'll try to dig into why the kvp keeps getting overwritten.

11 hours ago, MitchTalmadge said:

That's a good question! I am not sure. I will say that the container doesn't do anything specific regarding kvp files so this must be default AMP behavior. I tried to find a Wakeup Mode setting in the Valheim config on the UI and I don't see it, I wonder why that was not included in the UI. Maybe it was forgotten? Anyway, I'll try to dig into why the kvp keeps getting overwritten.

I assume they haven't updated the servers config UI since initially adding Valheim support to AMP. There's a lot of game-specific settings missing that you can find in the config files.

What's odd is other .kvp files aren't overwritten. I changed "SFTP.SFTPEnabled" in "FileManagerPlugin.kvp" to "False" to disable SFTP and that sticks after an instance update. I haven't seen a UI option for that either.

 Has anyone managed to get the discord bot plugin working with this? I went through the setup script and bot instructions with no issue and the ports are all forwarded but I always get an "application did not respond" error when running the commands via discord
https://github.com/winglessraven/AMP-Discord-Bot
Running ARK survival evolved with it and the only notable logs I see:

[11:29:19] [Loader Info/1]        : Discord Bot Activated
[11:29:19] [Loader Info/1]        : Attempting Discord connection...
[11:29:19] [Discord Info/1]       : 01:29:19 Discord     Discord.Net v1.0.0 (API v10)
[11:29:20] [System Info/1]        : Bot successfully connected.
[11:29:20] [Discord Info/10]      : 01:29:20 Gateway     Connecting
[11:29:20] [System Info/1]        : /home/amp/.ampdata/instances/ARKAberration01/WebPanel-ARKAberration01
[11:29:20] [Core Warning/1]       : Schedule trigger 616c7c22-e552-4111-8236-4eefcf05e87e has a mismatched ID!
[11:29:20] [Discord Info/9]       : 01:29:20 Gateway     Connected
[11:29:21] [System Info/9]        : Base command for bot: amp
[11:29:21] [Discord Info/9]       : 01:29:21 Gateway     Ready
...
[11:29:41] [System Error/7]       : Source RCON failed to connect:
Connection refused.
[11:29:41] [RCON Info/13]         : Source RCON disconnecting...
[11:29:42] [RCON Info/13]         : Source RCON disconnected
[11:29:47] [System Error/7]       : Source RCON failed to connect:

Not sure what's causing the mismatched ID but the RCON stuff should be fine, I double checked and the ports are forwarded correctly so I'm not sure what else to do

Edited February 16Feb 16 by frostymm

I rebooted Unraid today and when AMP came up it upgraded to 2.7.0.0. My game servers were up and running and everything looked good. Well, I had to make some tweaks in Unraid and restart my containers again. This time AMP came up as 2.6.4.2 and thinks it's a factory default instance. Can't login, no game servers are up, etc. I thought I would post here to share the experience and then also ask what the best procedure is to restore my config? I have appdata backups, but most of the data seems to be there still on my file system, AMP appears to have created a new Instance called ADS01 and I now can't login to the UI. I think my config might all live in the Main instance and then each game server has its folder still and they all look good from a quick glance, but not too sure right now. Anyway, I didn't see anything on the github issues page or anywhere else I have searched, so I figured I would start here. Thanks for any help you can suggest to me.

Edited March 6Mar 6 by Luminance1364

1 hour ago, Luminance1364 said:

I rebooted Unraid today and when AMP came up it upgraded to 2.7.0.0. My game servers were up and running and everything looked good. Well, I had to make some tweaks in Unraid and restart my containers again. This time AMP came up as 2.6.4.2 and thinks it's a factory default instance. Can't login, no game servers are up, etc. I thought I would post here to share the experience and then also ask what the best procedure is to restore my config? I have appdata backups, but most of the data seems to be there still on my file system, AMP appears to have created a new Instance called ADS01 and I now can't login to the UI. I think my config might all live in the Main instance and then each game server has its folder still and they all look good from a quick glance, but not too sure right now. Anyway, I didn't see anything on the github issues page or anywhere else I have searched, so I figured I would start here. Thanks for any help you can suggest to me.

Ty for letting me know! Most likely what happened is for some reason it could not find the Main instance and fell back to creating the ADS01 instance (new name for “Main” since last update to conform with how AMP does things in a VM). I’m unsure why that happened but I’ll try to quickly reproduce it and get back to you with a fix. For now hang onto the backups. Thanks!

3 minutes ago, MitchTalmadge said:

Ty for letting me know! Most likely what happened is for some reason it could not find the Main instance and fell back to creating the ADS01 instance (new name for “Main” since last update to conform with how AMP does things in a VM). I’m unsure why that happened but I’ll try to quickly reproduce it and get back to you with a fix. For now hang onto the backups. Thanks!

BTW, did you change any settings in the template between the last time it worked and now? Like volumes or something? If you can post or DM me your config with private stuff blocked out that could also help me. It’s okay if not. Thank you!

BTW, did you change any settings in the template between the last time it worked and now? Like volumes or something? If you can post or DM me your config with private stuff blocked out that could also help me. It’s okay if not. Thank you!

Yeah, sure thing! No worries. I hope I got all of the sensitive data. Here are screenshots.

I did not change anything in AMP to my knowledge. The change I was making was removing some VLANs that are no longer needed and then adding a new one for a new project. None of which were the network or VLAN that AMP uses.

2 hours ago, Luminance1364 said:

Yeah, sure thing! No worries. I hope I got all of the sensitive data. Here are screenshots.

I did not change anything in AMP to my knowledge. The change I was making was removing some VLANs that are no longer needed and then adding a new one for a new project. None of which were the network or VLAN that AMP uses.

Thanks! Your config looks fine. I tried creating a 2.6.4.2 instance and upgrading to 2.7.0.0, but it didn't cause the same problem you had. I wasn't able to reproduce it. However, we can probably still fix it. Can you answer these for me?

1. In /mnt/user/appdata/mitchtalmadge-amp-dockerized/instances , what folders do you see? e.g. Main, Valheim01...

2. Inside /mnt/user/appdata/mitchtalmadge-amp-dockerized/instances.json , search for InstanceName, and let me know all the ones you can find.

   • For example: "InstanceName": "Main", "InstanceName": "Valheim01", etc..

   • In theory you should see the names of all your games in there.. If not, they might be in one of the backups; see (3).

3. Do you see any backup instances.json files in that same folder? For example, instances.json-20260209.bak or something similar.

   • If your instances.json file doesn't contain your games, it's possible that these backup files do. You can look for the same InstanceName lines.

Hopefully this might be as simple as renaming a few things to ADS01. I'm also preparing a new release of the container that uses the latest internal AMP code just in case the current code is incompatible with 7.0.0.0. This update should be out in the next half hour. You'll have to click "check for updates" on Docker's page.

Thanks for your patience with this :)

Edited March 7Mar 7 by MitchTalmadge

Thanks! Your config looks fine. I tried creating a 2.6.4.2 instance and upgrading to 2.7.0.0, but it didn't cause the same problem you had. I wasn't able to reproduce it. However, we can probably still fix it. Can you answer these for me?

1. In /mnt/user/appdata/mitchtalmadge-amp-dockerized/instances , what folders do you see? e.g. Main, Valheim01...

2. Inside /mnt/user/appdata/mitchtalmadge-amp-dockerized/instances.json , search for InstanceName, and let me know all the ones you can find.

   • For example: "InstanceName": "Main", "InstanceName": "Valheim01", etc..

   • In theory you should see the names of all your games in there.. If not, they might be in one of the backups; see (3).

3. Do you see any backup instances.json files in that same folder? For example, instances.json-20260209.bak or something similar.

   • If your instances.json file doesn't contain your games, it's possible that these backup files do. You can look for the same InstanceName lines.

Hopefully this might be as simple as renaming a few things to ADS01. I'm also preparing a new release of the container that uses the latest internal AMP code just in case the current code is incompatible with 7.0.0.0. This update should be out in the next half hour. You'll have to click "check for updates" on Docker's page.

Thanks for your patience with this :)

I really appreciate your attentive assistance! Thank you so very much!

I saw the update on the docker this morning, so I just tried it for fun. It looks like it moved to 2.7 again, but things are a touch different, from what I can see in the logs.

[Info/1] Upgrading instance ADS01

[Info/9] Upgrade successful

Starting AMP...

[Info/1] AMP Instance Manager v2.7 built 05/03/2026 00:25

...

[Notice/8] AMP instance ADS01 is now running.

AMP Started!

AMP is now running. Logs can be viewed through AMP web UI or at ampdata/instances/Main/AMP_Logs

So the way I read that is the new default instance of ADS01 is running, but it is writing into the Main instance. So it's kind of crossing the wires. Anyway, here is what I have done.

Answers to your questions:

1. ADS01, 4 x Minecraft servers, Main, 1 x Factorio server and 1 x Terraria server.
2. There is just 1: "InstanceName": "ADS01"
3. Yes, lots, 99 in fact. Dating all the way back to 2024. So that's great. The last one that looks good is: instances.json-20260301.bak.

Here is what I did. I renamed the current instances.json to instances.json-20260307.2.bak. Then I copied instances.json-20260301.bak and renamed it instances.json. Then I moved the instances\ADS01 folder to my workstation, so it's off of the server. Since I suspect that one to be the problematic one. Now the instances.json file matches the file system. Then I turned my container on and it did the same thing. It created an ADS01 folder and started a factory instance. I removed the new instances.json, re-copied the last known good instances.json, edited the file to change Main to ADS01, deleted the new ADS01 and then copied the old Main and renamed it ADS01. I then had to hop in the CLI and run 'su -l amp' and then 'ampinstmgr reactivate Instance_Name_01' for each server. All of my servers are up now, hooray! I will try restarting the container at another time. I don't have time to do much else today.

I appreciate your support! Thanks so much. AMP really is a great tool, so thanks for doing the work to make it available to us all on Unraid.

Having an issue where I cannot connect to the WebUI at all from any device. It was working a week or so ago the last time I logged in but not I cannot access it. Logs seem to show it starting and running correctly and I haven't changed any settings that would mess with this.

Getting the following error when trying to install via docker containers. I don't know if this is intended behaviour.

Create Instance Failed: This instance either requires or has been configured to use containers, but Podman was not found on the system.

vbnet

Changing setting ADSModule.Defaults.PropogateRepos to True

Changing setting ADSModule.Defaults.ContainerManager to 0

Create Instance Failed: This instance either requires or has been configured to use containers, but Podman was not found on the system.

Changing setting ADSModule.Defaults.ContainerManager to 2

Create Instance Failed: This instance either requires or has been configured to use containers, but Podman was not found on the system.

Changing setting ADSModule.Defaults.UseDocker to False

Changing setting ADSModule.Defaults.ContainerManager to 0

Updating remote source CubeCoders/AMPTemplates:main

Updating existing remote source https://github.com/CubeCoders/AMPTemplates.git...

No stash entries found.

Non-managed instances exist, autoconfigure cannot guarantee that the configuration is valid!

Waiting for AMP instance to start...

AMP instance Astroneer01 is now running.

Managed remote instance Astroneer01 at http://127.0.0.1:8081/

Authentication token --- for sekhujin requested by ManageInstance on behalf of sekhujin

Slow method invocation: ManageInstance took 6089ms to complete.

Slow response: ADSModule.ManageInstance took 6090ms to complete.

Slow method invocation: Login took 5050ms to complete.

Slow response: Core.Login took 5051ms to complete.

Managed remote instance Astroneer01 at http://127.0.0.1:8081/

Slow method invocation: Servers took 11808ms to complete.

Slow response: ADSModule.Servers took 12772ms to complete.

Authentication token ---- for sekhujin requested by ManageInstance on behalf of sekhujin

Slow method invocation: ManageInstance took 8174ms to complete.

Slow response: ADSModule.ManageInstance took 8175ms to complete.

LIM - Failure to make API call to Astroneer01 (Timed out): The request was canceled due to the configured HttpClient.Timeout of 30 seconds elapsing.

Slow method invocation: Servers took 30003ms to complete.

Slow response: ADSModule.Servers took 30003ms to complete.

LIM - Failure to make API call to Astroneer01 (Timed out): The request was canceled due to the configured HttpClient.Timeout of 30 seconds elapsing.

Slow method invocation: Servers took 30002ms to complete.

Slow response: ADSModule.Servers took 30002ms to complete.

Slow method invocation: Login took 31619ms to complete.

Slow response: Core.Login took 31620ms to complete.

Slow method invocation: Login took 10032ms to complete.

Slow response: Core.Login took 10033ms to complete.

First image is when trying to install Abiotic Factor. The 2nd deployment log is when trying to install Astroneer. Thanks

Edited April 14Apr 14 by korefuji

On 4/14/2026 at 4:52 AM, korefuji said:

Getting the following error when trying to install via docker containers. I don't know if this is intended behaviour.

Create Instance Failed: This instance either requires or has been configured to use containers, but Podman was not found on the system.

vbnet

Changing setting ADSModule.Defaults.PropogateRepos to True

Changing setting ADSModule.Defaults.ContainerManager to 0

Create Instance Failed: This instance either requires or has been configured to use containers, but Podman was not found on the system.

Changing setting ADSModule.Defaults.ContainerManager to 2

Create Instance Failed: This instance either requires or has been configured to use containers, but Podman was not found on the system.

Changing setting ADSModule.Defaults.UseDocker to False

Changing setting ADSModule.Defaults.ContainerManager to 0

Updating remote source CubeCoders/AMPTemplates:main

Updating existing remote source https://github.com/CubeCoders/AMPTemplates.git...

No stash entries found.

Non-managed instances exist, autoconfigure cannot guarantee that the configuration is valid!

Waiting for AMP instance to start...

AMP instance Astroneer01 is now running.

Managed remote instance Astroneer01 at http://127.0.0.1:8081/

Authentication token --- for sekhujin requested by ManageInstance on behalf of sekhujin

Slow method invocation: ManageInstance took 6089ms to complete.

Slow response: ADSModule.ManageInstance took 6090ms to complete.

Slow method invocation: Login took 5050ms to complete.

Slow response: Core.Login took 5051ms to complete.

Managed remote instance Astroneer01 at http://127.0.0.1:8081/

Slow method invocation: Servers took 11808ms to complete.

Slow response: ADSModule.Servers took 12772ms to complete.

Authentication token ---- for sekhujin requested by ManageInstance on behalf of sekhujin

Slow method invocation: ManageInstance took 8174ms to complete.

Slow response: ADSModule.ManageInstance took 8175ms to complete.

LIM - Failure to make API call to Astroneer01 (Timed out): The request was canceled due to the configured HttpClient.Timeout of 30 seconds elapsing.

Slow method invocation: Servers took 30003ms to complete.

Slow response: ADSModule.Servers took 30003ms to complete.

LIM - Failure to make API call to Astroneer01 (Timed out): The request was canceled due to the configured HttpClient.Timeout of 30 seconds elapsing.

Slow method invocation: Servers took 30002ms to complete.

Slow response: ADSModule.Servers took 30002ms to complete.

Slow method invocation: Login took 31619ms to complete.

Slow response: Core.Login took 31620ms to complete.

Slow method invocation: Login took 10032ms to complete.

Slow response: Core.Login took 10033ms to complete.

First image is when trying to install Abiotic Factor. The 2nd deployment log is when trying to install Astroneer. Thanks

If you really want to use CubeCoders AMP on Unraid to be honest a docker container is by far the worst way to do it. It really needs its on system. If you must run it on Unraid do so within a Debian VM. Trying to run containerized game instances inside an AMP Docker container that’s the problem. You’re stacking container runtimes on top of each other. Im not saying you can't get it running just saying it's wrong way of going about doing it.

4 hours ago, PikkonMG said:

If you really want to use CubeCoders AMP on Unraid to be honest a docker container is by far the worst way to do it. It really needs its on system. If you must run it on Unraid do so within a Debian VM. Trying to run containerized game instances inside an AMP Docker container that’s the problem. You’re stacking container runtimes on top of each other. Im not saying you can't get it running just saying it's wrong way of going about doing it.

Understood, but i can't even get a non containerised version working of Astroneer. And Abiotic Factor is recommended as a Container, so Im just sharing my experience. If they work that'd be enough but I'm facing issues right now as above.

Hello,

Is there a way to make the folder be owned by "nobody" user "99:100". I can usually get some containers to do this by using the "--user 99:100" option, but this fails to start the container.

Sometimes I have to link the /etc/passwd file from unraid host to the container and that sometimes works with the --user option.

The current owner is an account I used only for local SMB Share access and don't want it to own a docker share.

Can a PUID 99 GUID 100 be added as an environmental variable to make it the owner of the folder?

Thanks,

On 4/17/2026 at 12:51 PM, zer0ish said:

Hello,

Is there a way to make the folder be owned by "nobody" user "99:100". I can usually get some containers to do this by using the "--user 99:100" option, but this fails to start the container.

Sometimes I have to link the /etc/passwd file from unraid host to the container and that sometimes works with the --user option.

The current owner is an account I used only for local SMB Share access and don't want it to own a docker share.

Can a PUID 99 GUID 100 be added as an environmental variable to make it the owner of the folder?

Thanks,

Unraid terminal chown -R 99:100 /mnt/user/appdata/your-container If its permissions issue then chmod -R 775 /mnt/user/appdata/your-container

14 hours ago, PikkonMG said:

Unraid terminal chown -R 99:100 /mnt/user/appdata/your-container If its permissions issue then chmod -R 775 /mnt/user/appdata/your-container

Yeah I've already done that. Once the container starts again it reverts back to whatever the container wants to use, amp (1000) amp (1000). Which is the same number as my local SMB share account. I think the image needs to be build with env variables to use 99:100 for folder ownership.

For unraid the best practice is to use the nobody user/group.

23 hours ago, zer0ish said:

Yeah I've already done that. Once the container starts again it reverts back to whatever the container wants to use, amp (1000) amp (1000). Which is the same number as my local SMB share account. I think the image needs to be build with env variables to use 99:100 for folder ownership.

For unraid the best practice is to use the nobody user/group.

Figured I'd take a look at the github and found there is a UID and GID variable that can be set. Changes it to UID 99 GID 100 and now everything is owned by nobody. Guess I'm just used to seeing the GUID and PUID variable. I'm good now. This container actually seems to be working better then installing a VM and AMP using their install steps.

Since 2.7.2.0 only about 10 instances start/activate, the rest fails with "error 135".

tried the basic things like reconfiguring with the license but it does not work, anyone else able to find a solution to this yet?

"Couldn't reconfigure the instance: AMP configuration failed with return code 135"

5 hours ago, Entxawp said:

Since 2.7.2.0 only about 10 instances start/activate, the rest fails with "error 135".

tried the basic things like reconfiguring with the license but it does not work, anyone else able to find a solution to this yet?

"Couldn't reconfigure the instance: AMP configuration failed with return code 135"

Having the same issue. Except I can only get 9 to run at a time

7 hours ago, Entxawp said:

Since 2.7.2.0 only about 10 instances start/activate, the rest fails with "error 135".

tried the basic things like reconfiguring with the license but it does not work, anyone else able to find a solution to this yet?

"Couldn't reconfigure the instance: AMP configuration failed with return code 135"

Running AMP within docker is not a supported setup. Run it in a VM or on a dedicated machine. Its been a min since I bought licence which one do you have?

Edited April 25Apr 25 by PikkonMG