Webhook URL still shows "localhost" in UI even with WEBHOOK_TUNNEL_URL set

Questions
1

Describe the problem/error/question

Even after setting the environment variable WEBHOOK_TUNNEL_URL=https://<my-domain> in my Docker-based production deployment, the webhook URL shown in the n8n UI still displays as http://localhost:5678.

I also tried setting VUE_APP_URL_BASE_API=https://<my-domain> just in case.

Both variables are correctly loaded into the container (verified via docker exec).
Additionally, I’m accessing n8n via the correct domain (not localhost), using HTTPS through a reverse proxy.

I upgraded from version 1.100.1 to 1.102.0 and the issue still persists.

What is the error message (if any)?

No error message. The issue is that the UI continues to show the webhook path with localhost.

Please share your workflow

This happens with even a basic workflow with a single Webhook node.

Share the output returned by the last node

N/A — This is a UI-level issue, not related to execution.

Information on your n8n setup

  • n8n version: 1.102.0
  • Database: Postgres
  • EXECUTIONS_PROCESS: queue mode with Redis
  • Deployment: Docker Compose with Traefik reverse proxy
  • TLS: handled via Let’s Encrypt
  • OS: Ubuntu 24.04 LTS

Final question

Is this expected behavior in the Editor UI?
Is there another variable or workaround to make n8n UI display the correct public webhook URL?

Thanks in advance!

2

Hi @abdulaziz.alfarra, welcome to community!
I think you did something wrong, because WEBHOOK_TUNNEL_URL already deprecated, see below:
n8n v1.0 migration guide | n8n Docs

Instead, you need to set it with WEBHOOK_URL environment.
You can read here for complete docker compose file from official documentation.

Below is my compose configuration, hope it can be your guide.

image
image653×141 4.69 KB

Oh! Almost forgot, if it helps your problem, kindly mark my message as solution, thanks!:slight_smile:

3

Hi
thank you for response.

I edited .env and added WEBHOOK_URL
The issue was resolved

thank you a lot

4

You’re welcome!
By the way, can you mark my message as solution? It makes me feel happy to be your helper:)

5

yes
your message was a solution

6

Okay, no problem…:slight_smile:

8

I think it’s coming from your dns (?), what is your purpose to add the dns there?

9

ahhh got it! now it works, I just followed this dns from another setup and removed it. thank you so much

10

You’re welcome!