-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated Unraid to 6.10.3 exsisting containers cannot launch #127
Comments
When updating unraid, I stopped the servers and shut down the containers before restarting unraid for the update. I'm guessing something in the perms is off but I don't know what? maybe needs an update to the app pushing out to tix the perms?? |
Update, making a new instance of Minecraft and moving the port over, and copying the files let me launch it but I think if Unraid is rebooted, I might face the same issue again with it not allowing me to boot the instance. Really unsure what is causing this permission issue? |
Can you post the logs of the container itself? |
AMP Logs:
|
Console logs:
|
AMPLOG 2022-06-15 14-34-06
|
I have tried to re-enter the license but that seems to have no effect? |
Huh, it says the instance is running but it can't connect... That's weird. I'll see if I can reproduce it on my server. For the license problem, did you set a static MAC address? Without one it will lose the license on each restart. |
I have set a static MAC address |
Rebooting AMP after adding the static MAC address looks to have broken the new test instances AMP Console Log for test instance:
|
making a new instance works fine still though |
Hey, got an issue trying to start up some containers on AMP installed on Unraid. getting this error when I try to start the instance of the minecraft server, any ideas?
![image](https://user-images.githubusercontent.com/19707286/173726444-0d29679e-6638-485c-bbd3-df87809f1744.png)
![image](https://user-images.githubusercontent.com/19707286/173726478-c15211eb-a7a9-4816-bdc5-0df53ac9b57e.png)
Tried to make a new Minecraft server container and it works fine, just the existing containers seem to error and are not allowed to launch??
The text was updated successfully, but these errors were encountered: