Nearly every Killing Floor 2 ticket is one of these.
1. Settings revert after a restart
Killing Floor 2 writes its config files when it shuts down, so anything typed while the server is running is overwritten.
- Stop the server and wait for it to report offline.
- Edit the file and save.
- Start the server.
If it still reverts, you are probably editing the config for the wrong platform. Check the file name prefix matches the build your server runs.
2. The server is not in the browser
- Prove the server works first with
open IP:GamePortin the game console. - Steam favourites need the query port, not the game port.
- Clear the browser filters for full and password protected servers.
- Give a newly started server a few minutes.
3. Workshop maps do not download
- Each map needs its own workshop item line in the engine config.
- The map name in the rotation must match the downloaded map exactly.
- Read the console during boot. Downloads are reported there, and a first start with several maps is slow.
4. The web admin will not open
- It has to be enabled in
KFWeb.iniand the server restarted. - It listens on its own port, which has to be allocated to your service. Check the server dashboard in the panel for a second port.
- Log in with the user name
Adminand the admin password from your config.
5. Players are dropped after an update
Steam updates the client automatically. Restart the server from the panel so it updates too, and let the console finish before trying again.
6. The server crashes on map change
- A broken or missing custom map is the usual cause. Remove the last map you added from the rotation and restart.
- If the console shows the process being killed rather than a game error, it ran out of memory. Reduce the map load or move to a larger plan.
Open a ticket from Support in the Client Area with the last 50 lines of console output if none of this fits.





