Possible Fixes

Maybee ....

Modpack Version

10-1.25 (Client) 1.25 (Server)

What happened?

The server is telling me in my logs that the client is using the wrong NeoForge version.

Since there i no official docker Image for Unraid I tried to create my own. For that, I used this as example docker-allthemods9.

Here is my adaption try for atm10:

atm10-docker-unraid

I think my approach worked, because I could set the image up on my Unraid and everything worked. Until it got to the point where I needed to join on the Server with my client.

PS: for the container creation, I am using GitHub workflows with "docker/[email protected]"

In the lauch.sh I am using the NeoForge Version "21.1.81" since that is the one the client Version 10-1.25 seems to be using.

But the log of the Server looks as the following if I try to connect with my client to the server:
"lost connection: Incompatible client! Please use NeoForge 21.1.81"

But Atm 10 Client Tells me it uses NeoForge version 21.1.81:

Is this a bug on my Docker-File or in Server/Client Instance?

latest.log

No response

Developer reports

No response

I've found this other already solved issue:
issues 791

This didn't solve the problem in my case.

My server contains the following "correct" NeoForge Version:

And I assume that the client is running NeoForge 21.1.81 as well, since it's stated in the manifest.json:

"modLoaders": [
  {
    "id": "neoforge-21.1.81",
    "primary": true
  }
]

As well, in the loading screen it shows the "correct" Version:

Will this also fix this kind of issue I have with trying to install it via GDLauncher?

I've now tested it with the Version 1.26 and Neoforge 21.1.83

Sadly, still not fixed ....

Finally, I made it work. My Setup of NeoForge in my Docker-Files were wrong and I managed adjusted them...

I've published a working Docker Container on Unraid named "all-themods-10".

Here is the link to the Repository:
https://github.com/fl3xm3ist3r/docker-allthemods10