> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nodexpanel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Fix common problems with nodes, servers, backups, and billing.

## 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:

1. Check that the machine is running and reachable from the internet
2. Check that your firewall or security group allows inbound traffic on port 3400 and outbound HTTPS and DNS traffic
3. Reload the [node overview](/node-overview) page

If you connected your own server, also review the [custom VPS requirements](/custom-vps).

### 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](/nodes#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](/nodes#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](/file-browser) and [backups](/server-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](/server-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](/server-overview) page and read the last messages. Then check the following:

* The **Startup Command** and variables in the [startup settings](/startup)
* The ports in the [network settings](/server-network)
* The node's free disk space and memory on the [node overview](/node-overview) page

If the server is stuck stopping, click **Force Stop** to terminate the process.

### Players cannot join

Check that the server is in the **Running** state. Players join using the node's IP address and the server's primary port, which are shown in the **Address** on the [overview](/server-overview) page.

If the server is running and players still cannot connect, make sure the node's firewall or security group allows inbound traffic on the server's ports.

### A port is rejected

Ports must be between 1024 and 65535. Two allocations of the same server cannot share a port, and a port that is in use by another server on the same node is rejected. Choose a different port in the [network settings](/server-network).

### The server creation page asks to upgrade

Your plan's server limit is reached. Delete a server you no longer need, or upgrade your plan. See [Billing](/billing).

## Files and backups

### An upload fails

The upload dialog shows the maximum file size. Files above it are rejected.

### The backups page asks for a client update

Backups require version 0.2.0 or later of the Nodex client on your node. The page shows the current and the minimum version of your node's client. To update it, contact [support](/support).

## Billing

### Updating the payment method is unavailable

When Nodex cannot open Paddle's payment page, it shows "Updating your payment method is not available right now." Try again later, or contact [support](/support).

### A payment failed

Nodex shows a banner when a payment fails. Update your payment method in [Billing](/billing#payment-method) to avoid an interruption.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.