ATM10 errors I that seem obvious but can't get past #3112
Labels
Comments
|
Other people seem to have gotten ATM10 to work such as #3090 For future reference troubleshooting modpacks should not be filed as an enhancement request. |
|
Thank you, I will try the extra env variables. Also apologies on the oversight of putting this in enhancement. |
|
@Bluewasabe I am currently running ATM10. Did you get yours running? |
|
@rhullah I did actually. I think the CF_EXCLUDES_MODS in the link that that itzg posted above was the thing that got me over the hump. |
|
Do you know how exactly you fixed the issue? Unable to get my ATM 10 Server back up after it tried to update |
|
Mine is still on 10-1.1
…On Sun, Oct 20, 2024 at 1:38 PM Ovaru ***@***.***> wrote:
Do you know how exactly you fixed the issue?
Unable to get my ATM 10 Server back up after it tried to update
—
Reply to this email directly, view it on GitHub
<#3112 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALVTZGG5JKKZABE63POVZW3Z4PTAZAVCNFSM6AAAAABQE6MCT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRVGE2DMMJZGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Mine is also on 1.1 or at least its supposed to be |
|
Just tried a new instillation of a new docker container and I am getting the same error |
|
This is the compose that got me through what I was seeing originally on this post |
|
Here is mine that's currently running 1.12, but I don't expect any issues upgrading to 1.13 which was recently released: services:
mc:
image: itzg/minecraft-server
tty: true
stdin_open: true
ports:
- "45121:25565/tcp"
volumes:
- data:/data
- /etc/timezone:/etc/timezone:ro
environment:
EULA: true
MAX_TICK_TIME: -1
MOTD: "ATM10"
MOD_PLATFORM: AUTO_CURSEFORGE
CF_API_KEY: ${CF_API_KEY}
CF_SLUG: all-the-mods-10
CF_FILENAME_MATCHER: "-1.2"
CF_EXCLUDE_MODS: |
986380
dark-mode-everywhere
iceberg
just-enough-mekanism-multiblocks
model-gap-fix
packmenu
reeses-sodium-options
sodium-extra
toast-control
MAX_MEMORY: 8G
DIFFICULTY: hard
ALLOW_FLIGHT: true
MAX_PLAYERS: 10
SPAWN_PROTECTION: 0
LOG_TIMESTAMP: true
ENABLE_ROLLING_LOGS: true
volumes:
data: |
|
The post above fixed it I believe I was excluding the mods incorrectly |
|
On the 1.11 version, I'm just getting: I've tried varying combinations on the above to no avail, my current compose file looks like this: |
|
Have you tried the CF exclude mods from either mine or rhullah's examples? That was the kicker for me. |
I am actively running 1.11 with no issues using my compose I shared above. |
I've tried an exact copy of yours and the other one, and various permutations to no avail |
|
It sounds kind of like a permission issue but not sure. Can you share your full log and compose file? |
|
I wonder if it is a windows issue. ATM9 ran perfectly fine within windows. Compose file: Logs |
|
@chris-ware maybe you need to temporarily set or similar logs about installing the modloader. |
|
@itzg One of those sorted the issue, it's now continuing on, many thanks. |
|
seems like sodiumoptionsapi also needs to be excluded. updated exclude looks like |
|
Yeah, I had already updated that locally. So I created a PR for an example. 1.17 also had some issues with the |
|
And the merged example https://github.com/itzg/docker-minecraft-server/tree/master/examples/atm10 |
I used this yesterday and was able to get the container running, i destroyed the container and recreated it this morning and when i try to connect to the server i get the error: docker compose: |
That typically happens when the client does not have all the right mods matching the right versions to what the server is running. |
|
Ah sweet thanks |
|
Had the same problem, log file was having some class not found exceptions for the Sodium mod. (Log of the initial failure for reference if needed: mc-docker-log.txt) Did some digging, turned out Sodium was not getting downloaded with a similar docker-compose as listed in this thread. Added the following line to my compose, which then led to the next error:
So then I tried this line instead, which got the server booting: Would be nice if I got that ERROR while trying to start the server or the docker imagine originally instead of having to jump through some hoops to figure that out. Maybe I missed something? The Auto Curseforge docs do mention stuff about manual downloads for mods that aren't allowed, but I had no indication that Sodium was disallowed to download from curseforge prior to trying to force it. This is the final docker-compose I used: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry if this is a repeat question with all the mods, but I've tried removing/downgrading mods like allthewizard gear and sodium-extra but I can not get this server to work. Also a crash report is not being generated which I am used to so commented out always on for clear end point of logs.
Docker compose file
logs.txt
The text was updated successfully, but these errors were encountered: