NodeWorld
ENFR

Common problems

The server says what goes wrong in its log: in its terminal, with journalctl -u nodeworld-server -f for the Linux service, or in the Logs folder next to NodeWorld.Server.exe for the Windows service (see Run as a service). Find the line you see below. Still stuck? Ask on the NodeWorld Discord with the lines of the log.

The server does not start

Log lineWhat to do
SETUP REQUIRED: could not load '…/server-config.yaml'. with Failed to read config file or Failed to parse config fileThe file cannot be read, or is not valid YAML. Fix the line the message names, or delete the file: the server creates a new one and runs its setup assistant.
SETUP REQUIRED: and a setting, such as TickRate must be between 1 and 240., At least one world must be configured., Duplicate world id 'Tavern' in server config.Fix that setting in server-config.yaml (configuration), then start the server again.
SETUP REQUIRED: the Server ID and the Server token are missing. Give them with --server-id and --server-token, or in the config file.The server started without a console (a service, a script) and its file has no ID or token. Run it once in a terminal, or give them as options.
SETUP REQUIRED: central server registration failed. then Check CentralApiBaseUrl, ServerId and ServerToken in server-config.yaml, then restart.NodeWorld refused the ID and the token. Copy them again from My servers; if the token was rotated, put the new one in ServerToken (see Your server on the website).
Could not open the game port. (exit code 3)Another program uses the port: often a second NodeWorld server. Stop it, or change GamePort.
FL# runtime unavailable (nodeworld_fluxsharp next to the server)The FL# runtime file next to the server is missing: the worlds' scripts do not run. Extract the whole package of your system again.

A service that stops with exit code 2 is not started again by systemd: fix the configuration, then sudo systemctl restart nodeworld-server.

Players cannot reach the server

In the game, the loading screen says This server isn’t available., or loads forever. In Explore, the server shows offline.

  1. Run the setup assistant again (--setup): its port test says whether NodeWorld reaches the port in UDP and in TCP. When it does not, it says Players cannot reach this server yet. Check, in this order: and lists what to check.
  2. WARNING: your router's internet address is … which is not public (CGNAT): nobody outside can reach a server on this connection. See When your provider shares your address.
  3. UPnP: and a reason: your router did not open the port. Forward it yourself (On your router).
  4. Server heartbeat failed: and a reason: the server cannot reach NodeWorld (its internet connection, or NodeWorld down). It tries again every 30 seconds; NodeWorld shows a server offline when its last heartbeat is older than 2 minutes.
  5. When the server starts, Public Endpoint: shows the address and the port players get. They must be your public address (or domain name) and the port your router forwards.

Refused connection from …: wrong protocol version.: that player's game and your server do not run the same version. When the game's new version is out before your server's update, the server is Server not up to date in Explore until it updates (Updates).

A world does not work

Log lineWhat to do
World '…' is not served: and the reasonThe world failed its check at start: see Each world is checked. Refused worlds on your server's page says the same.
World '…' has reached its instance cap (…).The world runs as many instances as its MaxInstances allows (configuration).
World '…' has FL# scripts but no scene for the server (server/scene.json): publish the world again with a PC platform.Ask the world's creator to publish it again with a PC platform checked.
FL# scripts of world '…' (room …) not started, its package is refused: and the reasonA file of the world does not match its manifest: copy the creator's folder again, whole. The world runs without its scripts.
TCP file server at max concurrency. Rejecting connection.More than 16 world files are being sent at the same time. A player refused sees The world didn’t finish loading. and chooses Retry.

An update does not install

Log lineWhat it means
Server … is out (this one is …). AutoUpdate is offAutoUpdate: false: update by hand, or set AutoUpdate: true (Updates).
Server … is out; no package is published for this system.Wait for the package of your system, or update by hand when it is out.
Server … not installed: and the reason (size, SHA-256, signature)The download did not match what NodeWorld published: nothing was installed. The server tries again at the next check, an hour later.
Server … could not be installed; starting this version again.The files could not be replaced; the error follows in the log. The server goes on with its version.
The new version is installed; start the server again.The new version is in place but did not start by itself: start the server.
Update check failed: and a reasonNodeWorld could not be reached for the check: the server tries again an hour later.