# n8n VPS

## n8n VPS

**Order:** <https://prevps.com/n8n-vps/>

### Related guide

* [Access and set up your n8n VPS](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/BoDPxozpgQ40q0BzU95a)

### What this is for

Use this plan to host **n8n** automations on your own server.

### Typical setup (high level)

* Install n8n (commonly via Docker).
* Put it behind a reverse proxy (Nginx / Caddy) with HTTPS.
* Persist data to disk.

{% hint style="warning" %}
If you expose n8n to the public internet, protect it. Use HTTPS and strong auth.
{% endhint %}

### Key features in the Client Area

You’ll typically see these sections:

* **Server Information**: hostname, status, specs, location, IPv4/IPv6, initial user/pass.
* **Quick Actions**: reboot, power off.
* **Console**: use the console when SSH fails.
* **Firewalls**: allow/deny inbound rules by port.
* **ISO Images**: mount an ISO to install a custom OS.
* **Rebuild**: reinstall the OS.
* **Rescue Mode**: boot into a rescue environment.
* **Backups**: manage backups (if your plan includes them).
* **Snapshots**: create manual point-in-time snapshots.
* **View Server Metrics**: CPU/RAM/disk/network usage charts.
* **Primary IP Address**: IP info, blocked status, reverse DNS (PTR).

{% hint style="warning" %}
Actions like **Rebuild** and **Restore** can erase data. Always create a backup or snapshot first.
{% endhint %}

### Quickstart

{% stepper %}
{% step %}

### 1) Get access details

1. Check your provisioning email.
2. Open the Client Area.
3. Open your **n8n VPS** service.

Keep these details:

* IPv4 (or hostname)
* Username (usually `root`)
* Initial password

Client Area: <https://prevps.com/clients/clientarea.php>
{% endstep %}

{% step %}

### 2) SSH into the server

{% tabs %}
{% tab title="macOS / Linux" %}

```bash
ssh root@YOUR_SERVER_IP
```

{% endtab %}

{% tab title="Windows" %}
Use Windows Terminal (OpenSSH) or PuTTY. Host: `YOUR_SERVER_IP`. User: `root`.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### 3) Minimum day-one setup

* Change the default password.
* Update OS packages.
* Add an SSH key.
* Disable password login if possible.
* Enable a firewall and open only required ports.
  {% endstep %}
  {% endstepper %}

### Manage your VPS (Server Management)

#### Server Information

Use this to quickly copy your server details:

* **Hostname**: server name.
* **Status**: Running / Stopped.
* **Server type**: vCPU, RAM, SSD.
* **Location**: datacenter location.
* **IPv4 / IPv6**: access addresses.
* **Username / Password**: initial login details.

{% hint style="info" %}
The password shown in the portal is the initial password. Change it right after your first login.
{% endhint %}

#### Quick Actions: Reboot / Power Off

* **Reboot Server**: restart the server.
* **Power Off**: power off the server.

Use this if the server is stuck. It’s also common after a kernel update.

{% hint style="warning" %}
Powering off can corrupt data during disk writes. Shut down from the OS first when possible.
{% endhint %}

#### Console

Console is useful when:

* SSH is blocked by a firewall rule.
* Networking is broken.
* You misconfigured the SSH daemon.

Open the console, then fix the issue from inside the server.

#### Firewalls

Use this to control inbound traffic. Start with an allowlist of ports you need.

Common ports:

* SSH: `22`
* HTTP: `80`
* HTTPS: `443`

{% hint style="danger" %}
Don’t block SSH before you have console access. You can lock yourself out.
{% endhint %}

#### ISO Images

ISO lets you boot from an image. Use it when you need a custom OS install.

Typical workflow:

1. Mount the ISO.
2. Reboot the server.
3. Open Console and run the installer.

#### Rebuild (reinstall OS)

Rebuild reinstalls the operating system from scratch. This usually wipes disk data.

Use Rebuild when:

* The OS is badly broken.
* You want to switch distros.
* You want a clean slate.

#### Rescue Mode

Rescue mode boots into a recovery environment. Use it to recover data or fix boot issues.

Common cases:

* Wrong network configuration.
* GRUB issues.
* Full disk.

#### Backups

If your plan includes backups, you can:

* Enable a backup schedule.
* View the backup list.
* Restore when needed.

{% hint style="info" %}
Backups and snapshots are different. Snapshots are best right before risky changes.
{% endhint %}

#### Snapshots

Snapshots are point-in-time images of your VPS. Create one before:

* Major updates.
* App upgrades.
* Firewall or network changes.

#### View Server Metrics

Metrics help you decide whether you need an upgrade. Track:

* CPU usage
* RAM usage
* Disk usage / IOPS (if available)
* Network traffic

Related:

* [Upgrades and downgrades](/billing-+-client-area/upgrades-and-downgrades.md)

### Primary IP Address + Reverse DNS (PTR)

In the IP section, you’ll see:

* IP address
* Blocked status
* Reverse DNS (PTR)
* **Edit** and **Reset** buttons

PTR is often required for mail servers. It can also improve IP trust with some services.

{% hint style="warning" %}
PTR should point to a hostname you control. That hostname should resolve back to the same IP.
{% endhint %}

### If you can’t access the server

Try in this order:

1. Check the status is **Running**.
2. Reboot using Quick Actions.
3. Use **Console** to check SSH and firewall rules.
4. Confirm your firewall allows SSH (port `22`).

See also:

* [Troubleshooting checklist](/support/troubleshooting-checklist.md)

### Recommended next reads

* Knowledge Base: <https://prevps.com/clients/index.php?rp=/knowledgebase>
* Announcements: <https://prevps.com/clients/index.php?rp=/announcements>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.prevps.com/products/n8n-vps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.