Migrated sqlite database to new server will not apply .env webhook URLS

Questions
1

This took me a while to figure out but on my migrated database, when i set the following in my .env file:

N8N_HOST=automation.MYDOMAINHERE.com
N8N_WEBHOOK=automation.MYDOMAINHERE.com
N8N_WEBHOOK_URL=https://automation.MYDOMAINHERE.com
WEBHOOK_URL=https://automation.MYDOMAINHERE.com
N8N_EDITOR_BASE_URL=https://automation.MYDOMAINHERE.com
N8N_PROTOCOL=https
N8N_PORT=5678
N8N_BASIC_AUTH_ACTIVE=true
N8N_BASIC_AUTH_USER=admin
N8N_BASIC_AUTH_PASSWORD=MYPASSWORDHERE$
N8N_SECURE_COOKIE=false
N8N_ENV=production
N8N_LOG_LEVEL=debug
N8N_LOG_OUTPUT=console,file

Debug info

core

  • n8nVersion: 2.18.4

  • platform: docker (self-hosted)

  • nodeJsVersion: 24.14.1

  • nodeEnv: production

  • database: sqlite

  • executionMode: regular

  • concurrency: -1

  • license: community

  • consumerId: unknown

storage

  • success: all

  • error: all

  • progress: false

  • manual: true

  • binaryMode: filesystem

pruning

  • enabled: true

  • maxAge: 336 hours

  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36

  • isTouchDevice: false

security

  • secureCookie: false

Generated at: 2026-04-30T04:29:24.861Z

Operating System

linux debian

n8n Version

see above

Node.js Version

see above

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

3

Sent you a dm btw.

4

Hi @Nicolas_Zein, on top of what @Miliaga said about N8N_WEBHOOK not being a real var, you also have a leading space after every = in your env file (N8N_HOST= automation...) — docker reads that space as part of the value, so N8N_HOST becomes automation.MYDOMAINHERE.com and the URL never matches. strip every space right after the =. quick test workflow to confirm webhooks resolve to your domain after fix:

import, activate, hit /webhook/test-url — the production URL shown in the node panel should now start with https://automation.yourdomain.com.

5

@achamm hey buddy, where do you see a space?

6

It was from the way that the forum rendered it at first, just make sure your env file is in right format! It should work then!