This guide focuses on the current network ports, launch parameters and INI configuration for a dedicated server. For console multiplayer compatibility, see our Satisfactory crossplay guide. The reviewed Satisfactory version 1.2.4.0 launched on August 11, 2026.
The key difference from older guides: Since Satisfactory 1.1, the dedicated server needs TCP 8888 for Reliable Messaging in addition to the ordinary server port 7777. Coffee Stain introduced this requirement in update 1.1, and the current server documentation reviewed for this article retained it.
Which ports does a Satisfactory dedicated server need?
| Port | Protocol | Use |
|---|---|---|
| 7777 | TCP | Server traffic and HTTPS API |
| 7777 | UDP | Game traffic and Lightweight Query API |
| 8888 | TCP | Reliable Messaging |
With default settings, allow 7777/TCP, 7777/UDP and 8888/TCP through your firewall and configure corresponding forwarding when the server sits behind a NAT router.
Why outdated port lists can be wrong
Satisfactory networking has changed several times. Ports 15000 and 15777 are no longer used as of version 1.0 according to the reviewed documentation. An intermediate 1.0.1.6 guide also required TCP 27777; version 1.1 introduced the new Reliable Messaging service on TCP 8888. The table above therefore reflects the 1.1-and-later configuration instead of a combination of obsolete port lists.
Set the base port using -Port
The basic launch argument is:
-Port=7777It controls both the TCP and UDP port used by the ordinary server traffic. The current documentation says mapping this base port to a different external port is not supported. If the server listens internally on 7777, configure external forwarding to 7777 as well.
Set the Reliable Messaging port
The second service uses its own launch argument:
-ReliablePort=8888If you explicitly choose an occupied port, the server cannot bind it. When no fixed value is supplied, the automatic search begins at TCP 8888 by default and can look for another available port within a configurable range.
Unlike the main -Port, Reliable Messaging supports specifying a distinct external port through:
-ExternalReliablePort=8888This matters when NAT or a hosting platform translates between internal and external Reliable Messaging ports. The server must know the public-facing port to give clients the correct destination after the handshake.
Configure the Reliable Port range in Engine.ini
Automatic port selection can be configured in Engine.ini. The documented defaults are:
[/Script/ReliableMessaging.ReliableMessagingTCPFactory]
PortRangeBegin=8888
PortRangeLength=512
ExternalPortRangeBegin=-1These settings start at 8888 and permit a search across up to 512 ports. One dedicated server is easier to audit with a clearly defined -ReliablePort. A range can be useful when several instances share a machine, provided firewall and NAT settings reflect the selected ports.
Where to find Engine.ini and Game.ini
The dedicated-server configuration lives relative to its installation folder:
- Linux:
<installation_directory>/FactoryGame/Saved/Config/LinuxServer/ - Windows:
<installation_directory>\FactoryGame\Saved\Config\WindowsServer\
The relevant files may not exist until the server has started at least once and then shut down properly. Edit INI files while the server is fully stopped: clean shutdown can write current runtime settings back to the files and overwrite manual changes.
Allow more than four players
The default player limit is four. To allow more participants, add a value such as the following to Game.ini:
[/Script/Engine.GameSession]
MaxPlayers=8The server also accepts this command-line form:
-ini:Game:[/Script/Engine.GameSession]:MaxPlayers=8The official wiki mentions a theoretical maximum of 127 players while warning that substantially increasing capacity affects performance, resource use and stability. Increase the limit gradually and monitor server load rather than treating 127 as a practical recommendation.
Server name and passwords
Normal settings such as the server name, administrator password, player password and other options can be managed through the integrated Server Manager. You generally do not need to edit the INI files for those ordinary options.
Troubleshoot common connection issues
- Server appears but joining hangs or fails: Check that TCP 8888 is available in addition to TCP and UDP 7777.
- Forwarding exists but connections fail: The external and internal base
-Portnumbers should match. - Reliable port translated by NAT: Configure
-ExternalReliablePortor the appropriateExternalPortRangeBegin. - INI edits disappear: Change files only with the server stopped; updates may also alter configuration.
- Multiple servers on one IP: Give each instance separate base and Reliable Messaging ports or compatible port ranges.
Revert configuration changes
Back up Engine.ini and Game.ini before changing port ranges, player counts or related settings. If something breaks, restore the previous files or remove the changed sections. Do not mark the INI files as read-only; the documentation warns that this can create update problems.