Forge Server Tools · every failure mode · guides
A client-only mod is installed on the server — FATAL
A mod that only exists for rendering/UI was placed in the server's mods folder. Common culprits: shader loaders, minimaps, HUD mods, texture utilities, animation mods.
Remove the named mod from the server's mods/ folder. Clients keep it. If players then get kicked for a mod mismatch, mark it client-side in your launcher/pack config rather than putting it back on the server.
Check the mod page: if it lists 'client' as its only environment, this is it. Shader loaders, minimaps, zoom, HUD tweaks, animation and sound mods are the usual ones.
Players then get kicked for a mod mismatch, which tempts people to put it back on the server. Do not — mark it client-side in the pack instead.
Audit the whole folder at once rather than one crash at a time. Most packs ship a client-only list, and server hosts frequently copy the client mods folder wholesale, which produces a queue of these.
Search your crash report or latest.log for any of these:
has been loaded on the is client net.minecraftforge.fml.ModLoadingException ... client
The free edition covers the eight most common startup failures, and this is not one of them — it is in the paid tool, which checks all 24 and names the mod jar from the stack trace. The fix above is the same one it prints, so you do not need it to solve this.