Replies: 6 comments 6 replies
-
|
It's a (newly) known issue that has been caused by Mojang's release publishing. |
Beta Was this translation helpful? Give feedback.
-
you can fix it specifying the version docker run -d -it --name bds-flat-creative or if you're using docker-compose specify VERSION in your docker-compose.yml |
Beta Was this translation helpful? Give feedback.
-
|
I tried to the do the a rollback to the "previous" version but haven't had any luck. I've even gone as far as to create a new container. Am I doing something wrong? I've tried in both in CLI and using Portainer. |
Beta Was this translation helpful? Give feedback.
-
|
@csellers85 this just now worked for me: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the clarification, I found in portainer where to edit that variable so it would pull the previous version. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I am once again getting "outdated client" message. Previously I was able to specify a particular dot release and get the connection going. However, this afternoon once again I get the error with the same server that was previously working. I guess the client was updated again and again a mismatch. I did get the latest container from dockerhub and switch my make file to version=Previous and version=Latest, and neither of these worked. |
Beta Was this translation helpful? Give feedback.
-
|
Anyone know how to get that version? I looked over on Fandom, but couldn't figure how to locate. Is it possible to get it from an info screen somewhere or a / command on the console in Minecraft client? Thanks, the server has been awesome and fun to play on for myself and kids inside our network! |
Beta Was this translation helpful? Give feedback.
-
|
I'm a bit confused. The startup automatically gets that latest version. If you want to see specifically what it used then it is reported in the logs. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for being dense. After working for a while, Minecraft for Windows again updated, and again I cannot connect to a world in my ITZG container. The error is "cannot connect to outdated server". So, the "latest" image is serving up a version that is outdated according to the Minecraft client. I'm not sure but I think the automatically latest version on startup might only apply to non-bedrock servers? At least that might be implied by the readme. You mentioned logs - I don't see any logs in my host machine directory dedicated to this container (volume) and if I do docker exec -it bash and look around, there are no *.log files. I did also look up a server.properties flag that should maybe make some log files, "content-log-file-enabled=true" but for whatever reason the container failed to start with this property set. |
Beta Was this translation helpful? Give feedback.
-
|
I just needed to restart my container today to get the latest that Minecraft can connect to again. |
Beta Was this translation helpful? Give feedback.
-
|
Good point @DominusExult . The auto-version lookup is only performed at container startup, so it is required to restart the container to have it check for and download updates. On a non-Desktop system that would be BTW, to see the container logs use |
Beta Was this translation helpful? Give feedback.
-
Get message "outdated client" when attempting to connect to my server. 1000 posts on the web say this is because, duh, the client is outdated, but also that it should be automatically updated on Windows (11).
So, I go through the rigamarole of finding my right windows login and reinstall with the latest version. MS does not make this easy! However, same error. Updated the latest bedrock server image here, and still same condition. Anyone have any other troubleshooting tips?
Beta Was this translation helpful? Give feedback.
All reactions