If you have spent any time in automation communities recently, you have probably seen n8n come up more than once. So what is n8n exactly? It is a workflow automation tool that lets you connect apps, build multi-step automations, and even set up n8n AI agent workflows without needing to be a developer to get meaningful results. The self-hosted version is what makes it genuinely interesting because you own the data, you control the environment, and there is no usage-based billing that quietly doubles your costs as your automations grow.<\/p>\n
Getting n8n on a VPS is where most people hit their first real decision point. Docker is the method that shows up in almost every tutorial, but it is not the only option and for some setups it is not even the best one. This guide walks you through all three installation methods, explains which one makes sense for which situation, and gets you to a working n8n instance with an optional domain and SSL setup at the end.<\/p>\n
Getting the prerequisites right before you start saves a frustrating hour of troubleshooting mid-install.<\/p>\n
Your server needs to be running Ubuntu 22.04 LTS with at least 2GB RAM. You can technically run n8n on 1GB but once you start building real workflows with multiple active automations or n8n AI agent tasks running in the background, that 1GB limitation shows up fast. 2GB is the comfortable starting point for anything beyond basic experimentation.<\/p>\n
Root or sudo access is non-negotiable. If your n8n hosting plan<\/a> restricts what you can install or configure at the system level, check what you actually have access to before going any further.<\/p>\n Docker needs to be installed if you are going that route. If it is not already on your server, this gets it there:<\/p>\n bash<\/em><\/p>\n curl -fsSL https:\/\/get.docker.com -o get-docker.sh<\/em> Node.js version 18 or higher<\/strong> is what you need for the npm method. Run node -v to check what you have. Anything below 18 needs an update before n8n will install cleanly.<\/p>\n A domain name<\/strong> is optional but genuinely worth having. Accessing n8n through a raw IP address and port number works for testing but gets annoying quickly and is not suitable for production webhook usage.<\/p>\n There are three ways to get n8n running on a VPS and each one trades something different. Here is the honest version of what each approach actually involves before you commit to one.<\/p>\n Docker wraps n8n and everything it depends on inside a container that runs independently of the rest of your server. The big practical benefit is that nothing on your server can break the n8n installation and nothing about the n8n installation can break the rest of your server. Updates are a single command. Moving to a new server means copying one config file. For people who are new to self-hosting or who just want n8n run without a lot of ongoing maintenance, this is the right starting point.<\/p>\n This one installs n8n directly on your server as a Node.js process. No container overhead, no Docker layer between you and the application. If you are already comfortable in a Node.js environment and prefer having direct access to the running process, this approach feels more natural. The trade-off is that you take on a bit more responsibility, specifically managing the Node.js version, handling process restarts, and making sure n8n keeps running after server reboots.<\/p>\n Docker Compose is the version of the Docker approach that scales. Instead of a single long command that you have to remember or keep in a notes file somewhere, your entire n8n configuration lives in a readable YAML file that you can version control and reproduce easily. More importantly, Docker Compose is the right path when you want to swap out the default SQLite database for PostgreSQL, which matters once n8n is handling real workflow volume on a daily basis.<\/p>\n For most people who are setting up n8n on a VPS for the first time, Docker is the right call. It is the fastest path to a working instance, the community support around it is extensive, and you are unlikely to run into environment-specific issues that take hours to diagnose.<\/p>\n If you already live in Node.js and the idea of adding Docker to a server that does not already use it feels like unnecessary overhead, the npm method is a perfectly reasonable alternative. The main thing you need to get right is process management so n8n does not disappear when you close your SSH session.<\/p>\n Docker Compose with PostgreSQL is worth the extra setup time if you are building something you will actually rely on. SQLite is fine for learning and light use, but for anything running continuously with multiple workflows executing throughout the day, PostgreSQL handles the load more gracefully and is simply more appropriate for a production setup.<\/p>\n This gets n8n running on your VPS through Docker as straightforwardly as possible.<\/p>\n bash<\/em><\/p>\n ssh your_username@your_server_ip<\/em><\/p>\n bash<\/em><\/p>\n docker –version<\/em><\/p>\n A version number means you are good to go. No version number means Docker is not installed yet.<\/p>\n bash<\/em><\/p>\n docker run -d \\<\/em> A few things in here are worth understanding. The –restart unless-stopped flag means n8n comes back automatically if the server reboots. The -v flag creates a local folder that stores your workflows, credentials, and settings outside the container, so none of that disappears if you ever need to recreate or update the container. The timezone is set to India which keeps your scheduled workflows firing at the right times.<\/p>\n bash<\/em><\/p>\n docker ps<\/em><\/p>\n n8n should appear in the list with a status of Up.<\/p>\n http:\/\/your_server_ip:5678<\/em><\/p>\n You will land on the n8n setup screen where you create your owner account and log in for the first time.<\/p>\n bash<\/em><\/p>\n npm install n8n -g<\/em><\/p>\n bash<\/em><\/p>\n npm install pm2 -g<\/em> That last command generates a startup script that brings n8n back online after a server reboot automatically. Follow whatever instructions it outputs for your specific system.<\/p>\n This step is optional if you are just testing things out. But if you are planning to use n8n regularly, connect it to external services, or use webhooks, do this before anything else.<\/p>\n Make sure your domain is pointing to your server’s IP address<\/strong> through an A record in your domain settings. You can do this from wherever you purchased your domain, i.e., your domain registrar. Once updated the changes might take a little time to start. It can take anywhere from a few minutes to a couple of hours to reflect.<\/p>\n bash<\/em><\/p>\n sudo apt install nginx certbot python3-certbot-nginx -y<\/em><\/p>\n bash<\/em><\/p>\n sudo certbot –nginx -d yourdomain.com<\/em><\/p>\n Certbot handles the Nginx configuration automatically and sets up auto-renewal so you never have to think about an expiring certificate.<\/p>\n Update n8n to know its public URL.<\/strong> Stop the existing container, remove it, and recreate it with the correct environment variables:<\/p>\n bash<\/em><\/p>\n docker stop n8n<\/em> docker run -d \\<\/em> After this, n8n is running at https:\/\/yourdomain.com and external services can send webhooks to it without issues.<\/p>\n n8n is not accessible in the browser after the Docker command ran<\/strong> bash<\/em><\/p>\n sudo ufw allow 5678<\/em><\/p>\n Pull the logs to see what actually went wrong:<\/p>\n bash<\/em><\/p>\n docker logs n8n<\/em><\/p>\n Nine times out of ten it is either a volume permission issue or not enough memory. Fix permissions with:<\/p>\n bash<\/em><\/p>\n sudo chown -R 1000:1000 ~\/.n8n<\/em><\/p>\n External webhooks need a publicly accessible URL with the WEBHOOK_URL environment variable correctly set in your container. If you set n8n up without a domain, webhooks from services like Stripe or GitHub have nowhere to send their requests. Either add a domain or use ngrok temporarily for testing.<\/p>\n This usually means the domain DNS had not fully propagated when you ran Certbot. If the changes have not reflected yet, give it some time to update. Once everything reflects, try to run the certbot command again. You can check propagation at whatsmydns.net.<\/p>\n PM2 is not configured correctly. Run pm2 startup and follow the exact output instructions for your system. Then run pm2 save to persist the process list.<\/p>\n Running n8n locally on a laptop is fine for building and testing workflows. But the moment you want those workflows to actually do something useful, a VPS changes everything.<\/p>\n Scheduled workflows keep running at 3am even when your laptop is off. When external services like Stripe, GitHub, or any other API need to send data to your n8n AI agent, they need somewhere reliable to send it. A VPS gives you a stable public address that is always reachable, which is something a home internet connection simply cannot promise.<\/p>\n And because the server runs continuously without sleep modes, unexpected reboots, or the kind of internet drops that happen at home, your multi-step automations keep processing data in the background exactly as they should, even when you are nowhere near a computer.<\/p>\n A VPS with 2GB RAM, NVMe SSD storage, and a clean Ubuntu install handles n8n comfortably for most individual and small business workloads. That combination of always-on availability and the flexibility of n8n is genuinely what makes it useful in practice rather than just impressive in theory.<\/p>\n host.co.in’s VPS hosting plans<\/a> are built on AMD EPYC Gen 4 hardware with NVMe SSD storage and full root access. Plans start from Rs 299 per month with Indian data centres and 99.95 percent uptime, which means your n8n instance and all the automations running on it stay up consistently.<\/p>\n There is no single correct way to install n8n on a VPS. Docker is the right starting point for most people because it is fast, clean, and low-maintenance going forward. npm installation suits developers who prefer direct control without a container layer. Docker Compose with PostgreSQL is what you graduate to when n8n stops being an experiment and starts being something your work depends on.<\/p>\n Pick the method that matches your current comfort level and server setup. You can always move to a more production-ready setup later without losing your workflows. If you are looking for a reliable hosting company India<\/a> users can choose for VPS infrastructure, explore host.co.in’s VPS hosting plans and get your n8n instance running on infrastructure built for continuous availability.<\/p>\n","protected":false},"excerpt":{"rendered":" If you have spent any time in automation communities recently, you have probably seen n8n come up more than once. So what is n8n exactly? It is a workflow automation tool that lets you connect apps, build multi-step automations, and even set up n8n AI agent workflows without needing to be a developer to get […]<\/p>\n","protected":false},"author":33,"featured_media":7790,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-7784","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-hosting"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
\nsudo sh get-docker.sh<\/em><\/p>\nDifferent Ways to Install n8n on a VPS<\/h2>\n
Install n8n Using Docker<\/h3>\n
Install n8n Using Node.js and npm<\/h3>\n
Docker Compose Setup<\/h3>\n
Which n8n Installation Method Should You Choose?<\/h2>\n
Step-by-Step: Installing n8n on VPS Using Docker<\/h2>\n
Connect to your server first:<\/h3>\n
Confirm Docker is installed and working:<\/h3>\n
Run this command to start n8n:<\/h3>\n
\n–name n8n \\<\/em>
\n–restart unless-stopped \\<\/em>
\n-p 5678:5678 \\<\/em>
\n-v ~\/.n8n:\/home\/node\/.n8n \\<\/em>
\n-e GENERIC_TIMEZONE=”Asia\/Kolkata” \\<\/em>
\ndocker.n8n.io\/n8nio\/n8n<\/em><\/p>\nCheck that the container is actually running:<\/h3>\n
Open a browser and go to:<\/h3>\n
If you are going the npm route instead, here is the short version:<\/h3>\n
Then install PM2 to keep it running:<\/h3>\n
\npm2 start n8n<\/em>
\npm2 save<\/em>
\npm2 startup<\/em><\/p>\nOptional but Highly Recommended: Add Domain and SSL<\/h2>\n
Install Nginx and Certbot:<\/h3>\n
Get your free SSL certificate:<\/h3>\n
\ndocker rm n8n<\/em><\/p>\n
\n–name n8n \\<\/em>
\n–restart unless-stopped \\<\/em>
\n-p 5678:5678 \\<\/em>
\n-v ~\/.n8n:\/home\/node\/.n8n \\<\/em>
\n-e GENERIC_TIMEZONE=”Asia\/Kolkata” \\<\/em>
\n-e N8N_HOST=”yourdomain.com” \\<\/em>
\n-e N8N_PROTOCOL=”https” \\<\/em>
\n-e WEBHOOK_URL=”https:\/\/yourdomain.com\/” \\<\/em>
\ndocker.n8n.io\/n8nio\/n8n<\/em><\/p>\nCommon n8n VPS Installation Issues<\/h2>\n
\nThe most likely cause is a firewall blocking port 5678. Open it with:<\/p>\nThe container starts and immediately stops<\/h3>\n
Webhooks from external services are not arriving<\/h3>\n
SSL errors immediately after setup<\/h3>\n
n8n disappears after closing the terminal on an npm install<\/h3>\n
Why VPS Hosting Works Better for n8n<\/h2>\n
FAQs<\/h2>\n
\n
\nYes. If you self-host n8n on your own VPS, you can use it for free. Your only regular cost is paying for the server infrastructure that you use, that means, your hosting.<\/li>\n
\nYes, you can run n8n on your own computer without any problem. But if you want to keep running your workflows smoothly even when your computer is turned off and avoid depending on your personal computer, a VPS usually gives you more benefits.<\/li>\n
\nIn most of the cases, 2GB RAM is enough for daily workflows. But if you expect your n8n setup to handle lots of workflows at a time, then going with 4GB RAM or higher will
\ngive you extra room.<\/li>\n<\/ol>\nConclusion<\/h2>\n