n8n VPS
Run n8n reliably on a VPS.
n8n VPS
Order: https://prevps.com/n8n-vps/
Related guide
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.
If you expose n8n to the public internet, protect it. Use HTTPS and strong auth.
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).
Actions like Rebuild and Restore can erase data. Always create a backup or snapshot first.
Quickstart
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.
The password shown in the portal is the initial password. Change it right after your first login.
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.
Powering off can corrupt data during disk writes. Shut down from the OS first when possible.
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:
22HTTP:
80HTTPS:
443
Don’t block SSH before you have console access. You can lock yourself out.
ISO Images
ISO lets you boot from an image. Use it when you need a custom OS install.
Typical workflow:
Mount the ISO.
Reboot the server.
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.
Backups and snapshots are different. Snapshots are best right before risky changes.
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:
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.
PTR should point to a hostname you control. That hostname should resolve back to the same IP.
If you can’t access the server
Try in this order:
Check the status is Running.
Reboot using Quick Actions.
Use Console to check SSH and firewall rules.
Confirm your firewall allows SSH (port
22).
See also:
Recommended next reads
Knowledge Base: https://prevps.com/clients/index.php?rp=/knowledgebase
Announcements: https://prevps.com/clients/index.php?rp=/announcements
Last updated