ResumeURL not pulling in WEBHOOK_URL env var

[dajinchu]

Bug Description

Webhook url environment variable is set, but resumeUrl is using localhost instead of webhook url's hostname.

To Reproduce

1. Self-host N8N behind proxy and set WEBHOOK_URL environment variable
2. Verify that webhook urls are correct
3. Create a Wait block. The generated $execution.resumeUrl is localhost, instead of the webhook URL

Expected behavior

I would expect the webhook-waiting url to use the webhook url hostname.

Debug Info

Verified that our webhooks have the proper host, indicating the webhook env var is set.

Used a simple flow to extract resumeUrl

Operating System

Docker n8nio/n8n:1.108.2-arm64

n8n Version

1.108.2

Node.js Version

22.17.0

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

[Joffcom]

Hey @dajinchu,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-4649".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

[Joffcom]

Hey @dajinchu

Can you share all of the env options you have set?

[dajinchu]

Hi @Joffcom

Here's all the env vars we have set.

DB_POSTGRESDB_DATABASE
DB_POSTGRESDB_HOST
DB_POSTGRESDB_PASSWORD
DB_POSTGRESDB_PORT
DB_POSTGRESDB_SCHEMA
DB_POSTGRESDB_SSL_REJECT_UNAUTHORIZED
DB_POSTGRESDB_USER
DB_TYPE
EXECUTIONS_MODE
N8N_AVAILABLE_BINARY_DATA_MODES
N8N_DEFAULT_BINARY_DATA_MODE
N8N_EDITOR_BASE_URL
N8N_ENCRYPTION_KEY
N8N_EXTERNAL_STORAGE_S3_AUTH_AUTO_DETECT
N8N_EXTERNAL_STORAGE_S3_BUCKET_NAME
N8N_EXTERNAL_STORAGE_S3_BUCKET_REGION
N8N_EXTERNAL_STORAGE_S3_HOST
N8N_LICENSE_ACTIVATION_KEY
N8N_LOG_LEVEL
OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS
QUEUE_BULL_REDIS_HOST
WEBHOOK_URL

[dajinchu]

@Joffcom Further investigation shows that despite WEBHOOK_URL being set, changing N8N_HOST changes resumeUrl. This is not an effective workaround though because we cannot change N8N_PORT (load balancer serves traffic on 443 but n8n runs on 5678)

[Joffcom]

Hey @dajinchu,

Sorry for the crazy delay on this one, I have just given it a test and I believe you have OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS set to true and that your workers don't have WEBHOOK_URL set.

If this is the case can you make sure WEBHOOK_URL is available to the workers and it will resolve the issue.

#triage:in-progress

[n8n-assistant]

As we haven’t heard back from you, we’re going to close this issue to keep things organized. But don’t worry, if you have more information or need further assistance, you’re welcome to reopen the issue anytime or create a new one. We’re always happy to help!

Thanks for reaching out and have a great day! If this was closed by mistake and you have been waiting for us let me know and I can also re-open it.