Is your The Forest game server missing from the server list, failing to start, or suddenly using a different save? Don't worry—most issues have a simple cause. Here we'll show you the most common problems and how to fix them yourself quickly.
Your game server's console is the most useful tool for troubleshooting. It shows what your server is doing during startup. Lines containing [forest-entrypoint] come from your server's startup script. For example, Starting The Forest dedicated server appears when the game starts. The console is read-only for The Forest, so you can't enter commands there.
Want to see more? Set showLogs to on in config/config.cfg. The console will then also show the server's event log. See our Server Configuration guide for instructions on editing the file.
The first startup or startup after an update takes a long time
The Forest server is a Windows program that runs on your Linux server using Wine. During the first startup and after an update, your server sets up its Wine environment again, and the console will show Initializing Wine prefix. This startup takes a little longer than a normal restart. Wait until Starting The Forest dedicated server appears in the console, then give the game a little more time to load.
Server doesn't appear in the server browser
- Check Overview to see whether your server is online, and wait a few minutes after starting it.
- In the game, go to Multiplayer → Join Game → Dedicated (Internet), search for your server name in the Filter By Name field, and click Refresh.
- If you still can't find it, connect directly using the Steam launch option
+connect <IP address>:<port>.
Our guide Connecting to the server explains both methods.
Can't join even though the server is listed
- Make sure your game is up to date and update it through Steam. If a new server version is available, ZapX will show the Update available notice when you open your game server. Click Apply update to install it; your saves and settings will be preserved.
- If you've set a server password, check that you have the correct capitalization.
- A The Forest server supports up to 8 players. If it's full, no one else can join until a slot becomes available. You can set the number of players in the Max. players field under Startup Parameters.
My changes to config.cfg are gone after restarting
Your server writes the server name, player count, passwords, Steam server token, IP, and ports to config.cfg from the Startup Parameters every time it starts. Always change these values in the Configuration tab under Startup Parameters. All other lines in the file, such as difficulty or veganMode, are preserved.
It's best to edit the file only while your server is stopped, then restart it. If you deleted config.cfg, your server will create a new file with the default values the next time it starts.
The difficulty doesn't change
The difficulty setting only applies when a new game starts. A continued save keeps the difficulty it was created with. To play at a different difficulty, start a new game in an empty slot (see the next section).
My save is gone or the server always starts a new game
- Check the
initTypeline inconfig.cfg. If it's set toNew, your server will start a new game. Set it toContinueto continue your save. - Check the
slotline. Your server uses exactly one of the 5 save slots. If you changed the slot, it will load the save from the new slot. Your old save is still in its original slot. - You can find your saves in the
savesfolder in the Savegames tab. Restore older saves from a backup in the Backups tab.
Learn more in our Managing savegames guide.
Progress is missing after a restart
Your server saves automatically at the interval set by serverAutoSaveInterval, which is 30 minutes by default. Progress made since the last automatic save may be lost after a restart or crash. Set a lower value in config.cfg to save more often; the minimum value is 15.
Server is overloaded or lagging
Check the Statistics tab to see how heavily your server's CPU and memory are being used. We recommend 4 GB of memory for a The Forest server. If performance is insufficient, switch to a larger plan. If you've changed targetFpsIdle or targetFpsActive in config.cfg, try setting them back to the default value of 0.
If none of these tips help, our support team is here for you every day. Just start a support chat in your ZapX customer account and describe your issue in as much detail as possible—ideally, include the last few lines from the console.