# Troubleshooting Your Subnautica Nitrox Server (/docs/subnautica/troubleshooting)



import { Step, Steps } from 'fumadocs-ui/components/steps';

Most "I can't connect" tickets for Subnautica Nitrox come down to four causes. Work through this page top to bottom -- the issues are ordered by how often they cause problems.

Quick Checklist [#quick-checklist]

Before diving in, run through this list. About 90% of Nitrox issues are on it:

1. Is the server **running**? (look for `Server is waiting for player` in the console)
2. Does the console port match the **Network** tab port?
3. Is `AutoPortForward` set to `False`?
4. Does the **password** in the save config match what players are entering?
5. Are all players on the **same Nitrox version** as the server?
6. Are you editing the config in `.config/Nitrox/saves/`, **not** in `subnautica/`?

If any of those answer "no" or "not sure", the right section is below.

Cannot Connect to Server [#cannot-connect-to-server]

Cause 1: Port Mismatch (most common) [#cause-1-port-mismatch-most-common]

Look at your server console. If it says `Listening on port 11000` but your server's port (shown on the **Network** tab in the [panel](https://panel.xgamingserver.com)) is different, that is the problem.

**Fix:**

<Steps>
  <Step>
    Open File Manager [#open-file-manager]

    Navigate to `.config/Nitrox/saves/My World/server.cfg` (replace `My World` with your save name if you changed it).
  </Step>

  <Step>
    Update ServerPort [#update-serverport]

    Set `ServerPort` to the value shown on the panel's **Network** tab.
  </Step>

  <Step>
    Restart the server [#restart-the-server]

    Confirm the console now logs the correct port on startup.
  </Step>
</Steps>

Cause 2: AutoPortForward is True [#cause-2-autoportforward-is-true]

UPnP does not work on hosted servers. If `AutoPortForward` is `True`, Nitrox tries to open ports itself and may fail or behave unpredictably.

**Fix:** Set `AutoPortForward = False` in `.config/Nitrox/saves/My World/server.cfg` and restart.

Cause 3: Nitrox Version Mismatch [#cause-3-nitrox-version-mismatch]

Server and all players must be on the **same Nitrox version**. If the server runs `1.8.1.0`, every client also needs `1.8.1.0` -- not `1.8.0.0`, not `1.7.x`.

**Fix:** Check the server version on the **Startup** tab (or in the console banner) and ask every player to install the matching version from the [official Nitrox download page](https://nitrox.rux.gg/download). See [Updating Nitrox](/docs/subnautica/update-nitrox) for the full upgrade flow.

Cause 4: Password Mismatch [#cause-4-password-mismatch]

If players enter the password but still can't connect, the password in the save config may not match what they were given.

**Fix:** Open `.config/Nitrox/saves/My World/server.cfg` and check `ServerPassword`. Make sure it matches what you set in the **Startup** tab and what players are typing.

> 📝 **Note:** Settings on the **Startup** tab and settings inside `server.cfg` can drift apart. The save config is the source of truth at runtime.

"Server is not visible / not in my server list" [#server-is-not-visible--not-in-my-server-list]

Subnautica Nitrox has no public server browser. Players join by **manually adding the server** in the multiplayer menu using the IP and port from your panel's **Network** tab. There is no list to be missing from.

"I edited server.cfg and nothing changed" [#i-edited-servercfg-and-nothing-changed]

You probably edited the wrong file. Nitrox v1.8+ ignores `server.cfg` in the `subnautica/` game directory. The file Nitrox actually reads is:

```
.config/Nitrox/saves/{SaveName}/server.cfg
```

The default save name is `My World`. See [Configuring Your Server](/docs/subnautica/configure-your-server) for the full path and settings list.

"I changed the save name and lost my settings" [#i-changed-the-save-name-and-lost-my-settings]

Each save has its own config. When you change `SaveName` on the **Startup** tab and start the server, Nitrox creates a fresh `server.cfg` with default values in:

```
.config/Nitrox/saves/{NewSaveName}/server.cfg
```

Your port, password, and other tweaks need to be re-applied to the new save's config. Your **previous** save's config is not gone -- it's still in the old folder under `.config/Nitrox/saves/`. If you switch back to the old save name, the old settings come back.

"Console commands aren't working" [#console-commands-arent-working]

Two things to check:

1. **You need to be logged in as admin.** In-game, press `Y` to open chat, then run `/login <AdminPassword>`. Find `AdminPassword` in `.config/Nitrox/saves/My World/server.cfg`.
2. **Vanilla Subnautica console commands require activation.** In single-player you press `F3` then click the checkbox to enable the console. The Nitrox-aware versions of those commands run from chat (`Y`) once you're an admin.

See [Admin Commands](/docs/subnautica/admin-commands) for the full list.

"World is desynced / teammate's base is missing" [#world-is-desynced--teammates-base-is-missing]

Open the in-game options menu and switch to the `Nitrox` tab. Click **Resync base buildings**. This forces a re-fetch of base structures from the server.

If desync persists across multiple resyncs, the underlying save may be corrupt -- back up first, then see [Backup & Restore](/docs/subnautica/backup-restore) or [Reset Server](/docs/subnautica/reset-server).

"Server crashed / save corrupted" [#server-crashed--save-corrupted]

<Steps>
  <Step>
    Stop the server [#stop-the-server]

    Don't keep restarting into a crashing state -- it can compound corruption.
  </Step>

  <Step>
    Check .config/Nitrox/saves/My World/ for backups [#check-confignitroxsavesmy-world-for-backups]

    Nitrox writes backup files alongside the active save. Restoring from backup is covered in [Backup & Restore](/docs/subnautica/backup-restore).
  </Step>

  <Step>
    As a last resort, reinstall [#as-a-last-resort-reinstall]

    If no backup loads cleanly, see [Reset Server](/docs/subnautica/reset-server). This wipes progress.
  </Step>
</Steps>

Still Stuck? [#still-stuck]

Join our [Discord](https://discord.xgamingserver.com) with:

* Your server IP and port (from the panel's **Network** tab)
* Your Nitrox version (server console banner)
* The exact error message players see
* Whether the server is logging anything in the **Console** tab

We'll get you back online.
