Credential callback url using webhook url, but fails, because webhook url is the webhook processor

Questions
1

Running two separate services, main and webhook processor running with EXECUTIONS_MODE="queue". I have the WEBHOOK_URL set to the the webhook processor.

When trying to setup a credential such as google with callback urls, I’ve noticed that it provides the url with the hostname as the WEBHOOK_URL hostname, where if you try the url, it’ll say the path does not exist. However, if you try the path of the url with the main url, it will work.

I was confused and curious whether I was either doing something wrong or the callback url should be using the regular hostname instead of the WEBHOOK_URL one.

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3
  • n8n version: 1.71.3
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): n/a
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: n/a
4

Hey @jacklaffin

Welcome to the community :raised_hands:

Assuming you are using 2 different URLs you will need to also set N8N_EDITOR_BASE_URL this value is then used for anything that needs to go to the main instance like test webhook executions or oauth redirects.

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.