Self-hosted N8N connection to self-hosted Baserow certificate validation issue

Questions
,
1

Background/Environment

o Self-Hosted N8N
o Self-Hosted Baserow

Describe the problem/error/question

Setting up credentials for Baserow is base auth: Username/Password

  1. I use the Baserow basic auth credentials to connect using the Baserow node.
  2. Operation: Create
  3. Database Name or ID: “Error fetching options from Baserow.”
  4. Hover-over /!\ shows:

Issues:

  • There was a problem loading the parameter options from server: “unable to verify the first certificate”

I’m assuming this means it’s only going to connect on a valid certificate. But in a self-hosted situation, we’re going to be dealing with self-signed certs. Of course they aren’t “valid.”

Now what? Seems like I’m screwed unless I stand on my head and create a valid certificate from my own CA and ask the browser to trust it – which still seems suspect (how does N8N determine valid certs?)

Information on your n8n setup

  • n8n version: 1.95.3
  • Database (default: SQLite): Yes
  • n8n EXECUTIONS_PROCESS setting (default: own, main): \0/
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Linux
2

hello @ChrisEOlive

You can import custom certificates.
Configure n8n to use your own certificate authority | n8n Docs

By default, n8n won’t trust any custom certificates.

1 Like
3

Me to Me: “Gee, bro. Maybe check the docs next time. ‘Cert’ in search brings up this exact topic.” :man_shrugging:

Thanks!

4

The n8n docs don’t really give any clues about what format the CA cert needs to be in. Or maybe I’m just revealing I don’t know enough about certs. Any light you can shed there, assuming you’ve done this (which also may be a bad assumption)?

5

Nevermind. A simple .crt export worked.

1 Like