To self-host n8n on Hostinger, you pick a VPS plan, choose the “Ubuntu 24.04 with n8n” template during setup, and Hostinger installs n8n inside Docker for you. There’s no command line for the install itself. What’s left after is the part I had to work out myself: a domain, HTTPS, and knowing when to update. I did those with an AI walking me through each step.
This post contains affiliate links. If you sign up through one, I earn a commission at no extra cost to you.
The month I stopped counting runs
I wasn’t watching my n8n bill. I was watching the execution counter.
Every time I built something new, I’d do this quick math in my head about whether it was allowed to run every 15 minutes or whether it had to be hourly. Not because hourly was better for the job. Because I was rationing runs. I had workflows I wanted on a schedule and I kept putting them on a slower schedule to stay under a number.
That’s a weird way to build. The whole point of an automation is you set it and stop thinking about it, and I was thinking about all of them, all the time.
So I moved to my own server. I run 193 workflows on it now, and 117 of them are active on schedules right now. I don’t know how many times they fired this week and I don’t need to.
What does self-hosting n8n on Hostinger get you?
You get an n8n instance running on a machine you rent, with no cap on how many times your workflows run. You own the box, the data, and the updates. Hostinger owns the hardware and the network.
The trade is real and it goes both directions. Here’s the honest split of who’s responsible for what:
| n8n Cloud | Self-hosted on a VPS | |
|---|---|---|
| Execution limits | Counted against your plan | None |
| Updates | Done for you | Yours to run |
| Security patching | Done for you | Yours to run |
| Your workflow data | On their servers | On your server |
| Backups | Included | Snapshots from Hostinger, plus whatever you set up |
| Someone to call when it breaks | n8n support | You, and your AI |
If you want the actual money comparison for your own numbers, I built a calculator for exactly that. Run yours before you buy anything, because the answer changes a lot depending on how often your workflows fire.
Who is self-hosting n8n on Hostinger for?
It’s for you if you’re bumping into execution limits, or you’re changing a schedule to avoid them. That was my signal and it’s the cleanest one. If you’ve ever set a workflow to hourly when you wanted it every 15 minutes, you already know.
It’s also a fit if you want your workflow data sitting somewhere you control, or you’ve got enough automations running that a plan change on someone else’s roadmap would be a genuine problem for you.
Here’s who should skip it.
- You’re running two or three workflows. You’re nowhere near a limit. A server is a chore you don’t need yet, and Cloud is doing its job.
- You’re handling other people’s sensitive data. Client records, health information, anything with payment details in it. Self-hosting means the security is yours. That’s a bigger commitment than a template click, and I’d rather say so than have you find out later.
- You want zero maintenance forever. This is low maintenance, not no maintenance. If updates and backups are going to sit undone for a year, Cloud is the safer home for your automations.
What do you need to self-host n8n on Hostinger?
Four things, and two of them you might have already.
- A Hostinger VPS plan. I’m on the plan I run n8n on. Their KVM 1 is 1 vCPU and 4GB of RAM, KVM 2 is 2 vCPU and 8GB, and it goes up from there. Paid.
- A domain or subdomain. Mine’s a subdomain of a domain I already owned. You need one so you’re not typing an IP address into your browser forever. Paid, unless you already have a domain sitting around.
- Somewhere to manage DNS. Wherever your domain lives. I use Cloudflare, and it’s free at the level I need.
- An AI you can paste error messages into. ChatGPT, Claude, whichever. This is the one people leave off the list and it’s the one I used most.
When I did this, I used ChatGPT. I build everything with Claude Code now, but this was a while ago and I wasn’t using it yet. Either one does this job fine.
How does the Hostinger one-click n8n install work?
You pick the plan, and during the VPS setup Hostinger asks what you want on the machine. You choose the n8n template instead of a bare operating system. It installs Ubuntu 24.04 with n8n already running inside Docker. You never touch a terminal for the install.
Hostinger has a few n8n templates now, including one with queue mode for heavier use. The standard one is what you want unless you already know why you’d need the other.
Then it hands you a running server and a URL made of numbers, and this is the moment where a lot of people stall out. The template does the install. It doesn’t do the rest of it. What’s left:
- Point your domain at the server. Add an A record at your DNS provider pointing your subdomain at the VPS IP address. Mine’s
n8non a domain I own. - Get HTTPS working. You want a real certificate so the browser stops complaining and so webhooks from other services will talk to you. Mine’s a Let’s Encrypt certificate renewing on the box.
- Tell n8n its own address. n8n builds webhook URLs out of a setting, and if it still thinks it lives at an IP address, every webhook URL it hands you will be wrong.
- Log in and set your password. First load asks you to create the owner account. Do it immediately, before you walk away from a server sitting open on the internet.
That’s the whole shape of it. Steps 1 through 3 are where I pasted things into ChatGPT and did what it said, and I’ve put those prompts below so you don’t have to invent them.
Get the prompts
This is the artifact for this post. It’s a prompt sequence, not a skill file, because setting up a server is a thing you do once rather than a rule you want an AI to follow forever.
Paste these one at a time, in order, into whichever AI you’re using. Wait for each one to finish before you move on. The two things you have to change are your domain and your VPS IP address, both marked below.
The setup prompts
PROMPT 1: Point the domain
I have a Hostinger VPS running n8n from their one-click Ubuntu 24.04 template.
I want to reach it at: n8n.MYDOMAIN.com <-- change this
The server's IP address is: 000.000.000.000 <-- change this
My DNS is managed at: Cloudflare <-- change if different
Walk me through adding the DNS record, one step at a time. Ask me to confirm
each step worked before you give me the next one. Tell me what I should see
in my browser when it's pointing correctly, and how long to wait before
deciding something is wrong.
PROMPT 2: Get HTTPS working
The domain now points at the server. I need a real HTTPS certificate so the
browser trusts it and so other services can send webhooks to it.
Tell me first how to check what's already installed in front of n8n on the
Hostinger template, because I don't want to install a second web server on
top of one that's already there. Then give me the certificate steps for
whatever is actually running. One step at a time, and tell me what a
successful result looks like at each step.
PROMPT 3: Tell n8n its own address
n8n is generating webhook URLs with the IP address in them instead of my
domain. Show me which setting controls that on a Docker install from
Hostinger's n8n template, how to change it, and how to restart n8n so the
change takes. Then tell me how to verify it worked by looking at a webhook
URL inside n8n.
PROMPT 4: When something is broken
Here is exactly what I did, and here is the error I got:
[paste the command you ran and the full error text]
Explain what this error means in plain language before you give me a fix.
If the fix has any risk of taking my n8n instance offline, say so first and
tell me how to undo it.
PROMPT 5: Check my work
n8n is installed and I think I'm finished. Walk me through verifying it, one
check at a time, and tell me exactly what a passing result looks like:
1. my domain loads n8n over HTTPS with no browser warning
2. the certificate is valid and set to renew on its own
3. a webhook URL inside n8n uses my domain and not the IP address
4. n8n comes back up on its own after I reboot the server
Give me the check first, then what to do if it fails.Prompt 4 is the one I used most. Pasting the whole error instead of describing it is the difference between a useful answer and a guess.
If you get stuck
I can’t debug your server for you, and I’d rather say so than leave you guessing. Anything about the VPS itself goes to Hostinger’s support first, because the machine and the template are theirs and they answer around the clock. Anything about how n8n behaves goes to the n8n community forum, where people running these every day answer each other. Between those two and prompt 4, I haven’t been stuck on this for long.
What this setup doesn’t do
Some of this is on purpose and some of it is stuff I found out later.
Your server has one IP address, and some sites block it. This one surprised me. Reddit returns a 403 to my VPS on requests that work fine from my laptop. Datacenter IP addresses get filtered by anti-scraping rules, and your automations are coming from a datacenter now. If a workflow needs to read a site with defenses like that, you’ll need to authenticate properly through their API or route the request somewhere else. Nothing about the Hostinger template causes this, and no setup guide warned me about it either.
Backups need a decision from you. Hostinger includes backups and snapshots on their VPS plans, and that covers the machine. What lives on the box is your execution history and your saved credentials, and a snapshot is the thing standing between you and re-entering all of them. I also back up my workflow files separately, because a workflow file and a credential are two different problems.
The security is yours now. Not in a scary way, in a factual way. Nobody is patching this machine unless you do.
Updating is not as bad as I made it out to be. I built it up in my head for a while. My brain decided updating a server was going to be the thing that broke everything, and then I did it and it wasn’t. If you’re avoiding self-hosting because of the update step, I’d tell you the dread is bigger than the task.
The thing I’ll actually own up to is this: I don’t know what I don’t know about servers, and that sits with me a little. I run 193 workflows on a machine I understand at the “I can ask an AI about it” level, not the “I could rebuild it from scratch” level. It’s been fine. It might not always be. I’d rather tell you that than pretend I’ve got it fully handled.
Frequently asked questions
How much does it cost to self-host n8n on Hostinger?
It depends on which VPS plan you pick and how long a term you commit to. I locked in a two-year term to get a better rate, which is why I can’t give you a single number that’ll be true for you. Run my n8n cost calculator with your own execution volume and compare it against what you’re paying now.
Is self-hosting n8n hard?
The install isn’t, because the one-click template does it. The part after the install takes about an hour if you’ve never pointed a domain at a server before, and that’s the part I used an AI for. If you can follow steps and paste an error message, you can do this.
What VPS specs do I need to run n8n?
Hostinger’s KVM 1 gives you 1 vCPU and 4GB of RAM, and KVM 2 gives you 2 vCPU and 8GB. More active workflows and heavier AI nodes want more memory. I’d rather you start smaller and move up when something feels slow than buy ahead of a problem you don’t have.
Do I lose my workflows if the server goes down?
Not if you’ve got snapshots turned on and your workflow files backed up somewhere else. Those are two separate safety nets and you want both. Snapshots restore the machine. Exported workflow files let you rebuild the automations somewhere new.
Can I move my existing workflows from n8n Cloud?
Yes. n8n exports workflows as files and imports them the same way. The part that doesn’t come along is your credentials, so plan on re-entering every connection on the new instance. Do that before you cancel anything.
Do I need to know Docker to run this?
No, and I don’t. The template sets Docker up and n8n runs inside it. You’ll see the word Docker in instructions when you’re updating or restarting, which is exactly when an AI walkthrough earns its keep. If the vocabulary is the barrier, my n8n glossary covers a lot of it.
Try it yourself
Self-hosting n8n on Hostinger takes a one-click template for the install, then a domain, an HTTPS certificate, and one n8n setting so webhooks point at the right place. The install is minutes. The rest took me about an hour with an AI reading my errors back to me. If you’re rationing how often your workflows run, that’s the signal it’s time.
Start with the calculator so you know whether the move makes sense for your volume, then grab the prompts above when you’re ready to build it.
A tool I built
Energy Battery
Log your energy through the day and watch your battery fill, so you can see what actually charges you and what drains you.
Find your spark →I run an affiliate program on the tools I build. Approved affiliates earn 20% on what their referrals pay, for up to a year. US only for now. See the program →
Related reading
- Should You Self-Host n8n? Run the Math First
- How I Back Up Every n8n Workflow Automatically
- The n8n Vocabulary Guide for People Who Are Not Developers
- Free Webhook Tester for n8n (See Every Request in Real Time)
Subscribe if you haven’t already, and I’ll keep bringing you the builds, including the parts where I had no idea what I was doing. Go forth and automate the boring stuff.
