Squad server errors and how to fix them

Most Squad server problems come down to a few things: the browser filter, a typo in a config file, a mod out of step with the game, or a server short on room. Find your problem below.

The server isn’t in the browser

1. Look under Custom Servers. Unlicensed servers aren’t in the main list.
2. Check that it’s advertised. Show in the server browser in Settings must be on.
3. Give it a minute. A new or restarted server takes a short while to appear.
4. Search for the exact name. Clear any filters you set, like map or player count.
5. Check the console. If the server stopped during start, the log shows why.

Players can’t join

• After a Squad update: the server and players must run the same version. Stop the server and start it again so it updates from Steam, and ask players to update too.
• On a modded server: every player needs every mod. See Mods for how to share them.
• The server is full: when all slots are taken, players wait in the queue. Raise Queue size in Settings if the queue is full too.
• Wrong password: passwords match exactly, capitals included.

How to connect has every way to join.

Admin commands don’t work

1. Check the SteamID64. It’s 17 digits and starts with 7656. A Steam custom URL name won’t work.
2. Check the line format. It’s Admin=<SteamID64>:<group>, with the group spelled as in its Group= line.
3. Check the group’s permissions. Kicking needs kick, map changes need changemap, and so on.
4. Restart. Admins.cfg is read when the server starts.

The config reference lists the permissions.

A mod won’t load

• Wrong Workshop ID: it’s the number after ?id= in the mod’s link. Check it in Settings.
• Wrong ID in the load order: ModLoadOrder takes the IDs from each mod’s .mi file, not Workshop numbers.
• The mod is out of date: after a Squad update, mods can stop working until their authors update them. Remove the mod and restart.
• Its layers never come up: a map mod only plays once its layers are in your rotation.

The server stops while starting

1. Read the last lines in the console. They usually name the file or mod at fault.
2. Undo your last change. Restore yesterday’s file from Files, or a whole backup from Backups.
3. Remove mods if the trouble started after a Squad update, and add them back one at a time.

A layer is skipped or the wrong map loads

Rotation files need layer IDs like Narva_AAS_v1, not the names you see in game. A typo makes the server skip that line. Check the spelling, one layer per line, and restart.

Matches lag when the server is full

This is usually the CPU, not the network. See performance for plan sizes and fixes.

Still stuck?

Write to us at support@wilderack.com. Real people answer. Tell us your server name, what you changed last and when the problem started. The help form in the panel can attach your server’s last log lines for you.