n8n - 💡(How to fix) Fix migrated sqlite database to new server will not apply .env webhook URLS [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#29552Fetched 2026-05-01 05:52:35
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
0
Timeline (top)
commented ×2closed ×1labeled ×1

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

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

To Reproduce

migrate an sqlite file

Expected behavior

should change the webhook url

Debug Info

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

extent analysis

TL;DR

Update the N8N_WEBHOOK_URL environment variable to reflect the correct domain after migrating the database.

Guidance

  • Verify that the N8N_WEBHOOK_URL environment variable is correctly set to the new domain after migration.
  • Check the database configuration to ensure it is pointing to the correct location.
  • Review the n8n documentation to understand how environment variables are used to configure the webhook URL.
  • Test the webhook functionality after updating the N8N_WEBHOOK_URL environment variable to ensure it is working as expected.

Notes

The issue seems to be related to the environment variables not being updated after migrating the database. The provided debug information suggests that the n8n version and node.js version are up-to-date, but the webhook URL is not being updated correctly.

Recommendation

Apply workaround: Update the N8N_WEBHOOK_URL environment variable to reflect the correct domain after migrating the database. This should resolve the issue with the webhook URL not being updated correctly.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

should change the webhook url

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix migrated sqlite database to new server will not apply .env webhook URLS [2 comments, 2 participants]