"n8n User Auth" in "Chat Trigger" seems redirect to the wrong url when N8N_PATH is set

[chhaj5236]

Bug Description

I set N8N_PATH to "/n8n/" and set "Chat Trigger" to "n8n User Auth". Then I open "Chat Url" in a web browser, it will redirect me to http://localhost:5678/signin?redirect=http://localhost:5678/n8n/webhook/xxxx/chat, but http://localhost:5678/signin does not exist.

I checked the source code and found that "Chat Trigger" does not take N8N_PATH as the prefix when trying to check the user auth or redirecting the url.

I also checked http://localhost:5678/n8n/rest/login is working as expected, but http://localhost:5678/rest/login is not.

I wonder if I miss something like other environment need to be set?

To Reproduce

1. Set environment N8N_PATH to /n8n/ and WEBHOOK_URL to http://localhost:5678/n8n/ then deploy the n8n service.
2. Go to Workflows page and add a new workflow and a Chat Trigger node.
3. Activate the workflow.
4. Open Chat Trigger node, Make Chat Plublic Available and set Authentication to n8n User Auth.
5. Copy Chat Url and open it in the web browser.
6. The browser will redirect to the url without "/n8n/" and failed.

Expected behavior

should redirect to the Chat Window.

Operating System

n8nio/base

n8n Version

1.31.0

Node.js Version

18.19.1

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @chhaj5236,

I have created NODE-1296 as the dev ticket to look into this in more detail, Out of interest is using the n8n_path a requirement in your environment or if needed would you be able to swap to a subdomain instead?

[chhaj5236]

Hi @Joffcom, thanks for the feedback. It's not easy for us to apply a subdomain, n8n_path is a good feature for us to serve n8n behind a proxy by using a different sub-path.

[Joffcom]

Hey @chhaj5236,

Is that a different sub path for multiple instances? One of the chats we have had internally was around possibly removing support for n8n_path in the future as we don't see it being used that often so it would be great to understand a bit more around what you are doing with it.

[chhaj5236]

@Joffcom It's not for multiple n8n instances, we have other services behind the proxy.

[javierfuentesm]

@chhaj5236 I'm getting a similar issue, with the chat trigger.

In this screen, the chat works fine

but when I open the chat after "publishing" it, I get an error. This window is calling the localhost, but I have never used the localhost; I have always used railway

any idea what it can be?

I have this in the env variables

[javierfuentesm]

oh and when i put the n8n authentication i get this