Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →If Subnautica Nitrox says “Unable to connect to remote server”, check the server’s port first. The port printed by the Nitrox server console (for example, Listening on port 11000) must be the same port listed in your hosting panel’s Network tab. A mismatch prevents players from reaching the server even when the server process appears to be running.
Playing with friends? Godlike.Host runs hosted Subnautica (Nitrox) servers from 10 data-center locations, with free DDoS protection.
Then disable automatic port forwarding on hosted servers, make sure the server and every player use the same Nitrox release, and allow the game and server through firewalls. The procedure below follows that order so you can stop as soon as the connection works.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Subnautica (PS4) | $23.46 | Buy on Amazon |
| 2 |
|
Subnautica + Subnautica Below Zero Double Pack (Nintendo Switch) | $48.46 | Buy on Amazon |
| 3 |
|
Subnautica - Xbox One | $69.14 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Start with the port mismatch
Port configuration is the most frequently identified cause in hosting troubleshooting guidance. Nitrox reports its active port in the server console. Your host exposes a port in its control panel, normally under Network. Those values must match exactly, including a custom port chosen by the host.
| What you see | Likely cause | First action |
|---|---|---|
| The console is running, but every player receives the remote-server error | The console port and hosting-panel port differ | Compare both values, set ServerPort to the panel value, then restart |
| The server works locally but not for friends outside your network | UPnP or firewall/forwarding is blocking the UDP port | Set AutoPortForward to False, then configure the port and firewall manually |
| Only one player cannot join | That computer has a firewall rule, version mismatch or local network restriction | Check that player’s Nitrox version and firewall exceptions |
| Players connect, but loading hangs or crashes | Different Nitrox builds or an older game/Nitrox combination | Bring everyone to the same supported 1.8.x build |
1. Confirm that the Nitrox server is actually listening
- Start the Nitrox server and leave its console window open.
- Wait for the startup messages to finish. Look for a line such as
Listening on port 11000. - Record the port number exactly. Do not assume it is 11000 if the console displays a different value.
- If no listening message appears, stop troubleshooting the player connection: the server has not completed startup. Restart it and inspect the preceding error messages, or repair the server installation before trying to join again.
A server that is closed, stuck during startup or listening on a different port cannot accept a remote connection. Have the host administrator perform this check when the server is rented, because the console may be available only to the account running the service.
#1 Best Overall
- Descend into the depths of an alien underwater world filled with wonder and peril
- Craft equipment, pilot submarines and out-smart wildlife
- Explore lush coral reefs, volcanoes, cave systems, and more
- Underwater survival and exploration
2. Match the console port to the hosting panel
On a hosted server, open the provider’s control panel and navigate to its Network tab. Compare the displayed port with the number printed by Nitrox. If they differ, change the Nitrox configuration rather than guessing at another number.
- Stop the Nitrox server process.
- Open the server’s
server.cfgfile in the Nitrox installation or server data directory. - Find the
ServerPortsetting. - Replace its value with the port shown in the hosting panel’s Network tab. Keep the setting numeric and do not add quotation marks.
- Save the file and start the server again.
- Check the new console output. The listening-port line should now show the same number as the panel.
Use the port from the panel as the authority for a hosted instance. If the panel assigns 11000, the console must report 11000; if it assigns another port, use that port consistently in the configuration, firewall rule and client connection details. Changing only the panel or only the configuration leaves the mismatch unresolved.
3. Turn off automatic port forwarding on hosted servers
Nitrox can attempt UPnP port forwarding automatically. Hosting environments often do not permit that request, or the server may be behind networking equipment that does not answer it. In those cases the automatic attempt can fail and leave the server unreachable.
- Stop the server.
- Open
server.cfg. - Set
AutoPortForwardtoFalse(capitalization as shown). - Save the file and restart the server.
- Use the manually assigned port from the hosting panel and confirm it appears in the console.
This setting does not replace a firewall rule or a provider-side port allocation. It simply prevents Nitrox from relying on an unsuccessful UPnP request. On a privately hosted server, you may instead need to configure forwarding on your router; see the VPN option below if forwarding is impossible.
4. Put every participant on the same Nitrox version
The server and all players must run the identical Nitrox version. A client on one build can fail during discovery, authentication or world loading even when the network port is correct.
Which release should current players use?
The latest build identified in the project notes is Nitrox 1.8.1.0. The 1.8 line targets the post-2.0 version of the original Subnautica game. Older Nitrox releases are not supported for that current game build, so installing an old 1.7 or earlier package is not a workaround.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- 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
Synchronize the server and clients
- On the server machine, open the Nitrox launcher or installation details and record the full version number.
- Have every player check the same number in their launcher.
- Update or reinstall any machine that reports a different build. Do not mix 1.8.0.x and 1.8.1.0 unless the server administrator deliberately runs that exact build for everyone.
- Close Nitrox completely after updating, then relaunch the server first and the clients afterward.
Nitrox 1.8 supports the Epic Games and Steam editions of Subnautica. Project notes for 1.8.0.1 and 1.8.1.0 also add Microsoft Store support. Experimental Linux support is noted, while macOS support was described as planned for a later stage; treat those platform notes as availability qualifications, not a guarantee that every platform combination can connect.
5. Allow Nitrox and Subnautica through both firewalls
Port forwarding alone is not enough if the operating-system firewall drops the traffic. The host and each player should create allow rules for the game executable and the Nitrox server executable. The server’s network traffic uses UDP, with 11000 as the standard port cited in the troubleshooting guidance.
On the server computer
- Add an inbound and, where your firewall separates them, an outbound exception for
NitroxServer-Subnautica.exe. - Add an exception for
Subnautica.exe. - Allow the UDP port used by the server. Use UDP 11000 when the console and hosting panel both specify 11000; use the assigned custom port when they specify another value.
- Apply the rule to the network profile used by the server. A rule limited to a different profile will not help when the machine is classified as Private, Public or Domain.
On each player computer
- Add firewall exceptions for
Subnautica.exeand the Nitrox client components when prompted. - Permit Nitrox on the active network profile.
- Temporarily disable third-party security filtering only as a controlled test, then restore it and create a permanent allow rule if it proves to be the cause.
Do not open random TCP ports when diagnosing this specific error. Confirm the protocol and number from the server configuration, then create the narrowest UDP rule that covers that port.
6. If you host at home, check forwarding and the address players use
A self-hosted server normally needs the selected UDP port forwarded from the internet-facing router to the computer running Nitrox. The forwarding destination must be the host computer’s current local address. If that address changes, a previously correct rule can point to the wrong machine.
- Reserve a stable local address for the host computer in the router, if your router supports address reservations.
- Forward the Nitrox UDP port to that address.
- Confirm that the server console and the forwarding rule use the same port.
- Give remote players the public address and port expected by your Nitrox setup, not the host’s private address such as a 192.168.x.x address.
- Test from a network outside the host’s Wi-Fi. A local test can succeed even when the router does not support hairpin connections for inside-to-inside traffic.
Some internet providers place customers behind carrier-grade NAT. In that arrangement, the household router does not receive a directly reachable public address and ordinary forwarding cannot work. Contact the provider if you suspect that limitation, or use the VPN-style method described next.
7. Use a VPN-style virtual LAN when forwarding is impossible
The official Nitrox wiki notes that a VPN tool such as Hamachi can avoid conventional port forwarding. A virtual-LAN tool puts the host and players on the same software-defined network, so players connect through the virtual address rather than an exposed home-router port.
Rank #3
- Dive into a vast underwater world - sub Nautica's ocean range from shallow coral reefs to treacherous deep-sea trenches, lava fields, and bio-luminescent underwater rivers
- Scavenge, craft, and survive - after crash landing in your life pod, the clock is ticking to find water, food, and to develop equipment needed to explore as you collect resources from the ocean
- Construct underwater habitats - build Bases on the sea Floor, choosing layouts and components, and managing hull-integrity as depth and pressure Increase
- Unravel the mystery - signs abound that something is not right and you must Figure out what happened to this planet and what caused you to crash - can you find a way to make it Off the planet alive
- Disrupt the food Chain - lure and distract a threatening creature with a fresh fish, or simply swim as fast as you can to avoid gnashing jaws of roaming predators
- Install the same VPN-style tool on the host and every player.
- Create a virtual network and have each participant join it.
- Verify that every participant appears online in the virtual network.
- Start Nitrox on the host and note the server port shown in the console.
- Have players connect using the host’s virtual-network address and the matching Nitrox port.
- Keep the firewall exceptions for Nitrox executables; a virtual network does not automatically override local firewall policy.
Do not combine several competing forwarding methods while testing. First establish a clean virtual-network path, then add other networking changes only if a specific error remains.
8. Understand the 1.8.1.0 and Subnautica 2.0 notes
Nitrox documentation uses “Subnautica 2” in some release discussions to mean the 2.0 update of the original Subnautica. It does not establish support for the separate standalone sequel commonly called Subnautica 2. Nitrox support described here applies to the original game updated to the post-2.0 branch.
Release notes identify several 1.8.1.0 changes that can affect multiplayer behavior:
- A substantially improved join queue, intended to reduce waits and bugs when players crash during loading.
- Synchronization for picking up items with Exosuit claw arms.
- Synchronization for drillable mineral deposits.
- IPv6 connectivity support.
The project notes describe 1.8.1.0 as probably the last content update for the 1.8 line. That does not remove the need for matching versions: a server on 1.8.1.0 still requires clients on the same supported build.
9. A complete connection-failure checklist
Work through these checks in order, changing one thing at a time:
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 reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- Server process: confirm the Nitrox server is running and prints a listening-port line.
- Port comparison: compare that number with the hosting panel’s Network tab.
- Configuration: if they differ, set
ServerPortinserver.cfgto the panel value and restart. - UPnP: on a hosted server, set
AutoPortForwardtoFalseand restart. - Versions: put the server and every player on the same 1.8.x release, preferably the project’s 1.8.1.0 build when it matches the server’s supported game installation.
- Firewall: allow
Subnautica.exeandNitroxServer-Subnautica.exeon the host and clients, and allow the correct UDP port. - Home hosting: verify router forwarding, a stable host address and testing from outside the local network.
- Alternative path: if forwarding cannot work because of NAT or provider restrictions, create a VPN-style virtual LAN and connect through the host’s virtual address.
10. Common mistakes that make the error persist
- Editing the wrong port: changing a client shortcut or a remembered default does not change the server’s active
ServerPort. - Leaving UPnP enabled on a hosted instance: a failed automatic request can coexist with an otherwise correct manually assigned port.
- Mixing game branches: pre-1.8 Nitrox builds are not the correct choice for the current post-2.0 original game. Steam users may see a Legacy branch for older game builds, but the server and clients must still be deliberately matched.
- Opening only TCP: the cited server port is UDP. A TCP-only rule does not permit the required traffic.
- Allowing the server but not the game: both executable exceptions matter, and the player’s firewall can block a connection even when the host is configured correctly.
- Testing only from inside the host’s network: that can conceal a router, NAT or public-address problem.
- Assuming “Subnautica 2” means the sequel: the 2.0 wording in Nitrox notes concerns the original game’s update, not confirmed sequel compatibility.
When to escalate to the host or project issue tracker
Contact the hosting provider when the Network tab shows a port that the server cannot bind, the panel keeps changing the assigned port, or the service cannot expose the required UDP mapping. Include the console’s exact listening-port line and the value shown in the panel.
Report a Nitrox issue only after confirming the process starts, the ports match, all versions are identical and the firewall path is allowed. Include the Nitrox version, game edition (Steam, Epic or Microsoft Store), operating system, whether the server is hosted or home-run, the listening port, and the point at which the connection fails. Those details distinguish a configuration problem from a reproducible software defect.
Quick Recap
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.




