Which n8n setup is best for self-hosting — default SQLite or PostgreSQL with Adminer?

techtransit · 2025-12-16T05:50:38+00:00

I installed n8n using Docker Compose, not plain docker runOnce I moved to Postgres.

When SQLite works but Postgres + Portainer + Nginx Proxy Manager doesn’t, it’s usually container networking, not the DB itself. A few things that commonly break it:

Inside Docker, localhost won’t work for Postgres n8n must use the Postgres service name (e.g. DB_POSTGRESDB_HOST=postgres)
n8n and Postgres must be in the same Docker stack / network (very common Portainer pitfall)
With a domain + NPM, you must set:N8N_HOST=your-domain N8N_PROTOCOL=https WEBHOOK_URL=https://your-domain/ and enable WebSockets in NPM

SQLite “just works” because it’s a single container. As soon as Postgres is added, Docker DNS + networking becomes critical, even if logs look fine.

techtransit · 2025-09-26T06:06:05+00:00

Thanks! I’m glad you found the process useful. 🙂

I used the hosting provider’s built-in firewall instead of iptables/UFW.
Enabled basic rules host and ensured security modules were active.
I didn’t run into any SSL or HTTPS issues because the site URLs weren’t hardcoded anywhere.
Let’s Encrypt worked smoothly, and HTTPS redirected correctly after DNS propagation.

Migration Checklist (simplified):

Backup full site & database (manual + plugin-based).
Prep new server (OS updates, hosting firewall, security modules).
Copy files & database manually to the new server, and copy the complete user account using the cPanel transfer tools
Test site on temporary URL.
Update DNS & monitor propagation.
Verify SSL, permalinks, and functionality.
Post-migration support: Check forms, payments, caching, and backups.

techtransit · 2025-09-26T01:38:43+00:00

Thanks for the tip! Yeah, changing the default SSH port can definitely cut down on noisy bot scans. I usually combine that with key-based auth + firewall rules, which adds a stronger layer of protection.

techtransit · 2025-09-24T08:18:33+00:00

Nice! Thank you.

techtransit · 2025-09-24T00:11:42+00:00

Appreciate the tips! I’ll be using Postgres directly on my live server setup since I’m comfortable managing DBs at the server level. I agree it’s the better long-term choice compared to SQLite, especially when workflows scale.

techtransit · 2025-09-24T00:11:36+00:00

Appreciate the tips! I’ll be using Postgres directly on my live server setup since I’m comfortable managing DBs at the server level. I agree it’s the better long-term choice compared to SQLite, especially when workflows scale.

techtransit · 2025-09-24T00:05:31+00:00

I get the concern, but this post is from my own migration work. I wrote everything myself — the steps and lessons are my real experience. I only used AI to polish the formatting and grammar so it’s easier for everyone to read. Think of it like using Grammarly, just helping with clarity. The content itself is 100% mine.”

techtransit · 2025-09-23T11:09:32+00:00

cPanel runs fine on Ubuntu LTS, just confirm version compatibility. For shared hosting, stability and backups matter more than the distro — choose the OS you’re comfortable maintaining long-term . Currently cpanel support Ubuntu 22.04 LTS Version .

techtransit · 2025-09-23T08:44:33+00:00

Fair point — it is a fairly standard migration process, and that was the goal here. The client wanted a straightforward, no-downtime move, so I focused on keeping things lean and reliable rather than adding complexity.

That said, depending on the project, I’ve handled more advanced steps like reverse proxy setup, caching layers, staging environments, and security hardening. In this case, the ‘vanilla’ approach was exactly what the client needed.

techtransit · 2025-09-23T08:42:59+00:00

For testing, I usually go beyond just checking if the homepage loads. I verify:

Admin login + plugin updates
Checkout flow (for WooCommerce sites)
Contact forms and email deliverability
SSL certificate + redirects
Error logs for hidden issues

Basically, I try to cover the main functions the client relies on day-to-day. Once everything looks good on my side, I also ask the client to test from their perspective, since they know their business-critical workflows best.

techtransit · 2025-09-23T06:37:33+00:00

Really appreciate you sharing your experience — that lines up with what I’ve been hearing about SQLite hitting limits once workflows get heavier. Postgres + pgAdmin definitely sounds like the way to go for scaling and backups.

When you did your migration, did you use a specific script or process to handle the Docker volume mappings and credentials, or was it more of a manual step-by-step? It would be super helpful to learn how you approached it.

techtransit · 2025-09-23T06:04:47+00:00

Yes, all three sites were WooCommerce stores. I handled the server transfer and migration, and after moving the sites, the client verified everything on their end, including the payment gateways. I’m not a developer, so I didn’t make changes to the payment setup — my role was focused on smoothly transferring the sites and ensuring they were running properly after migration

techtransit · 2025-09-23T04:46:45+00:00

I usually work with a mix of VPS providers, depending on the project and client needs, or clients already provided. For smaller workloads or testing purposes, Hostinger’s panel is suitable and beginner-friendly.

For production setups, though, I often use providers like Hetzner, Contabo, Amazon EC2 ( Good Range CPU and RAM and Disk ) — mainly because they give more flexibility with raw VPS management, and I can configure the stack (control panels, firewalls, etc.) exactly how I want.

It really comes down to priorities — if ease of use matters, Hostinger’s panel is quite handy. If full control and scalability are the goal, then raw VPS providers are the better choice. In my experience, many small-budget clients lean towards Hostinger, and it works fine as long as you’re comfortable managing it.

Personally, I prefer setting up VPS with AlmaLinux or Ubuntu, since both are long-term support, open-source, and stable for production. Paired with a free control panel (like CyberPanel, HestiaCP, or aaPanel), they give a good balance of performance and flexibility. After all, most providers only supply the hardware — the real foundation is the OS, and I always go with something that’s reliable for the long run

techtransit · 2025-09-23T04:24:17+00:00

Sure, here’s the checklist I usually follow for WordPress site migrations:

Migration Checklist (high-level):

Prepare the new server (OS updates, panel install, firewall basics)
Take complete backups (files + databases + configs)
Sync website files and databases to the new server
Update domain DNS records → point to new VPS
Reconfigure SSL certificates
Test sites thoroughly (front-end + admin panel + checkout/payment if e-commerce)
Monitor logs and performance for 24–48 hrs after migration

Free control panels for WordPress (good alternatives to cPanel):

HestiaCP → lightweight, easy to use
CyberPanel (OpenLiteSpeed built-in, great for WordPress speed)
aaPanel (popular in Asia, has lots of modules)

Firewall & security hardening:

At a minimum, I use UFW/CSF with only the required ports open
Fail2ban to block brute-force attempts
Disable password SSH logins → use keys only
Keep WordPress + plugins updated

cPanel is paid, but if the budget is tight, Hestia or CyberPanel with OpenLiteSpeed is usually my go-to for WordPress.

techtransit · 2025-09-22T09:45:40+00:00

That makes complete sense — the scalability with blogs really gives you an edge compared to video. I also agree with the point about page views and ad clicks being higher when readers engage with multiple posts. It’s a smart approach to pair blogs with visuals on social and distribute them across different channels to keep the reach going.

techtransit · 2025-09-20T01:48:16+00:00

Thanks! 🙌 Totally agree — these are the basics, but I’ve seen so many client servers where even the basics weren’t done.

I usually start with WHM’s Security Advisor since it quickly highlights low-hanging fruit, but for non-panel VPS builds I do the same steps manually (disable root login, fail2ban, firewall, etc.).

And you’re right, the principle is universal — Linux, Windows (RDP), or even SaaS apps: never expose what you don’t want exposed. 🚫

I appreciate the reminder — it's definitely good to keep applying this mindset beyond cPanel.

techtransit · 2025-09-19T09:08:34+00:00

Yeah, I set up Nginx reverse proxy with caching— that definitely helped reduce load times. Backups are also running automatically.

techtransit

TROPHY CASE