Nodes
The node is offline
A node reports its status to Nodex regularly. When Nodex stops receiving these reports, it marks the node and its servers as Offline. By default, this happens after 15 minutes without a report. To bring the node back online:- Check that the machine is running and reachable from the internet
- Check that your firewall or security group allows inbound traffic on port 3400 and outbound HTTPS and DNS traffic
- Reload the node overview page
The node says Requires Installation
A node created with Using a custom VPS waits for you to run its install command. Open the node’s Installation tab, copy the command, and run it as root on your server. See Create a node using a custom VPS.The node says Provisioning Failed
Nodex could not finish setting up a node created through a cloud provider. Delete the node with the Delete provider instance option to stop billing for the instance, then create a new node. See Delete an existing node.The page says the server could not be reached
Pages that read data from the node, such as the file browser and backups, show “We could not reach your server to fetch the data” when the node does not respond. Bring the node back online as described above, then reload the page.Servers
The installation failed
A server that fails to install shows Install Failed on its overview page. Click Retry to run the installation again. If it keeps failing, open the server’s Settings tab and use Reinstall the server.The server does not start
If a server stays in the Starting state or returns to Offline, open its console on the overview page and read the last messages. Then check the following:- The Startup Command and variables in the startup settings
- The ports in the network settings
- The node’s free disk space and memory on the node overview page

