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? In /mnt/user/appdata/mitchtalmadge-amp-dockerized/instances , what folders do you see? e.g. Main, Valheim01... 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). 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 ~10 mins. Thanks for your patience with this :)

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!

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!

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.

You did indeed save me a day of work, thank you for this solution. Using the new tailscale feature of Docker containers, I was also able to expose this privately on my tailscale network instead of giving it a LAN IP. This is working better for me than the Unraid implementation anyway. Probably not gonna go back to the old way even after it's fixed. Thanks!!

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:

It might be a port issue, can you show me your configuration for the container? Block out the password and license of course.

Hi everyone! V24 has been released! There is a very important data migration that needs to be completed BEFORE updating for people who are running these games: Satisfactory, ASKA, Saleblazers, or Sunkenland. Please view the release notes, which has instructions on what to do. People not running those games will be fine not running the migration, but I would prefer that everyone take the time to do it if possible. Thank you so much in advance for your patience with this. If you run into trouble you can post here or in this GitHub discussion. Thanks!!

Oh yay I’m glad it’s working! I used to put out a container update for every AMP update, but that was only cus I couldn’t get the built-in updater working. I eventually figured out how to make it work and so now I only push container updates when something is broken or new game dependencies are needed

It's supposed to update automatically on container restart, or can be done through the UI. Let me know if it isn't working!

I reseated all my various peripherals (SATA ports, internal USB header, M.2 slots, etc.) and recreated my Docker image. I've had no problems since then! I guess it was a loose connection. (I am still using the same USB drive as before, I guess there wasn't really any problems with it.) Thanks for the help.

Thank you @JorgeB, I'll try this out. Also, I believe my USB drive is a lemon. I ran Check Flash on it and it had a read error: I'm going to run a more thorough test to be sure. I probably need to find a new drive though. ---- Update: I ran more tests and didn't run into the error again. I am leaning towards that being a fluke. I'm going to try running Unraid again and see if the problem persists after a reboot. I did find a somewhat loose M.2 SATA adapter in my case which could have been part of the problem.

Good morning, I have been having some issues with Docker on my new Unraid (v6.11.5) build. I have resolved some of it, but I wanted to share my experience and get advice going forward. Build DetailsNo parity -- see next bullet. One 14TB HDD that I am transferring data onto from another computer. Once this is done I will move two more 14TB HDDs from that computer into this Unraid build, and use one of them as a parity disk. I am constantly transferring ~100MB/s of data into the Unraid build during the events outlined in this post. One 512GB SATA SSD to be used as cache. Ryzen 5 3600 CPU 32GB RAM (not ECC at the moment, but ECC is coming). Unraid is installed on a brand new Samsung BAR Plus 64GB USB 3.1 Flash Drive (MUF-64BE4/AM) ProblemSometimes when I try to install a docker container, the web UI hangs during download of the images, then starts throwing up the "500 Internal Server Error" page. After a while (~10 minutes) it will resolve itself and the UI loads again. During this time I can still SSH into the server, I can transfer files in and out, etc. without issues. This happened when installing plex, but not when installing SWAG. For my latest attempt, I tried to install pihole and the Unraid UI once again froze up and I could not open it up in another tab; I would get 500 Internal Server Error. It eventually came back up, but the Docker container was all sorts of messed up. I was getting errors such as "Error response from daemon: Failed to create btrfs snapshot: read-only file system" whenever trying to do anything with the container. I couldn't remove or re-create the container because of the "read-only file system." Fixing "read-only file system"I read somewhere here on the forums that the read-only problem can be a result of corruption when using btrfs (as I am) and the cache drive becomes full (as it did -- I accidentally filled it up with the mover). So I brought the array down, set minimum file sizes on the cache pool and the shares (30GB each), then brought the array back up. After this, the pihole docker image was working and the read-only messages were gone, but it had no way to edit the image. The UI told me that it believed the image was added manually (not via apps). I stopped and deleted the container + image, went back to the apps area, and re-downloaded/configured pihole. This time it worked with no issues and I have a working pihole instance. I believe this problem is fixed but I would like to hear feedback about whether this fix was "proper" or not. Fixing "500 Internal Server Error"I don't really know what causes the 500 internal server errors, or how to fix it. I don't believe they are related to the cache drive; they happened even when the cache drive was mostly empty. I am worried that it could be a bad USB drive, from what I have read on the forums, but I don't know how to verify that. Let me know what you think, or if more context would help. I greatly appreciate your time!

I'm glad to hear that it works. You can change back to the latest image now (mitchtalmadge/amp-dockerized) as I have pushed this patch to latest. Thanks!

Hello, if everyone experiencing the web UI problems could try out the following image, I think it will solve your problem: mitchtalmadge/amp-dockerized:staging-startonboot @xXMrZombie20Xx @CorneliousJD @synnc Thanks!