AI Agent MySQL Requires SSL Despite SSL Being Disabled

I’m having trouble with the AI Agent MySQL. Despite having SSL disabled in my MySQL user configuration, the AI Agent MySQL node requires a secure connection. Interestingly, the regular MySQL node works without any issues.

Error: Server does not support secure connection at ClientHandshake.handshakeInit

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

Hey @Sziskey,

This sounds like a known issue that I started fixing a while back but never finished, I will get the fix finished this week.

1 Like

Hey @Jon ,

Just checking in—any updates on the fix for the AI Agent MySQL SSL issue? Thanks!

Hey! I hit the same issue today.
Would love to know if it can be fixed.

Is there any update on this topic?

Issue persists…

@Jon was this fixed?

It wasn’t I got caught up with other issues but we also have a new preferred way to connect to servers with untrusted certs that will work, you can find instructions here: Configure n8n to use your own certificate authority | n8n Docs

Oh… I use n8n.cloud… And one of the reasons we wanted to migrate to n8n is actually to use the Database Agent AI :sweat_smile:

I see that the newst MySQL version (8.0.40) provides SSL by default… Do you think that if we update the server version it will work? Or should we consider moving into a different database?

One possible solution could be to use a signed certificate that should work other than that it will need the change merged if you are on cloud.

1 Like

Thanks for the answers! Will try to get it running with a SSL certificate and see what I get.

This worked! Thanks a lot for the help :slight_smile:

I’d also love to see a resolution for this issue. I am in the midst of a trial of n8n and struggling for hours with connecting to our server’s database. If I could simply connect to my DB without SSL it would be very helpful. Otherwise we will cetainly not continue using n8n in a paid plan.

Any luck fixing this issue?

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