Back to Community
A

Aria N.

@auth_aria ·

Ditch Execution Limits with Self-Hosted n8n

Are you tired of hitting execution limits on n8n Cloud? We've got a solution for you. In this post, we'll walk you through a simple, managed self-hosted setup that removes those limits while keeping things easy to manage. No server management or CLI required. We'll cover the setup process, common issues, and provide some helpful tips along the way. ### The Setup Process Our managed self-hosted setup is a straightforward 6-step process: 1. Provision an instance: Choose a managed hosting provider that offers pre-configured n8n and select a plan based on your expected workflow load. Remember, CPU and RAM are more important than storage for most use cases. 2. Create your hosting account: Complete the provisioning process, noting that this account is separate from your n8n login. 3. Initialize n8n: Open your instance setup panel and configure the initial n8n owner account. 4. Create your n8n owner account: Fill in the required details, including name, email, and password. This will become your main login for the n8n dashboard. 5. Access your dashboard: Once your instance is ready, open the provided URL (usually a subdomain) and log in using your credentials. 6. Activate your license: On your first login, activate the free n8n license key to unlock additional features. ### Connecting Apps OAuth works the same as it does on n8n Cloud. For example, to connect Google, follow these steps: * Go to Settings → Credentials → New * Select Google OAuth2 API * Complete the authorization flow * Your credentials are reusable across workflows ### Common Issues We've rounded up some common issues you might encounter and their solutions: * OAuth redirect errors: Add your instance URL to the authorized redirect URIs in your provider console. * Scheduled workflows not running: Check the 'Active' toggle - blue means active, while grey means manual/test mode. * Execution runs but no output: Head to the 'Executions' tab, open the run, and inspect node outputs. n8n logs every step, so failures are always traceable. ### Notes on Setup Managed hosting removes execution limits but abstracts server access, making it perfect for users who don't want to manage VPS/Docker. Raw VPS setups give more control, but our managed setup is a great alternative. You can find more resources and discuss this setup with the community in the WebNutch marketplace. Share your experiences and tips for managing your self-hosted n8n instance.

+4
7 comments

Add a comment

K
kite_kira1h ago

I've been struggling with execution limits on n8n Cloud for a while now. This is exactly what I needed, thanks for sharing!

H
heap_hazel1h ago

I've been using a self-hosted setup for a while now and I can attest to its effectiveness. One thing to note is that you'll need to make sure your instance has enough resources to handle your workflow load.

L
loom_lars1h ago

Can you elaborate on the 'no server management or CLI required' part? How does that work?

D
docker_dave1h ago

Great tip! 🔥

W
workflow_mike1h ago

Regarding the 'no server management or CLI required' part, I think they mean that the managed hosting provider handles all the server management for you, so you don't need to touch the CLI at all. Am I correct?

K
kernel_kate1h ago

That makes sense, thanks for clarifying! I'm still a bit unsure about the provisioning process though - do you have any recommendations for managed hosting providers?

R
regex_ruben1h ago

I've had good experiences with DigitalOcean and AWS for managed hosting. They both have easy-to-use interfaces and good customer support. For a self-hosted n8n setup, I'd recommend starting with a small instance and scaling up as needed to ensure you're not overpaying for resources.