Free tools Windows power users keep installed
One-click scans. No signup required.
A Satisfactory dedicated server that “won’t start” can have two very different problems: the FactoryServer process may have failed, or the process may be running while a firewall, router, NAT, or port mismatch blocks connections. Check the process first, then test from the same LAN, inspect the server’s actual listening ports, and only afterward troubleshoot internet forwarding. This order prevents changing router rules when the server never started.
Godlike.Host offers hosted Satisfactory servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
The documented default ports are 7777/TCP, 7777/UDP, and 8888/TCP. Installation validation, the first fatal line in FactoryGame.log, and a backed-up settings reset solve most startup failures without deleting a working save.
As an Amazon Associate I earn from qualifying purchases.
First determine whether the server process is running
The official dedicated-server guidance identifies the simplest explanation for an unreachable server: it was never started, or it crashed and was not restarted. Do not begin by editing port forwarding. Confirm that FactoryServer exists as a running process and then check what it is listening on.
Check on Linux
- Open a terminal on the server host.
- Run
pgrep -f FactoryServer.sh. - If the command returns a process ID, the server process exists. If it returns nothing, the server is not running; inspect the launch command, permissions, and logs before changing network settings.
A process ID only proves that a process exists. It does not prove that the game has finished loading a save or that the expected ports are open. A process can also remain visible briefly while shutting down, so repeat the check after a failed connection attempt and compare it with the current log.
#1 Best Overall
- [Ultimate 98000+ Game Archive: 9800+ 3D & 1000+ Premium Titles]Unleash the definitive retro collection: 98000+ preloaded classics now enhanced with 9,800+ immersive 3D games and 1,000+ curated high-end PC masterpieces. From pixel-era arcades to cinematic epics, all optimized for instant launch.
- [Games need exclusions and runtimes, not malware]Some customers ask why our retro game drives can trigger Windows Security warnings. Many game files are older DLLs that Windows Defender sometimes flags as threats. They are not viruses or malware—just old or uncommon code causing false positives. We temporarily add them to the exclusion list so they aren't blocked, then re-enable Security to keep your PC protected. Many classic games also need legacy VC++ and DirectX runtimes, which modern Windows doesn't include by default. Installing them ensures compatibility and smooth play. Your safety matters to us—these are safe, standard steps for retro games.
- [Important:Before you buy]your OS will show ~12.7TB due to decimal/binary measurement difference – this is a common practice among international manufacturers, not a capacity labeling error. Also, actual working game count may vary by system and emulator; please verify compatibility upon receipt. Every unit is fully tested for storage and game functionality before shipment. Includes an updated manual with setup and troubleshooting tips. Contact us for any missing or non-working titles – we’ll help promptly.
- [Unified 7-System Gaming Hub & Seamless Compatibility]Revolutionize your setup with all-in-one access to 7 gaming generations via integrated frontend. Play seamlessly across vintage consoles to modern PC rigs – 260+ platforms supported without complex configurations.Tip: For 4K-ready AAA gameplay, pair with GTX 1060 Ti GPU or higher
- [ Massive 14TB Retro Gaming Storage & USB 3.1 Speed]Upgrade to expansive capacity with this 14TB retro game hard drive, featuring next-gen USB 3.1 interface (10Gb/s transfer speed). Experience plug-and-play simplicity on Windows PC 7/8/10/11 – 50% faster data access than standard USB 3.0 drives.
Check on Windows
- Open Task Manager and look for
FactoryServer.exe, or open Command Prompt. - In Command Prompt, run
tasklist | find "FactoryServer.exe". - If no matching process appears, start-up failed or the process exited. If it appears, continue with listening-port and LAN tests.
Distinguish a crash from a slow start
Large saves can take time to load, so avoid killing a process merely because the console is quiet for a short period. Use the process check together with the current log. A process that disappears while loading, repeatedly returns after a launch attempt, or leaves a crash report indicates a start-up failure rather than a router problem.
Record whether the process exits immediately, survives long enough to load the world, or dies only when a particular save is selected. Those are different failure patterns. An immediate exit points toward the launch, installation, configuration, or port bind. A failure during save loading makes the log and crash report especially important. A server that stays running but cannot be reached belongs in the connectivity branch of the diagnosis.
Use a LAN test before testing the internet
Connect from another device on the same local network using the server host’s LAN address. This single test separates local host problems from external routing problems.
If LAN access fails
- Recheck that
FactoryServeris still running. - Confirm the server is listening on the configured ports, not merely the documented defaults.
- Allow the game executable through the operating-system firewall, antivirus, or Windows Defender. Coffee Stain’s support guidance specifically recommends creating an allow rule for the executable.
- Review the server log for a fatal error, bind failure, missing file, or crash report.
- Check that the client is using the server’s current LAN address and configured port, rather than an old address saved from a previous DHCP lease.
When a client on the same LAN cannot connect, internet forwarding is not the primary suspect. Solve the process or host-firewall issue first. If the server host has more than one network interface, also make sure the address used for the test belongs to the interface carrying the LAN connection.
If LAN access works but internet access fails
A successful LAN connection proves that the game server and local firewall path work. Focus on the router and public network path: forward the configured ports to the server host’s LAN address, verify that the public address is current, and check for carrier-grade NAT or other ISP restrictions. A forwarding rule aimed at an old DHCP address will fail even when the server itself is healthy.
Test from a genuinely external connection, such as a mobile-data connection, rather than relying on a router’s loopback behavior. Some routers do not support connecting to the public address from inside the same LAN. If an external test fails while LAN play remains reliable, do not repeatedly reinstall the server; the remaining fault is almost certainly in forwarding, addressing, NAT, or an upstream restriction.
Configure the documented ports exactly
The current dedicated-server documentation lists these defaults. A custom port assignment is valid, but every layer must use the same values: the server configuration, operating-system firewall, and router forwarding rules.
| Port | Protocol | Documented function |
|---|---|---|
7777 |
TCP | Server traffic and HTTPS API |
7777 |
UDP | Game traffic and lightweight query API |
8888 |
TCP | Reliable messaging |
Forward the same ports that the server uses
- Find the configured server port values in the server’s configuration rather than assuming the defaults.
- Give the host a stable LAN address, preferably with a DHCP reservation, so forwarding does not follow a changing address.
- Create router rules for each required protocol and port, pointing to that LAN address.
- Create matching inbound rules in the host operating-system firewall.
- Restart the server and test on the LAN before trying the public address.
Use separate rules when the router distinguishes TCP and UDP. Forwarding only a port number without the required protocol can leave one part of the connection unavailable. If you remap an external port to an internal port, document the mapping and ensure the server and clients use the values expected by that arrangement; a hidden translation is a frequent source of confusion.
The Satisfactory Steam announcement says the server can try up to 512 ports. That behavior does not remove the need for correct forwarding: if NAT or a firewall remaps a port, the remapping must match the server configuration and the value clients are expected to use.
Rank #2
- Create, build and run the most realistic city you can imagine
- Connect your metropolis with other cities you've created to form a massive region of SimCities
- Sculpt mountains, gouge valleys, and seed forests
- Deploy police cruisers and fire trucks to the scene
- For 1 player
Common port mistakes
- Forwarding only UDP 7777 and omitting TCP 7777 or TCP 8888.
- Forwarding the default ports while the server was remapped to custom values.
- Creating a router rule but leaving the host firewall blocked.
- Pointing rules at a stale LAN address after the server received a new DHCP lease.
- Testing the public address from inside a router that lacks NAT loopback support.
- Changing several port values at once without recording the previous configuration, making it difficult to identify which change fixed or caused the failure.
Read the log and crash report before reinstalling
Startup failures leave their most useful evidence before files are deleted or an installation is replaced. Server logs are stored under FactoryGame/Saved/Logs. The active file is FactoryGame.log; older logs are rotated into files whose names contain dates and times.
Crash reports are stored under FactoryGame/Saved/Crashes in randomly generated directories. Preserve the first fatal or error line, plus the surrounding context, before attempting cleanup. The first failure is generally more diagnostic than later messages caused by the same fault.
What to record
- The exact time of the failed launch.
- The first line marked fatal or error in the current
FactoryGame.log. - Whether a new directory appeared under
FactoryGame/Saved/Crashes. - The configured port and whether another process may already be using it.
- Whether the process exits immediately, remains running, or crashes only while loading a save.
- Whether the failure began after an update, configuration edit, or service change.
Do not delete the log or crash directory until this information is copied. A clean reinstall cannot recover evidence that was removed. When comparing attempts, keep the timestamp and launch options with each copy so an old error is not mistaken for the cause of a newer failure.
Validate and update a SteamCMD installation
For a SteamCMD server, validate the installed files before reinstalling. Stop the server first so SteamCMD can replace files that are in use, then run the documented command:
steamcmd +force_install_dir <game_server_directory_change_this> +login anonymous +app_update 1690800 validate +quitReplace the angle-bracketed directory with the actual server installation path. The command checks the app identified by 1690800 and reacquires files that do not match the depot. The dedicated-server guide also recommends repeating the original installation command to force an update check.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsValidation is preferable to deleting the whole installation because it preserves the surrounding server layout while checking the files SteamCMD manages. It is still wise to back up saves, configuration, and settings before any update or repair. After validation, launch interactively once and verify that the process remains present before returning it to a service supervisor.
Recover from SteamCMD error 0x606
A SteamCMD file-in-use error such as 0x606 means another process is holding a file open. Stop duplicate FactoryServer processes, verify that no second launch script or service is active, and run validation again. Reinstalling while the original process still owns files can reproduce the same error.
Check configuration paths and file state
Configuration files may not exist until the server has successfully started at least once. If the expected directory is missing on a new installation, launch the server once and check again rather than creating a random path.
- Linux:
<installation_directory>/FactoryGame/Saved/Config/LinuxServer/ - Windows:
<installation_directory>FactoryGameSavedConfigWindowsServer
Do not mark edited INI files as read-only. A read-only configuration can prevent the server from saving changes and can make later troubleshooting appear ineffective. Keep a copy of the last known-good file before editing, and change one related setting at a time so a later launch failure has a clear point of comparison.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRank #3
- 285G LIGHTWEIGHT BUILD — Experience superior audio and game for hours without being weighed down by the headset
- TRIFORCE 40MM DRIVERS — Cutting-edge proprietary design divides the driver into 3 parts for the individual tuning of highs, mids, and lows —producing brighter, clearer audio with richer highs and more powerful lows
- HYPERCLEAR CARDIOID MIC — An improved pickup pattern ensures more voice and less noise with the sweet spot easily placed at the mouth because of the mic’s bendable design
- HYBRID FABRIC AND MEMORY FOAM EAR CUSHIONS — Wrapped in a combination of breathable fabric and plush leatherette to provide a snug fit to ensure constant comfort for prolonged gaming
- 7.1 SURROUND SOUND — Provides accurate positional audio that lets you pinpoint intuitively where every sound is coming from. *Only available on Windows 10 64-bit
Autosave expectations
The documented default autosave interval is 300 seconds (five minutes). That is an interval, not a guarantee that every recent action is recoverable after a crash. Save manually before planned maintenance and back up the save files before changing configuration.
An autosave setting also does not replace a backup plan. Keep at least one separate copy before validation, a settings reset, an update, or a service migration. If a server is being tested with a large or important world, perform a manual save while players are disconnected or before stopping the process.
Reset corrupted administrator or server settings safely
If administrator authentication or server settings are corrupted, the dedicated-server guide specifies deleting ServerSettings.PORT.sav, where PORT is the configured port. This is a recovery step, not a routine fix.
- Stop the server completely and confirm that no duplicate process remains.
- Back up
ServerSettings.PORT.savand the save data to a separate location. - Delete the settings file corresponding to the configured port.
- Start the server and set a new administrator password and other values.
Deleting this file resets the administrator password, server name, player password, auto-load session name, and certificate. It does not preserve those settings for you, so record the intended values before the reset. If the server uses a custom port, the filename must correspond to that configured port; removing an unrelated file will not address the problem.
Use the symptom to choose the next remedy
| Observed condition | Most useful next action |
|---|---|
| No FactoryServer process | Inspect the launch command and FactoryGame.log; look for a crash report. |
| Process starts, LAN connection fails | Check listening ports and the host firewall, then validate installation files. |
| LAN works, internet connection fails | Correct router forwarding, public addressing, NAT, and ISP restrictions. |
| Process exits during launch or save loading | Capture the first fatal log line, preserve the crash directory, and validate SteamCMD files. |
SteamCMD reports 0x606 |
Stop duplicate or service-managed server processes and retry validation. |
| Authentication or settings behave as if corrupted | Back up and remove ServerSettings.PORT.sav, then reconfigure the server. |
| Server must survive reboot or crashes | Run it as a service after manual-save and backup procedures are in place. |
This comparison prevents a common wrong turn: using a destructive settings reset for a forwarding problem, or changing router rules for a process crash. Match the remedy to the first condition you can prove.
Run the server as a service for boot and crash recovery
The official service guidance states that running the dedicated server as a service can start it after system boot and restart it after a crash. This addresses a common cause of an apparently random outage: the process died hours earlier and nobody launched it again.
Before enabling a service
- Confirm the standalone launch works interactively.
- Use an absolute installation path and the intended configuration.
- Ensure the service account can read and write the installation, logs, saves, and crash directories.
- Make sure only one supervisor starts the server; a manual process plus a service can cause duplicate-process and file-lock errors.
- Test a controlled stop and restart while monitoring
FactoryGame.log. - Confirm that the service starts with the same working directory and configuration that worked during the interactive test.
Stopping the service does not automatically save the game. When players are connected, save manually before shutdown, then stop the service and perform maintenance. A restart policy improves availability, but it cannot repair a bad configuration or missing installation files; a service may simply restart the same failing command repeatedly. Inspect the log after an automatic restart rather than assuming the recovery succeeded.
Hardware and save-size expectations
No universal CPU, RAM, or disk benchmark guaranteeing a particular player count is established in the cited official material. Requirements vary with the number of players and the size and complexity of the save. Treat a process that starts but becomes unstable under load as a separate capacity investigation: preserve logs, note player count and save size, and avoid presenting an unverified hardware number as a requirement.
Do not interpret a slow load alone as proof of insufficient hardware. First establish whether the process eventually completes startup, whether LAN clients can connect, and whether the log records a fatal event. Capacity concerns are most credible when instability correlates with a larger save or more simultaneous players, not merely with an internet connection failure.
Rank #4
- 【For PC & Steam Game Conosle 】Wireless gaming controller supports PC (Windows XP/7/8/8.1/10 /11), Steam PC gaming consoles.
- 【2.4G Wireless Transmission】2.4G Wireless Transmission Technology (with USB receiver) ensures a stable connection without any delay.
- 【Improved design】The classic new left and right shoulder button design is easy to use, has 12 function keys, Supports 2 controllers at the same time (requires game support)
- 【Vibration feedback 】PC wireless controller provides automatic vibration feedback to ensure riveting gameplay every time to enhance the game experience.
- 【High-performance chip 】The PC controller uses a high-performance chip, which has good stability and zero game delay.
A complete recovery sequence
- Check for
FactoryServerwithpgrep -f FactoryServer.shon Linux or Task Manager/taskliston Windows. - If it is absent, inspect
FactoryGame.logandFactoryGame/Saved/Crashesfor the first fatal evidence. - If it is present, determine the ports actually in use and compare them with the configured values.
- Test from another device on the same LAN.
- For a LAN failure, fix the host firewall, process, configuration, or installation.
- For a LAN success but internet failure, forward every required TCP and UDP port to the correct LAN address and investigate NAT or ISP limits.
- Stop the server and run SteamCMD validation before reinstalling.
- Back up saves and settings before deleting
ServerSettings.PORT.savor changing configuration. - Once stable, place the server under service supervision if automatic boot and crash restart are required.
At each stage, change one thing and test again. That produces a usable record of what solved the failure and avoids combining a file repair, port remap, and settings reset into one opaque experiment.
Frequently Asked Questions
Why won’t my Satisfactory server start at all?
First verify that FactoryServer exists. On Linux, run pgrep -f FactoryServer.sh; on Windows, check Task Manager or run tasklist | find "FactoryServer.exe". If no process remains, inspect the current FactoryGame.log and any new directory under FactoryGame/Saved/Crashes. Capture the first fatal or error line before reinstalling. If the process starts and then exits, stop duplicate launches and validate the SteamCMD installation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The server process is running, but nobody can connect. What should I check?
Test from another device on the same LAN using the host’s LAN address. If LAN access fails, check the actual listening ports, the operating-system firewall, antivirus or Windows Defender, and the log. If LAN access works, investigate router forwarding, the host’s current LAN address, public addressing, carrier-grade NAT, and ISP restrictions. Test from mobile data or another genuinely external network because some routers do not support NAT loopback.
Which ports does a Satisfactory dedicated server use?
The documented defaults are 7777/TCP for server traffic and the HTTPS API, 7777/UDP for game traffic and the lightweight query API, and 8888/TCP for reliable messaging. Custom values are possible, but the server configuration, host firewall, router rules, and client connection details must agree. Forward every required protocol, not only UDP 7777.
Why does forwarding the default port not fix my server?
The server may be configured for a custom port, or the router rule may point to an old DHCP address. Find the values the server is actually using, reserve a stable LAN address for the host, and create matching TCP and UDP rules. Also allow the executable through the host firewall. A public-address test from inside the LAN can fail even when forwarding is correct if the router lacks loopback support.
Where are Satisfactory dedicated-server logs and crash reports?
Logs are under FactoryGame/Saved/Logs. The current file is FactoryGame.log, with rotated backups whose names contain dates and times. Crash reports are under FactoryGame/Saved/Crashes in randomly generated directories. Preserve the first fatal or error line and surrounding context before deleting files or attempting a clean reinstall.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →How do I repair a SteamCMD server without reinstalling everything?
Stop every server process and service, then run steamcmd +force_install_dir <game_server_directory_change_this> +login anonymous +app_update 1690800 validate +quit, replacing the placeholder with the real installation directory. Repeat the original installation command to force an update check. SteamCMD error 0x606 indicates that another process still has a file open, so remove duplicate launches before retrying.
What happens if I delete ServerSettings.PORT.sav?
After backing up the file and save data, deleting the file named for the configured port resets the administrator password, server name, player password, auto-load session name, and certificate. Start the server and configure those values again. This is appropriate for corrupted authentication or settings, not as a first response to a network-forwarding failure.
Can a service keep the server online after a reboot or crash?
Yes. The official service guidance says a service can start the server after system boot and restart it after a crash. First prove that an interactive launch works, use absolute paths, grant the service account access to installation and save directories, and ensure no manual process starts at the same time. Stopping the service does not automatically save the game, so save manually before planned shutdowns.
The Bottom Line
Start with the process, not the router: verify FactoryServer, test on the LAN, match the documented or custom ports across the server, firewall, and forwarding rules, then use logs and SteamCMD validation to repair startup failures. Back up settings before a reset, and use a service only after the interactive server works.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
