2 critical, 2 warnings, 1 observation found. Every finding below comes from what was actually in the pasted files. Treat the fixes as suggestions: they cover the common causes, and this case may need more digging.
NeoforgeMinecraft 1.21.1Java 21
What this error means, and every way to fix it →
tpa read its config before it was loaded
tpa 2.0.0 asked for a config value before the loader had read that config file, and the loader refuses rather than hand back a guess. Server configs are not loaded until a world is, so a mod that reads one from the title screen or during startup crashes like this. This is a bug in tpa, not in your setup. Update it, since fixes for this are usually quick to ship. If its config file in config/ or serverconfig/ is empty or broken, deleting it lets tpa write a fresh one. If neither helps, remove tpa and report the crash to its author with this report.
Usual suspects: tpa.
jump to line 1886A client-only mod is in the server files
A mod that only works in the game client was installed on the dedicated server, and it crashed trying to load client-side code. Remove the mod from the server's mods folder, or exclude it from the server-side pack. Players keep it in their own clients.
Why this happens: Client-only mods on a server →jump to line 6089 config or data files are empty or corrupt
Gson could not parse a file the game or a mod tried to load (recipe/beetroot_soup.json is named just above the first error). "End of input at line 1 column 1" is an empty file, which is what a crash or kill mid-write leaves behind; "Expected BEGIN_OBJECT but was STRING" is text where JSON was expected. Whatever depended on that file is running on defaults or not at all. Find the file (the lines just above each error usually name it), back it up, then delete it so the mod regenerates it, or restore it from a backup. If the same file keeps breaking, the disk filled up or the server is being killed while it saves.
jump to line 1246The tick loop fell 10301ms behind, 206 ticks in one go
A tick took far longer than the 50ms it is allowed, so the server ran behind real time and skipped ahead to catch up (4 times in this log). Players see rubber-banding, delayed block breaks and mobs that stutter. One burst after a restart, a world upgrade or a chunk pre-generation run is normal. A steady stream is lag with a cause: profile it with spark (/spark profiler start --timeout 120 in the console) rather than guessing. The usual culprits are view-distance and simulation-distance set too high, entity or item build-ups, chunks generating live as players explore, and garbage collection pauses when the heap is too small.
Hosting with the headroom to keep up →Why this happens: Diagnosing server lag →jump to line 1770Refmap warnings are cluttering the log
A "reference map could not be read" warning on its own is usually harmless build noise from a mod, not the cause of a crash. Ignore these lines unless a real mixin failure appears further down. They only matter when paired with an injection error.
jump to line 463199 sensitive values (addresses, passwords and the like) were stripped before this page was stored.
As received, after redaction.
Need more help or want to discuss your issue further? Join our Discord and bring the link to this page.
Join our DiscordRun a community? Add the Roastd bot and anyone can roast a crash log in your support channel.
Add the Roastd botGot a server of your own that deserves a second opinion?
Roast your own serverRoastd is a free tool built by Hostd. This diagnosis stays put. The log it was read from is deleted on a timer.