Satisfactory Server Not Showing in Server Manager
If your server does not appear in the in-game Server Manager, it is almost always a port, claim, or firewall issue. Follow these steps in order.
Patch 1.1+ Users: Since Patch 1.1.0.0, you must have both Port 7777 AND Port 8888 open. Many servers stopped showing after this update because only 7777 was forwarded.
On a hosted server this section does not apply. Your host opens the ports for you, and they are your server's own port and the next one up, not 7777 and 8888. The steps below are for a server you run on your own machine or network.
Quick Diagnostic Table
| Check | Why It Fails | Fix |
|---|---|---|
| Port 7777 (UDP+TCP) | Blocked game traffic | Open UDP and TCP on port 7777 |
| Port 8888 (TCP) | Missing reliable messaging port (1.1+) | Open TCP on port 8888 |
| Server claimed | Unclaimed servers don't show properly | Claim via Server Manager first connection |
| Multihome flag | -multihome breaks API in 1.0+ | Remove -multihome from launch params |
| IP format | Missing port in address | Add using address:port, with the port your host shows (7777 only if you launched the server yourself) |
Step-by-Step Fix
- Add the server manually. In Server Manager, click Add Server and enter the address and port your host shows, as
address:port. On a hosted server that port is on your panel page, not 7777. - Confirm the port is open. On Supercraft it already is, so skip this step. If you run the server yourself, see Connection Issues for firewall rules and tests.
- Claim the server once. Use the claim flow in Configuration Guide.
- Check server name vs session name. See Change Server Name.
- Review logs for startup errors. Use View Logs to confirm the server finished booting.
Port Testing
# Check if ports are listening (Linux)
netstat -tulpn | grep -E "7777|8888"
# Test connectivity from another machine
nc -zvu YOUR_SERVER_IP 7777 # UDP
nc -zv YOUR_SERVER_IP 7777 # TCP
nc -zv YOUR_SERVER_IP 8888 # TCP (1.1+ only)Firewall Configuration
# Windows PowerShell (Run as Administrator)
New-NetFirewallRule -DisplayName "Satisfactory 7777" -Direction Inbound -Protocol UDP -LocalPort 7777 -Action Allow
New-NetFirewallRule -DisplayName "Satisfactory 7777 TCP" -Direction Inbound -Protocol TCP -LocalPort 7777 -Action Allow
New-NetFirewallRule -DisplayName "Satisfactory 8888 TCP" -Direction Inbound -Protocol TCP -LocalPort 8888 -Action Allow
# Linux iptables
sudo iptables -A INPUT -p udp --dport 7777 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 8888 -j ACCEPTStill Not Showing?
Additional Troubleshooting:
- Validate server files: Run
steamcmd +login anonymous +app_update 1690800 validate +quit - Check logs: Look for errors in server log files - see View Logs
- Restart server: The API can "go to sleep" after long inactivity
- Remove -multihome: This flag breaks API binding in 1.0+
- Docker users: Use
network_mode: hostor ensure all ports are mapped
Note: Port redirection is NOT supported - external and internal port numbers must match in your port forward rules.
Keep factories online. Host your Satisfactory server with Supercraft for pre-configured ports and monitored auth services.