I have setup a N8N instance behind a NGINX reverse proxy, routing to a base path of /n8n. I have set N8N_PATH=/n8n accordingly and can access my n8n instance by navigating to http://localhost/n8n
Everything is working fine except when navigating to /n8n while unauthenticated, I am redirected to a signin page which appends a redirect query string param of localhost/n8n/signin?redirect=%25fn8n. Because of this, when logging in, I am then redirected to localhost/n8n/n8n, which results in a 404.
I am trying to determine how to get N8N to resolve this redirect correctly in this scenario. Is there a specific header or something that N8N uses to compute this redirect? Thx!
Basically, we’re setting up a N8N instance on K8s on a shared domain “example.company.com” with the intention of routing N8N traffic to example.company.com/n8n. Originally, we had some difficulty getting the nginx ingress to rewrite to N8N container at / so after digging through your forums, we saw a recommendation to set the N8N_PATH=/n8n to match our route with the appropriate rewrite rule. This worked fine in every way except for the redirect on login which resulted in the redirect after login going to example.company.com/n8n/n8n.