SSL Error accessing own server webhooks

Describe the problem/error/question

When I call a webhook on my own server the HTTP module returns unable to verify the first certificate. But chrome and web browsers don’t indicate any problem with the certificate.

I changed my server setup a few weeks ago. Before I had the server “behind” a load balancer which also did SSL termination. Now it’s on its own server, and the SSL certificate is installed directly in N8N:

export N8N_PROTOCOL=https
export N8N_HOST=auto.windetergent.com
export N8N_PORT=443
export N8N_SECURE_COOKIE=FALSE
export WEBHOOK_URL=https://auto.windetergent.com/
export N8N_SSL_KEY=/etc/letsencrypt/live/auto.windetergent.com/privkey.pem
export N8N_SSL_CERT=/etc/letsencrypt/live/auto.windetergent.com/cert.pem

I can work around this by setting the “ignore SSL issues” option, but that means I need to go through dozens of automations that were working fine and change that setting.

Did I miss something in the SSL setup for N8N? Is there a certificate chain I need to install somewhere?

Information on your n8n setup

  • n8n version: 1.45.1
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: Ubuntu

Looks like Hookdeck is having the same problem authenticating my certificate. Must be something I missed in the SSL config. I’ll see if I can figure it out.

Fixed it. For those who find this thread in the future, if you’re using letsencrypt for SSL certificates you need to use fullchain.pem as your SSL CERT:

export N8N_SSL_CERT=/etc/letsencrypt/live/auto.windetergent.com/fullchain.pem
2 Likes

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