Satisfactory dedicated-server commands are run from the server’s Console tab in the in-game Server Manager, not from the client’s debug console. First add or claim the server, set its administrator password, authenticate, and then enter version-matched syntax such as server.SaveGame FactoryBackup or quit. The documented command list is limited and was identified by the official Satisfactory Wiki as the known set for dedicated servers as of version 5.0.4, so treat older lists of chat-style commands as suspect.
This guide explains the complete supported workflow, every command in that reference, HTTPS automation, configuration locations, network requirements, security implications, and the fixes for the most common “command not working” problems.
What are Satisfactory server admin commands?
They are console instructions for a Satisfactory Dedicated Server. They control the server process, save the current world, manage Server API credentials, and adjust a narrowly scoped local-access setting. They are separate from commands typed into a normal game client.
The official reference labels its list incomplete and dates the known command set to v5.0.4. Availability and syntax can change with a server update, so check documentation matching the build actually installed before adding any command to a script.
The documented command set
| Command | Purpose | Important behavior |
|---|---|---|
quit |
Requests server shutdown. | Alias of stop and exit; a service manager may start the process again. |
stop |
Requests server shutdown. | Same shutdown operation as quit and exit. |
exit |
Requests server shutdown. | Same shutdown operation as quit and stop. |
server.SaveGame saveName |
Saves the current session under a specified name. | Put quotation marks around a name containing spaces. |
server.GenerateAPIToken |
Generates an application token for the Server API. | Treat the returned token as a credential. |
server.InvalidateAPITokens |
Revokes previously generated application tokens. | Any automation still using an invalidated token must be updated. |
FG.DedicatedServer.AllowInsecureLocalAccess 1 |
Allows unrestricted Server API access from localhost. | Applies only until the server restarts and weakens local-access protection. |
Do not assume that an internet list containing /kick, /ban, /give, or /tp describes the dedicated-server console. Those may be copied from unrelated tools, old builds, or fictional command references.
Where do I enter Satisfactory server commands?
Use the Server Manager’s dedicated-server console. The client debug console is a different interface intended for debugging information and local settings; it does not administer a dedicated server.
- Start Satisfactory and open Server Manager.
- Choose the option to add a server, enter a name, and provide the server address or connection details requested by the manager.
- For a new unclaimed server, choose Claim and set the administrator password. Keep the password in a protected password manager rather than in chat or a public configuration file.
- Authenticate as an administrator when the manager requests it. Protected settings and command execution require administrator access.
- Select the server and open its Console tab. For the v5.0.4 command reference, this is the documented execution path.
- Enter one command at a time, preserving capitalization, punctuation, spaces, and arguments. Submit it and read the console response before issuing another state-changing command.
If the server has already been claimed, add it to Server Manager and enter the existing administrator credentials instead of attempting to claim it again.
How do I shut down a dedicated server?
Enter any one of the three shutdown aliases: quit, stop, or exit. They request the same operation; choose one spelling for scripts and use it consistently.
Warn connected players before shutting down. A shutdown during construction or a save operation can interrupt their work. If the process is supervised by a system service, the service manager can automatically restart it after the command; use that service manager for routine restarts, maintenance windows, and stop/start policies.
How do I create a named save from the console?
Use server.SaveGame saveName. For example:
server.SaveGame FactoryBackupWhen the name contains spaces, enclose the complete name in quotation marks:
server.SaveGame "Before Update"Use a descriptive name that identifies the purpose or maintenance window. Creating a named save before configuration changes, version updates, or other world-state work gives you a known recovery point. Confirm the success message and verify that the save appears in the expected save list before proceeding.
Practical save naming
- Use a stable prefix such as
pre-updateormaintenance. - Add a date or sequence that is meaningful to the people maintaining the server.
- Avoid names that differ only by punctuation or capitalization when several administrators share the server.
- Do not rely on the autosave interval as a substitute for an intentional pre-change save.
How do I generate and revoke Server API tokens?
Generate an application token in the dedicated-server console with:
server.GenerateAPITokenCopy the returned value directly into the secured automation system that will use it. Do not paste it into public chat, issue trackers, screenshots, shell history that is shared with other users, or logs collected by an external service.
To revoke previously generated application tokens, run:
server.InvalidateAPITokensThis is a broad invalidation operation. Plan a replacement before rotating credentials for an automated system: generate a new token, update and test the clients that need access, then invalidate the old tokens once the new path works. If an old token is exposed, invalidate it immediately and treat every system that stored it as potentially compromised.
What does AllowInsecureLocalAccess do?
FG.DedicatedServer.AllowInsecureLocalAccess 1 allows unrestricted Server API access from localhost. The setting is temporary: it lasts only until the server restarts.
FG.DedicatedServer.AllowInsecureLocalAccess 1Use it only when you understand why a local integration needs the relaxed protection. “Localhost” limits the scope to the server machine, but the setting still weakens an access control. It does not make remote administration safe or remove the need for administrator authentication. Recheck the setting after every restart and return to the normal protected configuration when the local task is complete.
Can I automate commands through the HTTPS API?
Yes. The documented HTTPS API has a Run Command operation that executes a console command and returns its output. The operation requires administrator privileges, so automation must authenticate with valid administrative credentials or an active application token.
When to use the API
- Use the Server Manager Console for an occasional manual save, shutdown, or credential operation.
- Use the HTTPS API for scheduled jobs, monitoring systems, maintenance scripts, or an external control panel.
- Keep API tokens out of source repositories and deployment logs, and restrict the machines and accounts allowed to call the endpoint.
- Record the command, time, and returned result in an access-controlled log so an administrator can diagnose a failed run.
The API is an administration route, not a way to turn client debug-console commands into server commands. Confirm the endpoint, authentication method, and command syntax against the documentation for the installed server version.
Which settings and network ports matter?
Dedicated-server configuration files are stored below these operating-system-specific directories:
| Operating system | Configuration directory |
|---|---|
| Linux | FactoryGame/Saved/Config/LinuxServer/ |
| Windows | FactoryGame/Saved/Config/WindowsServer/ |
The official configuration documentation gives an autosave default of 300 seconds (five minutes) and a default server tick rate of 30. These are defaults, not performance guarantees. A busy factory, storage speed, CPU capacity, and network conditions can still affect how quickly the server responds or completes a save.
| Traffic | Default port | Administration implication |
|---|---|---|
| Standard server traffic | 7777 | Allow the protocol required by your deployment and firewall rules. |
| Reliable messaging | 8888 | Allow the relevant TCP/UDP rules used by the server and hosting environment. |
Internet-hosted servers must account for both ports in the host firewall, router forwarding, cloud security group, and any provider-level network policy. Opening only one port can leave the server visible but unusable for players or for a required messaging channel. Do not expose management interfaces more broadly than necessary.
What is the difference between the client debug console and the dedicated-server console?
The client debug console is opened with the keyboard console key and is designed for debug data and local settings. The dedicated-server console is the authenticated Console tab in Server Manager and is the documented place to execute the commands listed in the v5.0.4 reference.
| Characteristic | Client debug console | Dedicated-server administration |
|---|---|---|
| Access path | Keyboard console key in the game client. | Server Manager, selected server, Console tab. |
| Permission model | Client-side access. | Claimed server and authenticated administrator. |
| Typical scope | Debug information and local settings. | Shutdown, named saves, API credentials, and documented server settings. |
| Automation | Not the documented remote-administration route. | Console entry or authenticated HTTPS API Run Command. |
| Persistence | Depends on the local client setting. | Console actions affect the running server; configuration-file changes can persist across restarts. |
The official client-console guidance also says that this console cannot be used for cheating such as spawning items. More importantly for administration, opening it does not grant control over a dedicated server.
Why is a Satisfactory admin command not working?
Work through the checks in order. Most failures come from using the wrong console, missing administrator authentication, or copying syntax from a different server version.
1. Confirm the server is claimed
An unclaimed server has no established administrator identity. Return to Server Manager, add the server, choose Claim, and set the administrator password. If it is already claimed, use the existing credentials rather than creating a second claim.
2. Confirm you are in the right console
The keyboard debug console in a game client is not the dedicated-server console. Select the server in Server Manager and open its Console tab before testing a command.
3. Recheck administrator authentication
Protected operations and API calls require administrator access. A valid player connection alone is not sufficient. Sign out and authenticate again if the manager appears to have lost the administrator session.
4. Match the installed version
Check the server build and compare the command with a reference for that build. The official list is explicitly incomplete and is identified as current as of v5.0.4; a command added or removed in another release may be rejected or behave differently.
5. Check exact syntax
- Preserve capitalization in names such as
server.SaveGameandFG.DedicatedServer.AllowInsecureLocalAccess. - Include the required argument after
server.SaveGame. - Quote a save name containing spaces.
- Do not add chat prefixes, slash characters, or punctuation copied from a different command system.
- Run one command at a time so the returned error identifies the failing operation.
6. Diagnose API-specific failures
For an HTTPS Run Command failure, check administrator authorization, token validity, endpoint reachability, and whether the token was revoked by server.InvalidateAPITokens. If local access was temporarily relaxed, remember that FG.DedicatedServer.AllowInsecureLocalAccess 1 expires at the next restart.
7. Diagnose connection problems separately
If players cannot connect at all, command syntax may not be the issue. Check port 7777 for standard traffic and port 8888 for reliable messaging across the host firewall, router, cloud security group, and any provider firewall. Confirm that the rules use the protocol required by the server and that the ports are forwarded to the correct machine.
How should I operate a live server safely?
Administrative commands can affect every connected player, so use a small change-control routine.
- Announce the maintenance action and ask players to stop making world changes.
- Run
server.SaveGamewith a unique, descriptive name. - Verify the console response and the resulting save before changing credentials, configuration, or network rules.
- Make one change at a time and record the old value, new value, and time.
- Use the least powerful path that solves the task: the Console tab for a one-off operation, configuration files for persistent settings, and the HTTPS API for controlled automation.
- For shutdowns, use
quit,stop, orexitonly after players have left or accepted the interruption. - After a restart, test administrator login, API authentication, and player connectivity before declaring maintenance complete.
What should you trust when looking for more commands?
Prefer a version-matched official dedicated-server reference. The published list is described as incomplete, which means the absence of a command from the page does not prove that no internal or future command exists; it means the command is not established by that reference.
Be especially cautious with pages that present ordinary client debug commands as universal server commands or that omit the installed version. A command should be considered suitable for production only when its syntax, permission requirements, scope, and restart behavior are documented for your server build.
Operational checklist
- Server added to Server Manager and claimed.
- Administrator password stored securely.
- Command entered in the dedicated-server Console tab.
- Syntax and capitalization checked against the installed version.
- Named pre-change save created when world-state work is planned.
- API tokens treated as credentials and rotated after exposure.
- Temporary local-access relaxation understood and cleared by restart when no longer needed.
- Configuration paths selected for Linux or Windows correctly.
- Ports 7777 and 8888 allowed through every relevant network layer.
- Shutdowns coordinated with players and the service manager.
Bottom line
For the documented v5.0.4 command set, Server Manager is the authoritative entry point: claim the server, authenticate as administrator, open Console, and use exact syntax. Save deliberately before changes, protect API tokens, treat local insecure access as temporary, and verify ports and version compatibility before blaming a command for a connection or authentication problem.
Frequently Asked Questions
How should I rotate a Satisfactory API token without interrupting automation?
Generate a replacement token first and deploy it to every authorized client in a protected way. Test one client, then roll the replacement through the remaining clients before running server.InvalidateAPITokens; otherwise all existing integrations will lose access at once.
Do configuration-file edits take effect immediately on a dedicated server?
Treat configuration-file changes as restart-bound unless the version-specific documentation explicitly says otherwise. Make a backup of the relevant file, stop the server cleanly, apply the edit, and validate the result after startup.
What should I record when a command fails?
Capture the server build, the exact command text, the Console response, the administrator-authentication state, and whether the failure occurred in Server Manager or through HTTPS. That information distinguishes a syntax error from a token, permission, or network problem.
Can a hosted server expose only one of the default ports?
A deployment may appear reachable with one port open while still failing required messaging or player operations. Check the host firewall, router or cloud rules, and the provider policy for both default ports and the protocols used by your server build.
What is a safe way to test an unfamiliar command?
Use a disposable or fully backed-up world, disconnect players, and verify the command against documentation for the exact server version before testing. Never experiment first on the only copy of a production save or with credentials that are still used by automation.