Fix Satisfactory Dedicated Server Not Connecting
can't connectserver won't claimofflineSatisfactory 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.
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.
Satisfactory hosting, ready to claim
Our Satisfactory hosting opens the port and gives you a clean IP to add — protected, online in minutes.
Frequently asked questions
What port does a Satisfactory dedicated server use?
Port 7777 (UDP and TCP) by default after the unified-port change. It must be open and forwarded for clients to connect.
How do I connect to a Satisfactory dedicated server?
There's no public browser. In-game open Server Manager → Add Server and enter the IP and port (7777). On first connect, set an admin password to claim it.
Why does it say the server is insecure?
Dedicated servers use a self-signed certificate by default, which triggers a warning. It's normal — accept it to continue connecting.
Why can't I connect after a Satisfactory update?
The dedicated server and the game client update separately. If the server hasn't been updated to the same patch as your client (or vice versa), the connection is refused — update both to match.
Can a corrupted save stop the server from accepting connections?
Yes — if the session fails to load properly, clients trying to connect can see it as a plain connection failure. Check the server console/log and restore from a backup save if needed.
Do I need a Steam account that owns the game to run the dedicated server?
No — the Satisfactory dedicated server binary runs independently and doesn't need a GSLT-style token or an owning Steam account, unlike some Source-engine games.
Related articles
Fix AMX Mod X "Couldn't load library" / Plugin Failed in CS 1.6
AMXX plugin stuck on "bad load", "couldn't load library" or "failed"? The real causes and the exact fix.
Read fix Game ServersFix FiveM "Couldn't load resource" / Failed to Start
A FiveM resource won't start or throws "couldn't load resource"? Here are the real causes and fixes.
Read fix Game ServersFix Rust Oxide / uMod Plugins Not Loading
Oxide/uMod plugins not loading after a Rust update? The usual causes and the quick fix.
Read fix