-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
docker image pushed on 8/11 broke server #3045
Comments
Is your OPS actually an empty string? I'm not sure where it got such a strange username in the lookup URL You probably need to set |
Oh, I see you later changed your config snippet. Do you have a comma separated list of usernames or UUIDs for your OPS? |
Aha! When using
It needs to be
Better yet, I highly recommend using object syntax since it is much more robust and leverages YAML features, such as:
|
Thanks for the info. I understand about using object syntax, and I have updated my syntax. However, that was not the cause here. The issue was with the player's UUID. It looks like our UUIDs have changed, and after digging up my UUID and updating it in the config, things are working again. |
This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open. |
Describe the problem
I run several docker vanilla Java servers in my house, and when I tried to access them today, they weren't running. After a bit of digging, I found that a new image was pushed sometime on 8/11, which my automation picked up on 8/12 using Watchtower and deployed. I started seeing the error and didn't notice it until today.
Here is the log line where Watchtower updated the image, and it started to fail
time="2024-08-12T02:00:09-07:00" level=debug msg=Comparing local="sha256:403ffaa737586d302e980d292ddf2837cc1ab2293ca005bc47b716f852960eed" remote="sha256:f9cc420f60eda63fbe5d7f5621ba3d4efa4a13ae64a6a93399c2865294cb0586"
I reverted to
itzg/minecraft-server:latest@sha256:403ffaa737586d302e980d292ddf2837cc1ab2293ca005bc47b716f852960eed
and everything is working again.Container definition
Container logs
My hunch is this change broke it because I do have an OP list: cea839a
The text was updated successfully, but these errors were encountered: