Satisfactory 1.0: Connection & Auth Fixes
Since the 1.0 Release, dedicated servers have changed significantly. The old manageable "Query Ports" are gone, and a new secure authentication system is in place. This guide fixes the most common errors.
1. The Golden Port: 7777
Forget 15777 or 15000. Satisfactory 1.0 uses **Port 7777** (UDP & TCP) for almost everything. Ensure your firewall allows this.
2. "Encryption Token Missing"
This error happens when you try to use "Join Game" via Steam/Epic friends list to join a Dedicated Server. **You cannot do this.** You must use the Server Manager.
3. Tier 0 Skipped?
This is not a bug. Dedicated Servers intentionally skip the "Onboarding" (Tier 0) tutorial phase. You start at Tier 2 functionality.
Authentication Issues
"Invalid Authentication Token"
- Token Expired: Authentication tokens have limited lifetime. Generate new token.
- Password Change: If admin changed server password, old tokens become invalid.
- Corrupted Token: Token file corrupted. Remove server and re-add.
- Network Issues: Connection interrupted during authentication. Try again.
"API Disconnected"
- Server Offline: Server not responding to authentication requests.
- API Timeout: Server taking too long to respond. Retry connection.
- Port Blocked: Port 7777 blocked by firewall or ISP.
- Service Down: Satisfactory authentication service experiencing issues.
"Failed to Connect"
- Version Mismatch: Client and server on different game versions.
- Mod Incompatibility: Mods causing connection issues. Try vanilla.
- Network Unstable: Connection dropping during handshake. Check internet.
- Server Full: Maximum player capacity reached. Wait for slot.
Advanced: The Docker/Multihome Bug
If your server is crashing or invisible:
- Remove Multihome: Do NOT use the `-multihome=X.X.X.X` flag anymore. It breaks the internal API binding on 1.0 servers.
- Docker Network: If running in Docker, you must set the network mode to `Host`. Bridge mode often blocks the secure handshake packets.
Note: If your server says "Offline" but is clearly running, try simply restarting it via the Supercraft Panel. The 1.0 server software has a known bug where the API "goes to sleep" after long periods of inactivity.
Automate the factory. Host your Satisfactory server with Supercraft, where all ports are pre-configured, and the API is monitored 24/7 for stability.