How to port forward a Satisfactory server
Since the 1.0 release a dedicated server needs port 7777 on both TCP and UDP. Gameplay moves over UDP, while the server API and part of the initial handshake use TCP on the same number, so opening one and not the other produces a server that is discoverable but never quite connects.
Your setup
Pick the firmware family, not the exact model — the menus are identical across a range.
Default is 7777. If you changed it, it is the value of -Port= launch argument.
The private address of the machine running the server — ipconfig on Windows, ip addr on Linux. It starts with 192.168, 10. or 172.
Open these
This firmware accepts ranges, so each line below is a single rule.
- 7777 TCP
- 7777 UDP
7777UDPGame trafficAll gameplay runs over UDP on this port.7777TCPReliable messaging / APISatisfactory 1.0 added a TCP channel on the same port number for the server API and the initial handshake. Forward both protocols.
Old versions only
Current builds do not use these. They are listed because older guides still tell people to open them.
15777UDPLegacy queryOnly servers older than Update 6 use this. A current install does not need it.15000UDPLegacy beaconPre-Update 6 discovery beacon. Skip it on any modern build.
Do not open these
This game has no remote-administration port to get wrong. Forward only what is listed on the left and nothing else.
Step by step: your router
- 1
Give the server a fixed local IP
A forward points at one address. If the server picks up a different one after a reboot, the rule silently starts pointing at nothing — this is why forwards "stop working" on their own.
On this router:look for DHCP Reservation, Address Reservation, Static Lease or Manually Assigned IP
- 2
Open the router admin page
Try these addresses in a browser on the same network:
- 192.168.0.1
- 192.168.1.1
- 192.168.2.1
- 10.0.0.1
Almost always printed on a sticker on the router itself.
- 3
Find the port forwarding page
Port Forwarding, Virtual Server, NAT, Applications & Gaming, or Port Mapping
Vendors use at least six names for the same feature. Whatever it is called, the page you want is the one asking for a port, a protocol and a device on your network. If the external and internal port fields both exist, set them to the same number.
- 4
Create one rule per line
a description field, if there is one External / WAN / Public / Service port Internal / LAN / Private port Protocol Internal IP / Device / Server IP Satisfactory 7777 7777 TCP your server’s local IP Satisfactory 7777 7777 UDP your server’s local IP External and internal port are the same number here. Changing the external port is possible, but then everyone connects on the new one, so keep them matched unless you have a reason.
- 5
Let the server through its own firewall
The router now sends traffic to the machine, and the machine can still refuse it. Windows Defender Firewall in particular blocks a freshly installed dedicated server by default, which looks exactly like a failed forward.
Take it with you
Satisfactory — port forwarding rules ------------------------------------ 7777 TCP -> <server local IP> 7777 UDP -> <server local IP>
Check whether it worked
Test from outside your own network. Connecting from a machine in the house proves nothing — that traffic never leaves the LAN and never touches the rule you just wrote.
What usually goes wrong
Guides written before Update 6 tell you to open 15777 and 15000 as well. Those were the old query and beacon ports and current builds do not use them. Opening them does no harm beyond leaving two unnecessary holes in your firewall, but their absence is not why your server is unreachable.
Not forwarding at all
Satisfactory can host a session directly from a player's game client, which uses the same ports but has to be running for anyone to play. A dedicated server is what makes the world persistent, and a rented one arrives with its ports already open.