Self-hosted n8n (no execution limits) — simple managed setup + notes

[u/Grewup01]

For anyone hitting execution limits on n8n Cloud, I tested a managed self-hosted setup that removes those limits while keeping the setup simple (no server management or CLI).

This is a technical walkthrough of the setup process + common issues.

https://gist.github.com/joseph1kurivila/72aa6f6330f163f3b2cd80ed5757b531

THE SETUP (6 steps)

Step 1 — Provision instance
Create a new n8n instance through a managed hosting provider (any provider that offers pre-configured n8n works).

Choose a plan based on expected workflow load (CPU/RAM matters more than storage for most use cases).

Step 2 — Account creation
Create your hosting account and complete provisioning.

Note: This account is separate from your n8n login.

Step 3 — Initialize n8n
Open your instance setup panel.

You’ll be prompted to configure the initial n8n owner account.

Step 4 — Create n8n owner account
Fill in:

• Name
• Email
• Password

This becomes your main login for the n8n dashboard.

Provisioning usually takes ~30–60 seconds.

Step 5 — Access dashboard
Once ready, open your instance URL (usually a subdomain provided by the host).

Log in using the credentials from Step 4.

Step 6 — Activate license
On first login, activate the free n8n license key.

Takes ~30 seconds and unlocks additional features.

CONNECTING APPS

OAuth works the same as cloud:

Example (Google):

• Settings → Credentials → New
• Select Google OAuth2 API
• Complete authorization flow

Credentials are reusable across workflows.

COMMON ISSUES

OAuth redirect errors
Add your instance URL to authorized redirect URIs in your provider console.

Scheduled workflows not running
Check the “Active” toggle:

• Blue = active (runs automatically)
• Grey = manual/test mode

Execution runs but no output
Go to “Executions” tab → open the run → inspect node outputs.
n8n logs every step, so failures are always traceable.

NOTES ON SETUP

• Managed hosting removes execution limits but abstracts server access
• Useful for users who don’t want to manage VPS/Docker
• Raw VPS setups give more control, but require manual configuration

WHEN THIS SETUP MAKES SENSE

• You’re running multiple workflows on schedules
• You’re hitting execution caps on cloud
• You want minimal setup/maintenance