Nova-Life: Amboise Server Not Showing in the List? How to Fix It
Nova-Life servers start private. Set isPublicServer to true in server.json, then check serverPort, the game version and your JSON if it still hides.
Updated Oct 7, 2026 · 4 min read
On this page
A new Nova-Life: Amboise server does not appear in the server list because it is created private: its server.json contains "isPublicServer": false. Stop the server, open Servers/<your server name>/Config/server.json, change that line to "isPublicServer": true, save, and start the server again. If it still does not show after that, the cause is usually a mismatch between serverPort and the port that is actually open, a server that is behind the current game version, or a typo that makes server.json unreadable.
This catches nearly every new city owner, because nothing in the game tells you the server is private. It simply never shows up.

Fix 1: Turn on isPublicServer
The setting lives in the city's own folder, not in the main server folder:
Servers/
MaVille/
Config/
server.json
- Stop the server. Editing while it runs risks the change being ignored.
- Open
server.jsonand find"isPublicServer": false. - Change it to
"isPublicServer": true. - Save, then start the server.
If you have more than one folder under Servers, edit the one whose name matches the name the server is started with (-startServer "MaVille", or the Server Name on a hosted panel). Editing the config of a different city does nothing to the one that is running.
Fix 2: Check the JSON is valid
A single missing comma or quote makes server.json unreadable, and the server may fall back to defaults or fail to start. After editing:
- Every key and text value is in double quotes.
- Every line but the last inside
{ }ends in a comma. trueandfalsehave no quotes.
Paste the whole file into any JSON validator if you are unsure. A correct block looks like:
"serverListName": "Ma Ville RP",
"serverSlot": 32,
"serverPort": 7777,
"isPublicServer": true,
Fix 3: Make serverPort match the open port
The server listens on the port in serverPort, 7777 by default. Players and the list can only reach it on that port. Problems appear when:
- You changed
serverPortbut forwarded the old port on your router. - A host gave your server a different port, but the
server.jsonyou uploaded from home still says 7777. - Two cities on one machine both use 7777, so only one can start.
Set serverPort to the port that is really open for this server, and forward it on your router if you host at home. Our port forwarding guide covers that. If the forwarding is right and nobody outside can connect, check whether your provider uses carrier grade NAT with our CGNAT guide.
Fix 4: Update the server
Nova-Life is in Early Access and updates often. When Steam updates the game, players get the new client right away. A server still on the old build drops out of what they can see and join. Update the server files with SteamCMD (app ID 1665030):
./steamcmd.sh +force_install_dir ../nova-life_server +login anonymous +app_update 1665030 validate +quit
Then restart. Plugins may need updates of their own after a big patch, so if the server starts crashing right after updating, move plugins out of the Plugins folder and add them back one at a time.
Fix 5: Search for the right name
The list shows serverListName, not serverName. If you set a fancy list name, search for that. serverName is only the folder name and is never shown to players.
Fix 6: Players can see it but cannot get in
If the city is in the list but joins fail, check:
| What happens | Likely cause |
|---|---|
| Join times out | Port closed, or server still loading |
| Kicked right after joining | Version mismatch between client and server |
| Stuck at the whitelist form | isWhitelisted is on and staff have not approved them yet |
| Crash while loading | A plugin failing. Check the server log |
Players with a damaged install can also fail to load into any server. Verifying game files in Steam (right click the game, Properties, Installed Files, Verify integrity of game files) fixes that.

The quick checklist
| Check | Where |
|---|---|
"isPublicServer": true |
Servers/<name>/Config/server.json |
| Valid JSON | Same file |
serverPort equals the open port |
Same file, plus router |
| Server on the latest build | SteamCMD or auto update |
Searching for serverListName |
In game server list |
On a hosted server
On a GamezServers Nova-Life: Amboise server, the port is opened for you and written into server.json when the server is installed, so Fix 3 is already done, and auto update keeps it on the current build. The one step left is the same as everywhere: open Servers/<your server name>/Config/server.json in the file manager, set isPublicServer to true, and restart from the panel. If you want a full walkthrough of the files first, see our Nova-Life setup guide.
FAQ
Why is my Nova-Life server private?
Servers are created with "isPublicServer": false. That is the default, not an error. Change it to true to list the city.
Where is server.json for Nova-Life?
In Servers/<your server name>/Config/server.json, inside the dedicated server's folder.
Do I need to restart after changing isPublicServer?
Yes. Stop the server before editing and start it again after saving.
Does a whitelisted server still show in the list?
Yes, if it is public. Players see it and fill in your application form when they join.
How do I change the name shown in the list?
Edit serverListName in server.json and restart. Leave serverName alone, since it must match the city's folder.
Skip the setup. Your own Nova-Life: Amboise server.
Then $9.99/mo. Just trying it? $2.50 for 3 days