How to Claim a Satisfactory Dedicated Server Safely

A Satisfactory dedicated server starts unclaimed, so the first person who reaches it through Server Manager can become its admin. To claim it, add the server in the PC game, set a server name and an admin password, then optionally set a separate password for players who join. This guide covers the normal claim, the documented API path and what to save before resetting a claim that is already taken. Dedicated servers are for PC players on Steam and Epic; PlayStation and Xbox players cannot join them.

Choose the right Satisfactory server for your group#

Check platforms before you spend time claiming anything. Steam and Epic players can play together on a PC dedicated server. PlayStation and Xbox players can play with each other, but Coffee Stain keeps console and PC separate: consoles cannot join dedicated servers or cross-play with PC. If someone in your group is on console, a dedicated server will not bring that player into your world. The official support FAQ spells out the platform limit.

If your group plays on Steam or Epic and you would rather skip the initial claim setup, Game Hosting’s Satisfactory server is already claimed for its owner, and the generated admin password appears in panel Settings. That saves the owner from exposing a new server while the group figures out the first connection. The service is for PC players; it does not add console compatibility.

For a server you control, claiming means assigning the server identity and the password that protects administrator access. It does not create a world by itself. After the claim, you can create a new session or load an existing save in Server Manager. The whole install and network setup is covered in the self-hosting walkthrough; this page focuses on first ownership and safe recovery.

Understand the admin and player passwords#

Satisfactory has two distinct passwords. The admin password lets its holder manage the dedicated server: for example, rename it, choose a session, change server options and use administrative functions. You set this password when you claim a new server. It should be known only to the people who need to manage the server.

The player password, also called the Client Protection Password in the API, is optional. It limits who can join as a regular player. Leaving it unset does not make an unclaimed server safe: the first person who reaches the server before it is claimed can become its administrator. Set the claim first, then decide whether your group needs a join password. Never hand friends the admin password just because they need permission to play.

There is no default admin password to look up. A provider should tell you who claims the server and how you receive its admin credential. For a server you own, keep a record in a password manager before you close the claim screen. The password itself is stored with the server’s settings; do not expect to recover it by opening a text file.

Claim the server through Server Manager#

Use the game’s Server Manager rather than the normal Join Game menu. The Server Manager connects to the dedicated server’s HTTPS API. When the server has no custom certificate, it generates a self-signed certificate; confirm that the address is the server you intended before trusting it. The official dedicated-server guide documents this flow.

1. Restrict access while the server is unclaimed

   Start the server but keep its public access limited while you prepare the first claim. For a home server, do not announce the address or open it broadly until you have claimed it. The first successful claimant becomes the administrator.

2. Add the server in the PC game

   Open Server Manager → Add Server from the main menu and enter the address and game port. The current default game port is 7777; a home-hosted server also needs Reliable Messaging on TCP 8888. The port note is only for finding a home server; use the address and port your provider gives you for a managed server.

3. Verify the certificate prompt

   If the server presents a self-signed certificate, check that its address matches the one you entered and accept it only for that intended server. This establishes the encrypted Server Manager connection; it is not a signal to disable certificate checks in another tool.

4. Claim and record the credentials

   Follow the claim prompt, enter a clear server name, and create a strong admin password. Store that password securely before leaving the prompt. The server should now appear as claimed and let you manage its settings.

If the server remains unclaimed, check that you added its actual game address, that it has finished starting, and that your client and server are on compatible builds. On a home network, 7777 uses both UDP for game traffic and TCP for the management API; TCP 8888 carries reliable messaging. Older instructions for ports 15000 or 15777 are obsolete. The official port table lists the current defaults.

Claim it with the HTTPS API if you are scripting#

The HTTPS API offers the same first claim without a Server Manager click-through. Use this only for a server you control, and keep the API connection on TLS. The flow is two requests: ask for an InitialAdmin token while the server is unclaimed, then use that token to call ClaimServer with the new name and admin password. A claimed server cannot grant this initial privilege again.

The request data for the first call is:

{
  "function": "PasswordlessLogin",
  "data": {
    "MinimumPrivilegeLevel": "InitialAdmin"
  }
}

Use the returned authenticationToken as a bearer token for the second request:

{
  "function": "ClaimServer",
  "data": {
    "ServerName": "Your Factory",
    "AdminPassword": "your-new-strong-admin-password"
  }
}

These are request bodies, not a complete shell command; send them as JSON POST requests to /api/v1 on the server’s HTTPS port. A server without a custom certificate uses a self-signed one, so a script must handle the certificate safely. Do not paste the real admin password or API token into a public post or an unreviewed third-party tool. The HTTPS API reference documents PasswordlessLogin, InitialAdmin and ClaimServer.

Create or load a world after the claim#

Claiming secures administrator access; it does not start a factory. In Server Manager, choose Create Game for a new world or Manage Saves to upload a PC save you own. Check the session name and selected save before you start. Steam and Epic PC saves are supported; console saves cannot be moved to a PC dedicated server because the platforms are separate.

If you are importing a world, keep an untouched copy of the original save until the server has loaded the intended session. A claim reset is a server-settings operation, not a world migration, but it can clear the name, passwords, certificate and auto-load session stored in:

ServerSettings.<port>.sav

The world files live separately. After a reset, you may need to select the intended session again before the server starts the factory.

The save screen is the right place to verify that the world you meant to start is present. If you need to move a co-op save or compare the entire self-hosted process, use the complete dedicated-server walkthrough before deleting or replacing your only copy.

Recover carefully if the server says it is claimed#

The API returns server_claimed when ClaimServer is called after someone has already claimed the server. Stop repeating the request. First confirm that the address belongs to your server and ask its owner or provider whether the server was claimed during provisioning. If it is managed, request access through the provider; do not try to reset a server you do not own.

If you own the machine and intentionally need to clear a mistaken claim or forgotten admin credential, the documented reset removes the server settings file. That file also holds server name, player password, auto-load session and the TLS certificate, so this is a full settings reset rather than a password-only change. Make a recoverable copy before you stop or remove anything.

Use the in-game server console or authenticated API to run this command for the active session:

server.SaveGame <save-name>

Confirm it returns successfully; then stop the server cleanly. Copy the relevant world save and settings file to a separate location. With the server stopped, remove only the settings file for the correct game port, start the server again, and claim it yourself before restoring public access. You will need to set the name and passwords again and choose the desired auto-load session. The official admin-password reset FAQ explains which settings file to remove.

If you only lost the admin password and already control the server, reset guidance belongs to that narrower recovery task. For now, keep a separate copy of your settings and world before asking a provider or deleting files.

Check the claim before you share the server address#

Before you invite the group, make sure the server appears as claimed in Server Manager, that you can authenticate with the admin password, and that a regular player can join using the optional player password if you set one. The claim process is complete when the server has a name and an administrator, not merely when its process is running. Keep the admin credential private and give players only the join details they need.

For home hosting, double-check that you opened the current port protocols rather than copying a pre-1.0 port list. 7777 is used over UDP and TCP, while 8888 is TCP for reliable messaging. For managed hosting, use the provider’s current connection card and ask how it handles save-before-stop behavior. An address that responds to a port check does not by itself prove that the game handshake or claim succeeded.

Once the first claim is secure, the next decisions are the player password, session, updates and save routine. The broader Satisfactory server setup guide explains how those pieces fit together. If your group is on console, use a console-hosted game instead; a rented or self-hosted PC dedicated server cannot bridge that platform gap.