After hours of mysterious Docker errors, permission denials, 403s, blank screens, and cookies screaming for HTTPS...
Today, I finally saw it.
The n8n Owner Account Setup Screen.
It was beautiful.
It was victory.
☁️ What happened
I wanted to self-host n8n on a remote Ubuntu server (Oracle Cloud), using Docker.
It should have been simple. But reality had other plans:
Docker container was exiting immediately → Permission denied for config file
Mounted volumes failed silently
“n8n is starting up… Please wait” — and it never stopped waiting
Then... "Cannot GET /"
Then... a warning about secure cookies and missing HTTPS
Then… nothing
🔧 The Fix
In the end, I did the following:
bashCopyEdit# Give correct permissions
sudo chmod -R 777 ~/.n8n
# Add environment variable to allow insecure cookies (only for testing!)
-e N8N_SECURE_COOKIE=false
And then, like magic:
🚀 n8n launched.
🔐 Owner setup appeared.
🎉 Victory coffee secured.
☕ Why this matters
I’m not a DevOps wizard. I just wanted to automate things without paying monthly fees.
And now I have my own automation system, running 24/7, for free.
This isn’t just about n8n.
This is about freedom.
💡 What I’ll do next
I plan to build:
Webhooks that respond with AI-generated replies
Auto-tweet bots
Workflow bridges between voice input and databases
Systems that make my life easier, silently
If you’ve ever wanted to self-host your own tools and thought,
“I don’t know enough to do this.”
I say:
You can.
Start messy. Break things.
Fix them.
And celebrate the small victories.
Thank you for reading! 🙌
If you want to support my experiments:
☕ Buy me a coffee and fuel the next automation adventure.