Reverse Proxy community node credentials error

Describe the problem/error/question

While running through reverse proxy community nodes are not working (everything else is, even webhooks). Using local host the credentials work fine for community nodes and workflow works, but webhooks are in turn not working externally (as expected)

Please share your workflow

Share the output returned by the last node

Docker Settings:
N8N_PROTOCOL = https
N8N_PORT = 5678

Information on your n8n setup

  • n8n version: 1.25.1
  • Database (SQLite):
  • n8n EXECUTIONS_PROCESS setting (main):
  • Running n8n via (Docker):
  • Operating system: Unraid

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:

Hey @Joonasself,

Welcome to the community :tada:

I have just checked one of my community nodes that uses a webhook and it appears to be working fine with my reverse proxy which makes me wonder if the issue is with the node.

Are you seeing any error messages that may help and have you raised an issue with the creator of the node or is it your node?

Hey! Thanks for the reply! Glad to be here.

I have a feeling it’s related to reverse proxy/docker setup as it possibly can’t communicate with the base url properly, but not sure how to confirm that.

The nodes work fine without reverse proxy. Credentials are correct and the whole workflow works. When accessing via proxy and subdomain is where the community node starts error out. Built in nodes still work perfectly.

Could you share your docker and reverse proxy settings for me to test?

Hey @Joonasself,

What makes you think it is the credential causing the issue? A reverse proxy is of course for inbound traffic not outbound so if the authentication is failing on the third party service it is unlikely to be the proxy but if the issue is with the connection coming back into n8n then it could be the proxy but you should be able to check the request logs to see what is coming in.

We have 2 examples for running n8n behind a reverse proxy one uses Traefik and the other uses Caddy. Personally I use nginx but I am not sure how helpful my nginx settings would be for you.

Traefik: Docker Compose | n8n Docs
Caddy: Digital Ocean | n8n Docs