To make a persistent The Forest server, install the separate The Forest Dedicated Server tool, create its Server.cfg, forward TCP and UDP ports 8766, 27015, and 27016 to the host computer, and launch the server with a valid save slot and initType Continue. The dedicated server is not a switch inside the normal game installation. The documented build is a Windows application; Linux hosting requires an unverified compatibility layer or a managed host that provides the operating system. This guide takes you from a clean installation through Internet visibility, save persistence, administration, and recovery when players cannot connect.
What do I need before making a The Forest server?
You need a Windows computer that can remain powered on, a stable network connection, router access for port forwarding, and a separate installation of the dedicated-server tool. The published setup material does not specify a minimum processor, memory, storage, or bandwidth requirement, so do not treat an arbitrary hardware figure as an official requirement. For a small private group, a modest Windows machine on a wired connection is the simplest self-hosting arrangement.
- Windows host: The cited dedicated-server build is a Windows executable. There is no official native Linux build in the documented material.
- Router access: Internet players need forwarding from your public connection to the host’s private address.
- Firewall access: Windows Firewall must allow the same three server ports you forward on the router.
- Steam account or SteamCMD: Steam’s Tools library is the easiest installation route; SteamCMD is available for command-line deployments.
- A save plan: Decide which save slot will hold the persistent world and where you will keep backups before inviting players.
A managed hosting service can handle the operating system, network exposure, and control panel if you cannot leave a Windows machine online or do not control the router. It reduces local networking work, but you trade away some direct control over files and restart procedures.
How do I install The Forest Dedicated Server?
Install the server as a separate Steam Tool, not from the normal game’s launch options. Steam’s current library listing and the current SteamCMD guides identify app ID 556450; an older installation reference lists 223350, so verify the package in Steam Tools if Valve changes the distribution record.
Steam graphical installation
- Open Steam and select Library.
- Use the library filter or drop-down to show Tools.
- Find The Forest Dedicated Server.
- Install it to a folder with enough free space and a path you can use consistently for updates and launch scripts.
The first launch and the configuration path are easier to manage when the installation directory is stable. Avoid moving the executable after you create shortcuts or batch files unless you update every path in those launch commands.
SteamCMD installation
For a command-line installation, run SteamCMD with an explicit destination and the current app ID:
force_install_dir "C:GameServersTheForest"
login anonymous
app_update 556450 validate
quitvalidate checks the downloaded files while updating. If this command stops working after a Steam distribution change, check the Steam Tools listing first rather than assuming the older ID is still valid. The conflicting older value, 223350, is a reason to verify the package directly whenever a fresh installation fails.
Where is Server.cfg, and how do I edit it?
Run TheForestDedicatedServer.exe once before editing anything. The initial run creates the configuration file in the Windows user profile at:
C:Users<user>AppDataLocalLowSKSTheForestDedicatedServerdsServer.cfgReplace <user> with the Windows account that launches the server. Stop the server before editing so it is not running with an older in-memory configuration while you save changes.
Using a separate configuration directory
The executable accepts -configfilepath so you can point it at an existing directory and file outside the default profile. This is useful when you keep server files under a dedicated account or want configuration and backups beside the installation. Use a full path in the launch command and make sure the file already exists at that location.
TheForestDedicatedServer.exe -configfilepath "C:/GameServers/TheForest/Server.cfg"Keep one authoritative configuration file. If you edit the profile copy but launch with -configfilepath, the running server will read the other file and appear to ignore your changes.
Which setting wins when values conflict?
The documented precedence rule is: “Command line parameters overwrite matching entries defined in the config file.” In practice, a value supplied in a shortcut, batch file, or service command can silently override the value you just changed in Server.cfg. Keep launch arguments limited to options you deliberately want to force, and inspect the startup command whenever a setting appears to revert.
Which Server.cfg values should I set first?
Use the host computer’s private LAN address for serverIP, not the public Internet address assigned by your provider. The following starter configuration uses the documented default ports, the documented eight-player maximum, a private password, and a persistent save:
serverIP 192.168.1.50
serverSteamPort 8766
serverGamePort 27015
serverQueryPort 27016
serverName The Forest Game
serverPlayers 8
serverPassword choose-a-private-password
serverPasswordAdmin choose-a-separate-admin-password
difficulty Normal
initType Continue
slot 1
showLogs onChange the example private address, server name, passwords, and slot to match your setup. The values below explain what each line controls and which choices are documented.
| Entry | Purpose | Documented choices or cautions |
|---|---|---|
serverIP |
Address on which the server binds. | Use the host’s private LAN address when it sits behind a router; do not substitute the public address. |
serverSteamPort |
Steam communication. | Default documented port: 8766, forwarded for both TCP and UDP. |
serverGamePort |
Gameplay communication. | Default documented port: 27015, forwarded for both TCP and UDP. |
serverQueryPort |
Server-list and query traffic. | Default documented port: 27016, forwarded for both TCP and UDP; this is the port used for direct Steam browser queries. |
serverName |
Name shown to players. | Use a recognizable name that identifies your group or world. |
serverPlayers |
Player capacity. | The tutorial documents a default maximum of eight players. |
serverPassword |
Password for normal players. | Choose a value you are comfortable sharing with the group. |
serverPasswordAdmin |
Password used for administration. | Keep it different from the player password. |
difficulty |
World difficulty. | The documented names are Peaceful, Normal, Hard, and HardSurvival. |
initType |
What the server does when it starts. | Use Continue after a world exists; leaving it at New prevents normal persistence. |
slot |
Save slot used by the dedicated server. | Valid documented slots are 1 through 5. Keep the same slot between restarts. |
showLogs |
Log visibility. | on makes startup and runtime messages easier to inspect while configuring. |
enableVAC |
Valve Anti-Cheat behavior. | The option is documented; leave it off or enable it according to your group’s needs. |
Why are the private address and save slot so important?
The private address tells the process which local interface to use, while the router forwards outside traffic to that same address. If the host receives a new DHCP address later, the forwarding rule can point to the wrong computer; reserve or otherwise keep the host’s LAN address consistent before troubleshooting remote access.
The slot is equally important for continuity. A server that starts with a different slot can appear to have lost the world even though the original save still exists in another slot. Pick one of the documented slots, record it with your backup notes, and do not change it casually.
Which ports does a The Forest server use?
A normal Internet setup needs TCP and UDP forwarding for all three documented ports, plus matching inbound firewall rules on the Windows host.
| Port | Protocol | Documented role | What to configure |
|---|---|---|---|
| 8766 | TCP and UDP | Steam communication port | Forward from the router to the server’s private IP and allow inbound traffic in Windows Firewall. |
| 27015 | TCP and UDP | Game communication port | Forward and allow both protocols on the same private IP. |
| 27016 | TCP and UDP | Query communication port | Forward and allow both protocols; this port is especially important for server discovery. |
How do I create the forwarding rules?
- Give the server computer a consistent private address, such as the example
192.168.1.50. - Open the router’s port-forwarding or virtual-server page.
- Create one rule for each port, forwarding both TCP and UDP to the server’s private address. If the router supports a combined TCP/UDP option, select it; otherwise create separate protocol entries.
- Open Windows Defender Firewall with Advanced Security and create matching inbound rules for the dedicated-server executable or for TCP and UDP ports 8766, 27015, and 27016.
- Save the router and firewall changes, then restart the server process so you can read a clean startup log.
Players on the same LAN do not need Internet port forwarding to reach the host locally. Players outside the home network do need the router and firewall path for all three ports.
How do I run the server continuously or in the background?
Launch the executable with batch mode so it runs without the normal interactive window, and include log output while you are still validating the setup. A repeatable Windows command is:
TheForestDedicatedServer.exe -batchmode -showlogs -configfilepath "C:/GameServers/TheForest/Server.cfg"-batchmode is the documented option for non-interactive operation, while -showlogs exposes startup messages in the launch session. If you use the default profile configuration instead, omit -configfilepath; do not edit one file and launch another.
What makes a home server available 24/7?
The process must remain running and the Windows machine must remain powered, connected, and reachable. A restart, sleep state, router reboot, changed private address, or Windows Firewall change can interrupt access. The setup references do not publish a dedicated hardware or bandwidth specification, so monitor the host’s own stability rather than relying on an invented capacity estimate.
Keep the installation directory, configuration path, and launch command documented in one place. When you update the server files, stop the process, back up the save, run the update, and start with the same configuration and slot.
How do players join and how do I verify visibility?
Start with the game’s Internet server list. If you want a direct Steam check, open Steam → View → Servers → Favorites → Add a Server and enter the public address followed by the query port, normally in the form public-ip:27016.
- Start the dedicated server and wait for the log to show that it has bound to the configured ports.
- From a device outside the host’s LAN, confirm that the public address is current.
- In Steam’s server browser, add the public address with
:27016. - Check that the server name and player capacity appear, then join through the game’s Internet list or the Steam result.
The query port is the discovery path. A server can be running while remaining invisible if 27016 is not forwarded, is blocked by the firewall, or does not match the value in the configuration. Check that port before changing unrelated gameplay settings.
How do I keep the world persistent and administer it?
Set initType Continue after the first world has been created, select a valid slot from 1 through 5, and make sure the server is writing saves. The documented warning is that leaving initialization at New prevents normal persistence, so a restart can look like a reset even when the process itself is healthy.
Save and backup routine
- Use one slot consistently and record its number with your server notes.
- Keep autosave enabled.
- Back up the dedicated-server save directory before changing slots, resetting a world, or testing a new configuration.
- Make a separate backup before updates or any command that could shut down or alter the world.
The available in-game administration commands documented for the server include /save, /shutdown, /kick, and /ban. They require the configured admin password. Give ordinary players only the player password; never publish the administrator credential in a public chat or server listing.
What should I check when the server does not appear?
| Symptom | Checks and corrective action |
|---|---|
| Server does not appear in the Internet list | Confirm the process is running, verify that query port 27016 is forwarded to the current private IP, check the Windows Firewall rule, and confirm that the public address is current. |
| Players connect locally but not remotely | Recheck router forwarding and matching TCP/UDP firewall rules for 8766, 27015, and 27016. Local success proves the process works, not that the Internet path is open. |
| World resets after a restart | Set initType Continue, choose a valid slot, keep that slot unchanged, and verify that the server is writing saves before stopping it. |
| Settings revert after editing Server.cfg | Inspect the launch shortcut or batch file for duplicate command-line values. Command-line parameters override matching configuration-file entries. |
| SteamCMD cannot download the files | Confirm the install directory and anonymous login syntax, then verify the app ID in Steam’s Tools listing. Current guides use 556450; an older reference lists 223350. |
| Linux instructions fail | There is no official native Linux build in the cited documentation. Use a Windows host, a managed provider, or a compatibility layer that you have explicitly tested rather than assuming native support. |
Reading the startup log
Use -showlogs or showLogs on while diagnosing. Look for the process to bind to the configured Steam, game, and query ports, then compare those values with the router and firewall rules. If the log shows a different configuration path than the file you edited, correct -configfilepath before changing individual settings.
Should I self-host or use managed hosting?
Self-hosting is best when you want direct access to the executable, configuration, saves, and backups and you can administer a Windows machine and router. Managed hosting is more practical when you cannot expose a home network, need a provider to handle the operating system, or want a control panel for deployment and restarts.
| Decision point | Self-hosting | Managed hosting |
|---|---|---|
| Operating system | You supply and maintain Windows hardware. | The provider supplies the server operating system and deployment workflow. |
| Network setup | You forward 8766, 27015, and 27016 and maintain firewall rules. | The provider handles the public network; confirm that the query port is exposed. |
| Files and backups | Full control, but you must copy and protect the save directory yourself. | Backup tools may be available; verify retention and download access before relying on them. |
| Location and latency | Bound to your home’s Internet connection and geographic location. | You can usually select a data-center location; check the actual region offered. |
| Capacity and policy | You choose the documented player setting and your own access policy. | Check the provider’s player limits, mod policy, support scope, and restart controls. |
| Cost | No hosting subscription, but you carry hardware, electricity, and network administration. | A recurring fee buys managed infrastructure; current prices vary by provider and region. |
Whichever route you choose, verify that the host exposes the query port and gives you a way to back up the world. A low monthly price is not useful if you cannot retrieve a save or diagnose a listing failure.
Can I run a The Forest server on Linux?
Not as an officially supported native build according to the cited setup documentation. Linux users must either run the Windows application through an unverified compatibility layer or choose a managed host that operates Windows for them.
A compatibility layer adds another failure point: updates, networking, and process behavior may differ from the documented Windows path. If you test that route, reproduce the same configuration, ports, query check, and save-backup procedure used on Windows before inviting other players. For predictable support, a small Windows machine or a provider with a documented deployment workflow is the safer choice.
What is the safest first-launch checklist?
- Install the dedicated server from Steam Tools or SteamCMD using the verified package ID.
- Launch once to create
Server.cfg, then stop the process. - Set the private
serverIP, ports 8766, 27015, and 27016, a server name, passwords, difficulty,initType Continue, and a slot from 1 to 5. - Forward TCP and UDP for all three ports and create matching Windows Firewall rules.
- Launch with
-batchmode,-showlogs, and the intended-configfilepath. - Test from the same LAN, then test externally through Steam’s Favorites server browser using the public address and
:27016. - Confirm the world saves, make a backup, and only then share the player password.
Frequently Asked Questions
Can I use a different port than 8766, 27015, or 27016?
The configuration exposes separate Steam, game, and query-port entries, so a changed value must be reflected consistently in the server file, router forwarding, and firewall rules. The documented defaults are the safest starting point; changing only one side of the path commonly breaks discovery or remote connections.
Why does my Steam browser entry show no server information even though the process is running?
The browser asks the query endpoint, not merely the game process. Add the public address with the query suffix, normally :27016, and verify that this port reaches the same private address as the running server; a game-port-only rule is insufficient for listing.
What happens if I put a launch option and a different value in Server.cfg?
The launch option wins. For example, if the file specifies eight players but the batch command supplies a different player value, the command-line value is used until you remove or change that argument.
Which difficulty names and save slots are accepted?
The documented difficulty names are Peaceful, Normal, Hard, and HardSurvival. Save slots are numbered 1 through 5; choose one and keep it unchanged when you want the same persistent world to load after restarts.
Is a public IP address required for players on my home network?
No. Players on the same LAN can connect without Internet port forwarding because traffic stays inside the local network. A public address and forwarded ports are needed for players outside that LAN.