Files
k3s-cluster/n8n
Roger Oriol 66433ff0b1 fix tls: use letsencrypt-prod cluster-issuer for jellyfin/n8n/qbittorrent/myorg/phoenix/fava
The ingresses referenced a Cloudflare OriginIssuer 'prod-issuer' whose CRD
and controller are not installed in the cluster, so cert-manager could not
issue certs and Traefik served a default cert (invalid SSL). Switch to the
existing letsencrypt-prod ClusterIssuer with specific hostnames + per-app
secrets, matching the working ingresses (http-01 cannot issue wildcards).
2026-06-23 11:46:38 +02:00
..
2026-01-24 11:19:21 +01:00
2026-01-24 11:19:21 +01:00
2026-01-24 11:19:21 +01:00
2026-02-02 20:47:09 +01:00
2026-01-24 11:19:21 +01:00
2026-01-24 11:19:21 +01:00

n8n-kubernetes-hosting

Get up and running with n8n on the following platforms:

If you have questions after trying the tutorials, check out the forums.

Prerequisites

Self-hosting n8n requires technical knowledge, including:

  • Setting up and configuring servers and containers
  • Managing application resources and scaling
  • Securing servers and applications
  • Configuring n8n

n8n recommends self-hosting for expert users. Mistakes can lead to data loss, security issues, and downtime. If you aren't experienced at managing servers, n8n recommends n8n Cloud.

Contributions

For common changes, please open a PR to main branch and we will merge this into cloud provider specific branches.

If you have a contribution specific to a cloud provider, please open your PR to the relevant branch.