Self-signed certificate in certificate chain

Questions
1

Describe the problem/error/question

I’m trying to connect to a supabase database through the postgre node. This is not the database of n8n, is another one different. It keeps saying “self-signed certificate in certificate chain” even though thre SSL is not toggled.

image
image1212×765 28.5 KB

I can download a certificate from supabase as chatpgt recomends but then the env. variables on n8n are asking for a key, which I dont have. im using a domain I purchased on namecheap to acess my instance.

Please help!!

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite): Sudabase
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker on render.com
  • Operating system: n/a
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:
4

hello @donpablo

Even if the SSL is not enabled, turn on the button
image

5

can you please scroll down and share a screenshot of the second half of that screen ?

6

I tried everything and decided to switch from render.com to digitalocean. cheaper and easier to set up. The fix was setting up the reverse proxy on Caddy properly to send the certificates. Used the digitalocean guide step by step and it worked!

thanks for the help guys

2 Likes
7

It is nice that it is working but the fix shouldn’t have fixed this, I suspect there was another change.

I have this a test earlier today and for me my supabase instance connected with no issues, I then went into supabase and enabled the option to make ssl a requirement and that then meant I had to set the ssl option in n8n but I got the same error about the self signed cert, to fix it I just had to enable the ignore ssl issues option and it started working.

8

same here

i can connect to PG when I select ignore SSL

image
image1748×1170 101 KB

but when I’m using same cred in SQL AI agent “ignore SSL” is ignored )
image
image2320×936 117 KB

and [ERROR: self-signed certificate in certificate chain]
appears again

9

Hey @Antonio1,

The SQL Agent doesn’t yet support the SSL ignore options, I think I do have an internal PR for this somewhere that I will dig out and update.

10

thank you Jon
have a great day

11

Is there a way to work around this, until SQL Agent supports the SSL ignore options?

I’m trying to make SSL required but I get the same error as Antonio1

13

This must still be a thing. Have you found a workaround?

14

the workaround would be to completely disable the SSL checks for n8n instance.

It can be done with the env variable NODE_TLS_REJECT_UNAUTHORIZED='0'

But that’s a very bad solutions in term of security