Skip to content

[DOCS-ISSUE] - SPA redirects generate double subpath (/subpath/subpath) on n8n self-hosted behind reverse proxy (with N8N_PATH), impossible to use folders [v1.123.5] #4003

@dan76dsk

Description

@dan76dsk

Where is the bug/mistake?

Page:
https://docs.n8n.io/hosting/configuration/environment-variables/
or
https://docs.n8n.io/hosting/configuration/configuration-examples/base-url/


What problem did you find?

There is a significant issue with n8n self-hosted instances deployed behind a reverse proxy under a subpath (using N8N_PATH). Most of the Editor UI works correctly with the subpath, except for one scenario:

When in the "personal/workflows" section, if you try to enter (click into) a folder that contains flows, the Editor UI generates a link (href) with a duplicated subpath.
For example, if your subpath is /secure-n8n-panel/, the generated link becomes:

/secure-n8n-panel/secure-n8n-panel/projects/<projectId>/folders/<folderId>/workflows

As a result, clicking this link leads to a 404 error and makes it impossible to access folders in this section.

This double subpath issue does not occur anywhere else in the UI. All other navigation and workflow editing works normally with the configured subpath.


Additional context

  • The issue occurs only in the "personal/workflows" section and specifically when clicking into a folder with flows.
  • Confirmed on n8n version 1.123.5, Docker, with official documentation-based N8N_PATH and reverse proxy setup.
  • The generated <a href> in the HTML points to the doubled path (e.g. /secure-n8n-panel/secure-n8n-panel/projects/...).
  • Other routes or navigation within n8n handle the subpath correctly.

This edge case is not currently documented and can cause significant confusion for users trying to deploy n8n under a subpath.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions