Update Failure with Minecraft - Minecraft Java stopped working after update

Technical Support
,
1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 13 on x86_64
Product AMP ‘Deimos’ v2.7.0.0 (Mainline)
Virtualization Podman
Application Minecraft
Module MinecraftModule
Running in Container Yes
Current State Ready

Problem Description

Issue

The Console is currently displaying the following error many times: “```vbnet
Error: LinkageError occurred while loading main class net.minecraft.bundler.Main
java.lang.UnsupportedClassVersionError: net/minecraft/bundler/Main has been compiled by a more recent version of the Java Runtime (class file version 69.0), this version of the Java Runtime only recognizes class file versions up to 65.0”. I’ve restored an earlier backup, and it is running, but this error is displayed continuously. How would I fix this?

Reproduction Steps

  • Created the minecraft server several weeks ago.
  • Recently clicked Update.
  • Just checked today, and it was not running, stating an error, and to check logs.
  • Restored to a backup from a few days ago, this did not fix it.
  • Used an even earlier backup, and this did start, but with errors.

Update:

I figured it out. Within the AMP console, click the ‘pen’ icon (Edit Settings), then into the Container Settings tab. Mine is configured for ‘Run in Container’. I changed the ‘Container Image’ from ‘docker.io/cubecoders/ampbase:java’ to ‘docker.io/cubecoders/ampbase:java-25’. Once all settings were saved, I clicked to ‘Update Instance’ from the main Local Instances screen again, and Minecraft started fine. The problem is that the ‘:java’ container is running an older version of Java, and the latest Minecraft server requires a newer version. ‘:java-25’ contains a newer version of Java that works with this newer Minecraft version.

I hope this helps someone.

4 Likes
2

Hi there,

Many thanks for the guidance on resolving this issue with Minecraft - I had updated mine here and kept hitting the same error.

Great Stuff!

Many thanks, Anthony

3

Hi, I’m having the same problem and was following your troubleshooting steps, but when I try to save the configuration, I get the following error in the log: “Permission denied while trying to connect to the Docker API at unix:///var/run/docker.sock
Failed to configure new instance worldTest01 - Startup failure: Error code 1. See AMP logs for more information.”
Did you also encounter this error? And how did you resolve it?

4

These are my container settings, if this helps. I have AMP running in a Linux VM within Proxmox. The container image is what I changed.

AMP_Minecraft_Container_Settings
AMP_Minecraft_Container_Settings1027×756 113 KB

5

Thank you. Made the changes, however I am still getting errors. The container settings saving. But when going to update the following prompts.

This task could not be completed: Starting Instance - Starting Origins 2.0 (Origins2001)… - State: 3.

Startup failure: Error code 125. Please check the AMP Logs for further info.

6

I just tried you’re solution and I was able to get my instance running.

(For other people who get stuck. If you changed the java version in the Minecraft settings, restore it back to JDK 25, restart the instance, and try to run again. I wasn’t immediately able to start the instance, did a bit of poking around and figured that out.)