Satisfactory dedicated servers connect by IP (there's no public browser) and must be claimed on first connect. Here's how to get in, set it up, and the version-mismatch trap that catches most players.
Quick answer
Satisfactory has no server browser: open UDP 7777 and TCP 8888 (since patch 1.1), then add the server in-game under Server Manager → Add Server with server-ip:7777. On the first connection you claim the server and set its admin password. If it still fails, make sure the server and every player run the same game branch and version.
Open the port
Satisfactory now uses a single UDP/TCP port for the dedicated server. Open/forward:
7777/udp + 7777/tcp game (default)Add the server by IP
There's no server browser — you add it manually. In-game: Server Manager → Add Server, then enter server-ip:7777.
Claim the server
On first connect the server is unclaimed. Set an admin password to claim it, name it, then either create a new session or load a save. Until it's claimed, no one can play.
Dedicated servers show an "insecure"/certificate notice because they use a self-signed cert by default. It's expected — accept it and continue.
Open 7777 (udp+tcp), add the server by IP in Server Manager, set an admin password to claim it, then load a session.
Step-by-step: get connected and claimed
Satisfactory's setup order trips up a lot of first-time hosts. Follow it exactly:
- Make sure the dedicated server is running and its game port is open on the host firewall (not just forwarded on the router).
- In-game, open Server Manager → Add Server and enter
server-ip:port. - Accept the self-signed certificate notice — it's expected on a dedicated server.
- On first connect the server is unclaimed: set an admin password to claim it and give it a name.
- Create a new session or load a save. Until a session is loaded, players see the server but can't actually play.
The most common "suddenly can't connect" is a version mismatch: your Steam/Epic client updated but the dedicated server hasn't yet (or vice-versa). They must be on the exact same build — update the server as soon as possible after every Satisfactory patch.
Other reasons it won't connect
- Version mismatch — the dedicated server and your Steam/Epic client update on different schedules. If the server hasn't updated yet after a patch, clients on the new version can't connect. Check both versions match exactly.
- The host's OS firewall blocks 7777 even though the router forwards it — check both.
- A corrupted save prevents the session from finishing load, which looks like a connection failure from the client side.
How to prevent connection issues
- Update the dedicated server as soon as possible after every Satisfactory patch, ideally same-day.
- Keep regular save backups so a corrupted session doesn't cost progress — see general backup practice in our game server security checklist.
- Give the server a fixed, memorable session name so returning players reconnect to the right save.
Related errors
For general port-forwarding steps, see how to port forward a game server. If the connection drops mid-session rather than failing outright, see fixing "connection timed out" on game servers.
Satisfactory is a trademark of Coffee Stain Studios. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Coffee Stain.