Quick answer: open port 7777 on both UDP and TCP, and since update 1.1 also TCP 8888. Everything else the older guides mention (15000, 15777) was removed when Satisfactory hit 1.0 and consolidated onto 7777.
The Actual Port List
| Port | Protocol | What it carries | Required |
|---|---|---|---|
| 7777 | UDP | Game traffic | Yes |
| 7777 | TCP | Server API and HTTPS (server list, login) | Yes |
| 8888 | TCP | Reliable messaging channel, added in update 1.1 | Yes since 1.1 |
The pre-1.0 beacon port (15000) and query port (15777) no longer exist. If a tutorial tells you to open them, it predates 1.0.
The 8888 Symptom Everyone Hits
Update 1.1 added a separate reliable-messaging channel on TCP 8888 next to the existing 7777 traffic. A server with 7777 open but 8888 blocked produces a specifically confusing failure: the server shows online in the browser, the status queries work, and then actual joins silently hang. If your players report exactly that pattern after 1.1, check 8888 before anything else.
On a Linux server, the firewall rules look like:
ufw allow 7777/udp
ufw allow 7777/tcp
ufw allow 8888/tcp
Both ports can be changed with launch options (-Port= and -ReliablePort=) if something else occupies them, in which case forward whatever you chose instead.
Checklist
- Open UDP 7777, TCP 7777, and TCP 8888.
- Close the legacy 15000/15777 rules if an old setup left them open.
- Back up saves before updates.
- Update server and client together, version mismatches also block joins.
- Monitor RAM as the factory grows.
Mistakes to avoid
- Following pre-1.0 tutorials that open 15000/15777 and skip 8888.
- Opening 7777 UDP but forgetting 7777 TCP, the API side needs it.
- Ignoring save backups.
- Underestimating late-game factory load.
Space-Node recommendation
Use VPS hosting for custom Satisfactory servers or a managed game server if you want less admin work.
FAQ
Is the cheapest option good enough?
Sometimes. The cheapest option is fine for testing, learning, and small private projects. For public servers, business workloads, monetized streams, or communities with regular users, stable uptime and support matter more than saving a few euros.
Should I choose managed hosting or a VPS?
Choose managed hosting when you want the service online quickly with less server administration. Choose a VPS when you need root access, custom software, Docker, unusual configs, or multiple services on one machine.
What should I check before ordering?
Check CPU, RAM, storage type, bandwidth policy, support scope, backups, upgrade path, and whether the product actually matches your workload. A good plan is the one that matches the bottleneck you will really hit.
If you would rather not run the machine yourself, our Satisfactory hosting plans cover the setup described above.