How To Host n8n On A VPS

Before You Order

Have a verified HostVon account, a domain or subdomain you can configure, and access to the services your workflows will use. You should be comfortable administering a Linux server. One-click installation supplies the application image; it does not complete your domain, HTTPS, or workflow setup.

• List the workflows, expected simultaneous executions, and file sizes you plan to process.
• Decide where you will store encrypted backups outside the server.
• Check whether your required n8n features need a separate software licence.

Choose A Compatible n8n Plan

Open the n8n hosting page and compare the available CPU, RAM, storage, and prices. HostVon checks plans against the application image’s installation requirements. These checks establish compatibility, rather than a guaranteed number of workflows or executions.

Allow headroom for overlapping workflows, large payloads, execution history, and the database. Start with a representative workload and measure its resource use before moving business-critical automation onto the server. Review the selected region, billing term, and full total at checkout.

Order And Complete First-Login Setup

Select a plan from the n8n hosting page. In the server configurator, confirm that n8n is the selected application before paying. Follow the order in your HostVon console and wait for provisioning to finish.

Open the server details for its IP address and server access information. Connect using the supplied access method and follow the installed image’s first-login instructions. Create your n8n owner account before exposing the application to other users. Do not run a second installer over a preinstalled instance or assume that its database and service names match a generic Docker tutorial.

If you ordered a plain VPS instead, follow n8n’s official installation documentation linked below. Choose one installation method and configure persistent storage before importing data.

Configure Your Domain, HTTPS, And Webhooks

Point your chosen hostname to the server and configure a reverse proxy with a valid TLS certificate using the installed image’s instructions. Keep the database and internal application port restricted; the public entry point should be the HTTPS proxy.

For a reverse-proxy deployment on n8n 2.35.0 or later, set N8N_WEBHOOK_URL to your public HTTPS base URL; earlier versions use WEBHOOK_URL. Configure N8N_PROXY_HOPS for the actual trusted proxy chain and confirm the forwarded headers described in n8n’s documentation. Restart the application using its installation method, then check that generated webhook URLs use your intended hostname.

Add credentials through n8n’s interface and update external OAuth callbacks where needed. Test both a manual execution and an activated workflow triggered from an external service. A running server alone does not establish that webhooks or credentials work.

N8N_WEBHOOK_URL=https://n8n.example.com/
N8N_PROXY_HOPS=1

Back Up Before Importing Or Migrating Workflows

Keep a consistent backup of the actual database, n8n encryption key, configuration, and any required binary files. For Docker installations, preserve the persistent .n8n directory as well as any separate database storage. Workflow JSON exports are useful, but do not replace a full recovery plan.

For a migration, check version compatibility, copy data securely, and test credentials and webhook callbacks on the new instance. Avoid letting both old and new installations execute the same scheduled jobs. Keep the old server recoverable until the new deployment passes your checks.

Verify Your Deployment And Keep It Working

Run a small workflow that exercises the integrations you actually need. Check its output, execution history, memory usage, and the public webhook response. Test a restore into an isolated environment before trusting the backup.

If the editor works but webhooks fail, check DNS, TLS, the public webhook URL, proxy settings, and whether the workflow is active. If executions fail under load, inspect memory use and payload sizes before changing resources. Use server and application logs for diagnosis without sharing credentials or workflow secrets.

Schedule software updates and backup checks. HostVon provides server controls and billing; you maintain n8n and its operating environment. External service charges and your maintenance time belong in the total cost of self-hosting.