SCP: Secret Laboratory server problems

Common SCP: Secret Laboratory server problems. See SCP: SL settings.

Server does not appear in the server list

Why it happens: The game’s own docs say a server must be verified by the game’s developers to show in the in-game server browser. Verification is optional and is aimed at servers with near-constant uptime.

How to fix it:

1. Wait a few minutes after Online.
2. Try direct connect with the address and port from Network. See Network and ports.
3. To be listed, the game’s guide says to fill in server_name, contact_email and max_players in config_gameplay.txt, then request verification (the guide describes typing !verify static or !verify dynamic in the server console, or emailing the game’s Safety and Compliance team) and follow their Community Server Guidelines. The guide says the email route can take 3 to 7 business days.
4. Open a ticket if you need help editing the config file or with the Console command.

Players cannot connect (“Connection refused” or timed out)

Why it happens: Wrong address or port, server offline, or a version mismatch.

How to fix it:

1. Check the status is Online.
2. Copy the primary address and port from Network.
3. Make sure players are on the same game version. See below.
4. See Can’t connect to any game server.

Version mismatch after a game update

Why it happens: SCP: SL updates often. The client and server must match.

How to fix it:

1. On a standard (Dedicated) server, keep Auto Update (AUTO_UPDATE) at 1 and restart.
2. If you use a Branch (SRCDS_BETAID), the client must be on the same branch. Changing a branch needs Settings > Danger Zone > Reinstall Server.
3. On an EXILED server, see the next issue.

EXILED server does not update, or plugins break after an update

Why it happens: With EXILED, Auto Update defaults to 0 and Version (VERSION) defaults to latest. EXILED must match the game’s version, and plugins must be built for that EXILED version.

How to fix it:

1. On Startup, check Version and set Auto Update to 1 if you want it to update.
2. Restart and read the Console.
3. Check each plugin’s page for a build for the new version.
4. If unsure, open a ticket.

Which do I have, Dedicated or EXILED?

Why it happens: There are two server types, and they show different Startup variables.

How to fix it: Open Startup. If you see Version and Auto Update only, it is EXILED. If you see Branch and Branch password, it is Dedicated. To switch, open a ticket.

Plugin load errors

Why it happens: Plugins need the EXILED framework, and must match the EXILED and game version. A plugin built for another version can fail with an error in the Console.

How to fix it:

1. Read the Console for the plugin name and the error.
2. Update or remove that plugin in Files. Plugins are normally in the EXILED plugins folder, so check the EXILED documentation.
3. Remove plugins one at a time to find the cause.
4. We cannot promise any plugin works. Ask the plugin’s author if it keeps failing.

Plugins do nothing on a Dedicated server

Why it happens: Standard Dedicated servers do not include EXILED.

How to fix it: Open a ticket to ask about the EXILED option.

How do I set up Remote Admin?

Why it happens: Staff access is set in config_remoteadmin.txt in the server’s config folder. There is no Startup variable for it.

How to fix it:

1. Open Files and find config_remoteadmin.txt. On Linux the game keeps it in a folder named after your server port, under .config/SCP Secret Laboratory/config/.
2. Add a line to the member list at the top of the file in this format: - 76561198000000000@steam: owner. There is a space before and after the dash, and a space after the colon. The role name must be one defined in the file.
3. Save and restart the server.
4. In game, open Remote Admin as described in the game’s Remote Admin guide.

Remote Admin says access denied or I have no permissions

Why it happens: The SteamID64 or role name in config_remoteadmin.txt does not match, or the file has a formatting error.

How to fix it:

1. Use the SteamID64 followed by @steam:, a space, then the role name.
2. Check role names match the file’s role list exactly, and that indentation and spacing match the other lines. This file is very picky about format.
3. Restart the server after saving.

Changing gameplay settings has no effect

Why it happens: Gameplay values (round timers, respawn and similar) live in config_gameplay.txt. Edits only apply after a restart.

How to fix it:

1. Edit config_gameplay.txt in Files and save.
2. Restart the server.
3. Watch the Console for a config error.

Server crashes on startup

Why it happens: A bad config file, a broken plugin, or a failed update.

How to fix it:

1. Read the last lines of the Console.
2. If you recently edited a config, undo the change.
3. If you use plugins, remove the newest one.
4. See Server keeps restarting.

Server runs out of memory

Why it happens: Big player counts and plugins use a lot of memory.

How to fix it: See Out of memory. Remove plugins first, then consider Upgrade.

Beta branch will not install

Why it happens: Branches are installed by the reinstall script and need the right password.

How to fix it:

1. Enter the Branch and (if needed) Branch password.
2. Go to Settings > Danger Zone > Reinstall Server. This can overwrite config, so make a backup first. See Backups.

Still stuck?

Open a ticket or ask on Discord. See Contact support.