Forge Server Tools · every failure mode · guides
Client-only code reached the dedicated server — FATAL
A mod referenced a client-only class (a Screen, Minecraft.getInstance(), a renderer) from code that runs on the server. Forge's RuntimeDistCleaner strips client classes out of the server jar, so the reference explodes at class-load time rather than at the call.
Search the log for DEDICATED_SERVER. The class named just before it will be under net.minecraft.client, or a mod package containing client, render, gui or screen. If the named class is not client-related, this is not your failure.
Looks almost identical to a stale or partial jar, which also throws NoClassDefFoundError. The difference is which class is missing: a vanilla client class means this; a class from the mod's own package means a bad download.
If removing the mod is not acceptable, check whether it publishes a separate server build, and whether the pack marks it client-side. Report it upstream with the stack trace — the author's fix is usually a one-line @OnlyIn(Dist.CLIENT) guard, and they cannot fix what they have not seen.
Search your crash report or latest.log for any of these:
Attempted to load class ... for invalid dist DEDICATED_SERVER RuntimeDistCleaner ... invalid dist
The free edition of Forge Server Doctor detects this one. It is a single Python file with no dependencies — point it at the report and it names the cause and the mod jar:
python3 forge_doctor_free.py crash-reports/crash-....txt