Describe the problem
This issue started happening all of a sudden. I was on latest so maybe it pulled a dud image but I pinned it to 2026.7.2 with paper version 26.2 and I am still getting crashing when loading the nether world. I have the logs attached. If someone could help me out that would be greatly appreciated.
I run the container as a pod on kubernetes with a sidecar that handles backups
mcs1-error.log
Container definition
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: mcs1
namespace: mc-system
spec:
serviceName: mcs1-svc
selector:
matchLabels:
app: mcs1
replicas: 1
template:
metadata:
labels:
app: mcs1
spec:
priorityClassName: critical-apps
containers:
- name: mcs1
image: itzg/minecraft-server:2026.7.2
env:
- name: EULA
value: "TRUE"
- name: ONLINE_MODE
value: "TRUE"
- name: TYPE
value: "PAPER"
- name: VERSION
value: "26.2"
- name: PAPER_CHANNEL
value: "default"
- name: MAX_MEMORY
value: "2G"
resources:
requests:
memory: 2000Mi
cpu: 1000m
ports:
- containerPort: 25565
volumeMounts:
- name: mcs1-data
mountPath: /data
- name: mcs1-config
mountPath: /config
- name: backup
image: itzg/mc-backup
imagePullPolicy: IfNotPresent
securityContext:
runAsUser: 1000
env:
- name: BACKUP_INTERVAL
value: "4h"
- name: PAUSE_IF_NO_PLAYERS
value: "true"
- name: DEST_DIR
value: "/backups/mcs1"
volumeMounts:
- mountPath: /data
name: mcs1-data
readOnly: true
- mountPath: /backups
name: backups
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: host
operator: In
values:
- baremetal
volumes:
- name: mcs1-data
persistentVolumeClaim:
claimName: mcs1-data
- name: mcs1-config
configMap:
name: mcs1-config
- name: backups
persistentVolumeClaim:
claimName: nfs-mc-backups
Container logs
[00:34:11 ERROR]: Encountered an unexpected exception
java.lang.RuntimeException: Could not create world config for minecraft:the_nether
at io.papermc.paper.configuration.PaperConfigurations.createWorldConfig(PaperConfigurations.java:323) ~[paper-26.2.jar:26.2-87-a95ae8d]
at net.minecraft.server.level.ServerLevel.lambda$new$0(ServerLevel.java:637) ~[paper-26.2.jar:26.2-87-a95ae8d]
at net.minecraft.world.level.Level.<init>(Level.java:855) ~[paper-26.2.jar:26.2-87-a95ae8d]
at net.minecraft.server.level.ServerLevel.<init>(ServerLevel.java:637) ~[paper-26.2.jar:26.2-87-a95ae8d]
at net.minecraft.server.MinecraftServer.createLevel(MinecraftServer.java:743) ~[paper-26.2.jar:26.2-87-a95ae8d]
at io.papermc.paper.world.PaperWorldLoader.loadInitialWorld(PaperWorldLoader.java:166) ~[paper-26.2.jar:26.2-87-a95ae8d]
at io.papermc.paper.world.PaperWorldLoader.loadInitialWorlds(PaperWorldLoader.java:131) ~[paper-26.2.jar:26.2-87-a95ae8d]
at net.minecraft.server.MinecraftServer.loadLevel(MinecraftServer.java:618) ~[paper-26.2.jar:26.2-87-a95ae8d]
at net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:339) ~[paper-26.2.jar:26.2-87-a95ae8d]
at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1267) ~[paper-26.2.jar:26.2-87-a95ae8d]
at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:303) ~[paper-26.2.jar:26.2-87-a95ae8d]
at java.base/java.lang.Thread.run(Unknown Source) ~[?:?]
Caused by: org.spongepowered.configurate.loader.ParsingException: []: Unknown error occurred while loading
at org.spongepowered.configurate.loader.AbstractConfigurationLoader.load(AbstractConfigurationLoader.java:171) ~[configurate-core-4.2.0.jar:?]
at org.spongepowered.configurate.loader.AbstractConfigurationLoader.load(AbstractConfigurationLoader.java:69) ~[configurate-core-4.2.0.jar:?]
at org.spongepowered.configurate.loader.ConfigurationLoader.load(ConfigurationLoader.java:56) ~[configurate-core-4.2.0.jar:?]
at io.papermc.paper.configuration.Configurations.createWorldConfig(Configurations.java:230) ~[paper-26.2.jar:26.2-87-a95ae8d]
at io.papermc.paper.configuration.Configurations.createWorldConfig(Configurations.java:208) ~[paper-26.2.jar:26.2-87-a95ae8d]
at io.papermc.paper.configuration.PaperConfigurations.createWorldConfig(PaperConfigurations.java:321) ~[paper-26.2.jar:26.2-87-a95ae8d]
... 11 more
Caused by: unacceptable code point '' (0x0) special characters are not allowed
in "'reader'", position 0
at org.spongepowered.configurate.yaml.internal.snakeyaml.reader.StreamReader.update(StreamReader.java:207) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.reader.StreamReader.ensureEnoughData(StreamReader.java:171) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.reader.StreamReader.ensureEnoughData(StreamReader.java:166) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.reader.StreamReader.peek(StreamReader.java:121) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.scanner.ScannerImpl.scanToNextToken(ScannerImpl.java:1222) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.scanner.ScannerImpl.fetchMoreTokens(ScannerImpl.java:338) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:242) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.parser.ParserImpl$ParseImplicitDocumentStart.produce(ParserImpl.java:210) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:161) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:152) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.composer.Composer.getSingleNode(Composer.java:166) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:179) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.Yaml.loadFromReader(Yaml.java:508) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.internal.snakeyaml.Yaml.load(Yaml.java:461) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.YamlConfigurationLoader.loadInternal(YamlConfigurationLoader.java:207) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.yaml.YamlConfigurationLoader.loadInternal(YamlConfigurationLoader.java:48) ~[configurate-yaml-4.2.0.jar:?]
at org.spongepowered.configurate.loader.AbstractConfigurationLoader.load(AbstractConfigurationLoader.java:161) ~[configurate-core-4.2.0.jar:?]
... 16 more
[00:34:11 ERROR]: This crash report has been saved to: /data/crash-reports/crash-2026-07-31_00.34.11-server.txt
[00:34:11 INFO]: Stopping server
[00:34:11 INFO]: Saving players
[00:34:11 INFO]: Saving worlds
[00:34:11 INFO]: Saving chunks for level 'ServerLevel[world]'/minecraft:overworld
[00:34:11 INFO]: [ChunkHolderManager] Waiting 60s for chunk system to halt for world 'minecraft:overworld'
[00:34:11 INFO]: [ChunkHolderManager] Halted chunk system for world 'minecraft:overworld'
[00:34:11 INFO]: [ChunkHolderManager] Saving all chunkholders for world 'minecraft:overworld'
[00:34:11 INFO]: [ChunkHolderManager] Saved 0 block chunks, 0 entity chunks, 0 poi chunks in world 'minecraft:overworld' in 0.01s
[00:34:11 INFO]: [ChunkHolderManager] Waiting 60s for chunk I/O to halt for world 'minecraft:overworld'
[00:34:11 INFO]: [ChunkHolderManager] Halted I/O scheduler for world 'minecraft:overworld'
[00:34:11 INFO]: ThreadedAnvilChunkStorage (world): All chunks are saved
[00:34:11 INFO]: ThreadedAnvilChunkStorage: All dimensions are saved
[00:34:11 INFO]: Waiting for all RegionFile I/O tasks to complete...
[00:34:11 INFO]: All RegionFile I/O tasks to complete
[00:34:11 INFO]: [MoonriseCommon] Awaiting termination of worker pool for up to 60s...
[00:34:11 INFO]: [MoonriseCommon] Awaiting termination of I/O pool for up to 60s...
Describe the problem
This issue started happening all of a sudden. I was on latest so maybe it pulled a dud image but I pinned it to 2026.7.2 with paper version 26.2 and I am still getting crashing when loading the nether world. I have the logs attached. If someone could help me out that would be greatly appreciated.
I run the container as a pod on kubernetes with a sidecar that handles backups
mcs1-error.log
Container definition
Container logs