Free tools Windows power users keep installed
One-click scans. No signup required.
Nitrox 1.8.0.0 is an alpha multiplayer modification for the PC version of Subnautica. It supports the final Subnautica 2025 Patch, but not older Subnautica versions. This guide covers the dedicated-server console, operator permissions, networking on UDP port 11000, saves, backups, and the limitations you need to plan for.
Godlike.Host offers hosted Subnautica (Nitrox) servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
For a reliable setup, every player must run the same Nitrox version, the host must make UDP 11000 reachable (by router forwarding or a VPN), and the server should be stopped with the stop command before files are copied or updated.
As an Amazon Associate I earn from qualifying purchases.
Nitrox compatibility and prerequisites
Nitrox 1.8.0.0 introduced a rewritten launcher and server architecture, multiple-server management in the launcher, world-backup restoration, and broad synchronization improvements. It is still labeled alpha, so a few multiplayer systems remain incomplete. Experimental Linux support is included, but compatibility should be verified on the particular distribution and installation you use.
Match the Subnautica and Nitrox versions
Nitrox 1.8.0.0 supports the final Subnautica 2025 Patch and drops support for older Subnautica builds. A player on a different Nitrox release, or on a Subnautica build that Nitrox no longer supports, can fail to connect or experience desynchronization. Update the server and all clients together, and do not assume that a previously working older installation remains compatible after Subnautica updates.
#1 Best Overall
- Survival is key: gather valuable materials, craft tools, manage your hunger and thirst, all while evading the dangerous wildlife that sees you as its next meal
- the mysteries submerged on planet 4546b: you came here in search of answers. You risked everything to get here and you will not leave until you have uncovered the truth…
- exploration: Delve into unique Aquatic and terrain biomes that will unlock not only materials, but the answers that you seek
- build your habitat: crafting and building the comforts of home here. These bases will be integral for your survival from not only the wildlife, but also the harsh environment around you
Game ownership and installation
The setup requirements call for a legitimate Steam account that owns the PC version of Subnautica. Each player needs the base game installed before launching Nitrox. Keep the game and Nitrox installations on the same machine when you are testing a local server, and verify that the launcher can detect the game before troubleshooting network issues.
Start a server and identify its connection details
- Install the supported Subnautica build and Nitrox 1.8.x on the host computer.
- Open NitroxLauncher and choose the server-start option. The rewritten launcher can manage more than one server, so select the intended instance before starting it.
- Read the server window. It displays the selected game mode, server password, admin password, and local and public IP information.
- Give players the public IP address (or the VPN address when using a VPN) and UDP port
11000, along with the in-game server password if one is configured.
The server process should remain open while players are connected. Use the console’s stop command, or the host panel’s Stop button, for an orderly shutdown that saves the world before exiting.
Networking: UDP 11000, forwarding, VPNs, and firewalls
Direct internet hosting
Nitrox uses UDP port 11000. On a typical home connection, create a router port-forwarding rule for UDP 11000 to the computer running NitroxServer-Subnautica.exe. The computer’s private address should be reserved in the router so the forwarding rule does not break when DHCP assigns a new address.
- Forward UDP, not only TCP.
- Forward to the host’s current private IPv4 address.
- Give friends the public IP shown by the server window, not the private address beginning with ranges such as 192.168.x.x or 10.x.x.x.
- If your internet service uses carrier-grade NAT, ordinary forwarding may not work; use a VPN path or a connection that provides an inbound public address.
VPN hosting
A VPN such as Hamachi can provide a private network path when router forwarding is unavailable. All players must join the same VPN network, and the host should provide the VPN-assigned address together with port 11000. The VPN adapter may change which address Nitrox displays, so confirm the address in the server window and test from another player rather than relying on a remembered value.
Firewall exceptions
Allow both Subnautica.exe and NitroxServer-Subnautica.exe through the host operating system’s firewall. Permit UDP traffic on port 11000 for the network profile you actually use. A successful local launch does not prove that an external connection is permitted; test from a different network, such as a friend’s home connection or a mobile hotspot.
Rank #2
- Size: 5" - Paint-Safe & Residue-Free: Features a heavy-duty magnetic backing that stays secure at highway speeds but can be removed instantly with zero sticky residue or paint damage.
- Built for the Road: Crafted from high-quality, 100% waterproof and weatherproof material that handles rain, sun, and road grime without fading.
- Interchangeable & Versatile: Perfect for those who want to swap designs frequently between vehicles, lockers, or any flat magnetic metal surface.
- The 5-Inch Standard: Perfectly sized at 5" for maximum visibility on trunks, tailgates, or refrigerators without crowding your space.
- Indoor & Outdoor Ready: UV-resistant ink ensures these magnets remain vibrant whether they are on your car or decorating your office gear. Proudly Made in the USA with industrial-grade materials and precision-cut edges for a professional, high-end look.
Dedicated-server console commands
Enter these commands in the Nitrox server console. Names containing spaces should be entered exactly as the server expects; if a command fails, run help first because command parsing and permissions can change between releases.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →| Command | Purpose | Operational note |
|---|---|---|
help |
Lists the server commands available in the running build. | Use this as the authoritative syntax check after updates. |
say [message] |
Broadcasts a message to connected players. | Useful for maintenance notices and planned restarts. |
list |
Shows players currently connected. | Use the displayed name when issuing moderation commands. |
kick [name] |
Removes a player from the server. | The player can reconnect unless separately banned. |
ban [name] |
Bans a player. | Reserve for deliberate moderation action; record the name and reason separately. |
unban [name] |
Removes an existing ban. | Use the exact identity shown by the server. |
save |
Forces an immediate world save. | Run it before maintenance, backups, or a planned restart. |
op [name] |
Grants operator or administrator permissions. | Only trusted users should receive this level of access. |
deop [name] |
Removes operator or administrator permissions. | Use it when a moderator no longer needs elevated access. |
stop |
Shuts the server down cleanly. | Prefer this command or the host panel’s Stop button so the world is saved. |
Console commands versus in-game commands
The console list above is distinct from the synchronized Subnautica commands added in the 1.8 release line. Release notes document in-game support for spawning, teleport, goto, warp, gamemode changes, keep-inventory, PvP, fastGrow, fastHatch, and Sunbeam and Aurora events. Vehicle teleportation is covered by the teleport, goto, and warp functionality. Exact syntax and the permission required for each command are version-sensitive, so run the server’s help output and test on a disposable world before using them on a shared save.
Make yourself an administrator
Set a private admin password
Admin authentication is configured in server.cfg. The setting may appear as SUBNAUTICA_ADMIN_PASSWORD or AdminPassword, depending on the configuration format in your installation. The documented default is PleaseChangeMe; change it immediately and never publish the live value in a screenshot, guide, stream, or chat message.
- Stop the server with
stop. - Open the server’s
server.cfgwhile the process is stopped. - Replace the default admin-password value with a long, unique password.
- Save the file and start the server again from NitroxLauncher.
- Use the server’s documented authentication flow, then run
op [name]from the console for each trusted operator. - Confirm access with a low-risk action, such as
listorsay, before granting additional staff access.
If an operator leaves the team, run deop [name] and change the admin password if you suspect it was shared. Do not distribute the configuration file casually because it contains authentication and permission settings.
Permission levels
DefaultPlayerPerm controls the permission assigned to newly joining players. The documented hierarchy is:
| Level | Capabilities | Recommended use |
|---|---|---|
NONE |
No world interaction. | Testing or deliberately restricted accounts. |
PLAYER |
Normal gameplay. | Default for ordinary players. |
MODERATOR |
Basic moderation, including kicking. | Trusted helpers who do not need bans or configuration access. |
ADMIN |
Full administrative permissions, including bans, operator management, and configuration control. | Server owners and a small number of senior administrators. |
CONSOLE |
Highest level, available through the server console. | Keep this restricted to the host process and owner. |
The 1.8.0.1 release notes say Nitrox demotes player permissions on disconnect to reduce admin spoofing. They also describe an option to disable automatic admin permissions for local players when proxies are involved. If a local player unexpectedly receives elevated access, inspect that option and the proxy arrangement before changing the entire permission hierarchy.
Configuration settings that affect play and recovery
Autosave interval
SAVE_INTERVAL controls autosave frequency. The documented default is 120000 milliseconds (two minutes). This is an interval setting, not a guarantee that every gameplay action is written instantly. Shorter intervals reduce the amount of progress lost after a crash but increase save activity; longer intervals reduce that activity while increasing rollback risk.
Disable autosave
SAVE_DISABLE can disable autosave. Use that only for a deliberate testing workflow with frequent manual save commands. Leaving autosave disabled on a normal cooperative world makes an unexpected crash much more damaging.
World name
SAVE_NAME controls the world directory name and defaults to world. A distinct name is useful when one installation hosts separate groups or test environments. Change it while the server is stopped, and verify that the new directory is the one you back up.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsEditing safely
- Run
save, thenstop, before editing configuration. - Copy the original
server.cfgbefore changing values. - Change one setting at a time and start the server to check for errors.
- Keep a written record of the previous value so you can revert quickly.
Saving, backing up, and restoring a Nitrox world
Manual saves and clean shutdowns
Run save before maintenance, then use stop for a clean shutdown. Closing the process through an operating-system kill command or power loss can leave the world in an inconsistent state even when autosave is enabled.
Rank #4
- Iconic Deep-Sea Gaming Design: Bring the thrill of the ocean depths into reality. Inspired by the mysterious creatures of Subnautica, this expertly crafted plush figure captures the unique features of the deep-sea leviathan, making it a must-have piece for every dedicated gamer and ocean explorer enthusiast.
- Premium Softness & Comfort: Crafted with high-quality, ultra-soft fabric and stuffed with high-density premium cotton filling. This huggable cushion offers an exceptionally smooth tactile experience, perfect for relaxing on the couch during intense gaming sessions or long office hours.
- Versatile Home & Office Decor: Beyond a gaming collectible, this striking deep-sea creature serves as an eye-catching decorative piece. Add a touch of sci-fi adventure to your living room sofa, bedroom bedding, gaming setup, desk space, or bookshelf display.
- Perfect Collectible Gift for Gamers: Looking for a unique surprise for a gaming fan? This authentic creature plush pillow makes an extraordinary gift for friends, family, adults, and gaming enthusiasts on birthdays, holidays, or any special celebratory occasion.
- Durable Craftsmanship & Easy Care: Features meticulous stitching and reinforced seams to ensure long-lasting durability for daily hugging and display. Designed for low maintenance, it is easy to spot clean with a damp cloth to keep its vibrant ocean colors looking fresh.
What to back up
- Save the world and stop the server.
- Use SFTP or the control panel’s file browser to download the complete save directory associated with
SAVE_NAME. - Download
server.cfgas well. It preserves the world name, save behavior, password and permission settings needed to recreate the instance. - Store the copy outside the server machine, and keep at least one dated version that you do not overwrite.
- Back up before changing Nitrox versions. Updates generally preserve saves, but the administration guidance recommends a backup in case a migration or rollback is needed.
Restoring after a failure
Nitrox 1.8’s launcher and server architecture include world-backup restoration. Stop the affected instance, preserve the current files for forensic comparison, and restore the dated save directory through the launcher or file-management workflow you use. Do not overwrite your only copy before confirming that the restored world loads.
If a save appears corrupt and no usable backup exists, create a fresh world by changing SAVE_NAME to a new value. This does not repair the old world, but it distinguishes a damaged save from a networking or installation problem and gives players a playable fallback.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchTroubleshoot players who cannot connect
- Confirm the version. Check the exact Nitrox release and Subnautica build on the server and every client. All must be on a supported, matching combination.
- Confirm the address. Use the public IP shown by the server window for direct hosting, or the VPN address for a VPN setup. Do not give players the host’s private LAN address unless they are on the same network.
- Confirm UDP 11000. Check the router forwarding rule, the host’s private address, and any upstream modem or second-router NAT.
- Check firewall rules. Allow
Subnautica.exeandNitroxServer-Subnautica.exe, and permit UDP 11000 on the active network profile. - Check passwords. A server password blocks entry even when the port is reachable. Re-enter it carefully and distinguish the player password from the separate admin password.
- Test the path. Have someone connect from outside the host’s LAN. Local testing can succeed even when the internet-facing port is closed.
- Try a VPN. If forwarding fails because of carrier-grade NAT or restrictive router policies, place all players on the same VPN and use the host’s VPN address.
Desynchronization, crashes, and save errors
Players see different world states
Have every player disconnect and reconnect, then verify the exact Nitrox version on each machine. Reconnection resolves transient state drift; a persistent mismatch usually indicates unsupported versions or one of Nitrox’s known synchronization gaps.
The server crashes after a Subnautica update
Check the official Nitrox release list for a build compatible with the newly installed Subnautica patch. Do not repeatedly launch an older Nitrox build against a newer game version while using your only production save. Restore the pre-update backup if the world was modified during an incompatible run.
The world will not load
Restore the most recent known-good save directory. If there is no backup, test a new SAVE_NAME. Preserve the failed directory before experimenting so a later compatible build can be tested against it.
Gameplay remains inconsistent
Review the known limitations below before changing router, permission, or save settings. A missing animation, unsynchronized fire, or sleeping problem can be a product limitation rather than a misconfigured server.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Known Nitrox 1.8 limitations
The 1.8 release notes identify several systems that are not fully synchronized. Plan cooperative sessions around these constraints:
- Story PDA content and terminals are not synchronized.
- Creatures other than leviathans are not fully synchronized.
- Oxygen tanks may appear empty after a relog.
- Cyclops health is not properly synchronized.
- Player animations are not fully synchronized.
- Exosuits are not fully synchronized.
- Scanner rooms are not synchronized.
- Fires are not synchronized.
- Sleep does not work.
These limitations can produce apparently contradictory screens or world states even when everyone is on the same version. Treat the server as an alpha multiplayer layer rather than a perfect reproduction of single-player Subnautica.
Self-hosting versus managed Nitrox hosting
The right choice depends on whether you value direct control or reduced network administration. Provider-specific prices, uptime and affiliate terms are not established here, so compare a real service against the following operational requirements rather than choosing on a headline price.
Quick Recap
| Decision area | Self-hosted server | Managed server |
|---|---|---|
| Networking | You handle UDP 11000 forwarding, firewall rules and, when necessary, a VPN. | The provider generally supplies an internet endpoint, reducing router work. |
| Console and files | Direct access to the Nitrox process, console and configuration files. | Access depends on the provider’s panel and file-transfer tools. |
| Backups and restore | You run save, stop the server and copy files through SFTP or a panel. |
Some services automate snapshots, but verify that they back up both the save directory and server.cfg. |
| Version control | You choose when to update Nitrox and Subnautica and can stage a backup first. | Confirm that the service supports Nitrox 1.8.x and lets you control update timing. |
| Operating-system support | You control the host operating system; Linux support is experimental in Nitrox 1.8.0.0. | Ask which operating system and Nitrox build the service actually runs. |
| Passwords and permissions | You set the admin password, DefaultPlayerPerm, operators and bans directly. |
Ensure the panel exposes equivalent password and permission controls rather than only a start/stop button. |
| Cost | Uses your existing computer, connection and electricity; any hardware or bandwidth cost is yours. | Requires a subscription or other provider charge; the amount depends on the service and is not stated here. |
Practical operating checklist
Before opening the server
- Confirm Subnautica and Nitrox versions match the supported 1.8 release.
- Set a unique server password and replace the default admin password.
- Check UDP 11000 forwarding or bring every player into the same VPN.
- Allow both executable files through the firewall.
- Set
SAVE_INTERVALdeliberately and confirmSAVE_NAME. - Make a dated backup of the save directory and
server.cfg.
During a session
- Use
sayfor maintenance notices. - Use
listbefore moderation actions. - Run
savebefore planned changes. - Grant
ADMINor operator access only to trusted people. - Remember that unsynchronized systems and alpha limitations can look like player-specific bugs.
Before maintenance or an update
- Announce the stop with
say. - Run
save. - Run
stopand wait for the process to exit. - Copy the save directory and
server.cfgto dated storage. - Update Nitrox and Subnautica together only when a compatible release is available.
- Start the server, check
help, and test a low-risk connection before inviting the full group.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
