Prisma•2y ago

Unable to connect Prisma to RDS database

I am deploying a beta version of my webapp to prod however I am unable to connect to my RDS db. I have tried multiple different engines (Aurora Mysql, Mysql 8.0.35, MariaDB 10.11.6)
I keep getting the error "PrismaClientInitializationError: Authentication failed against database server at

db-host

db-host

, the provided database credentials for

db-user

db-user

are not valid"

The credentials are definitely correct and I have tested connecting to the database without Prisma and it works perfectly fine.

Any guidance would be greatly appreciated as I have been troubleshooting this issue for 3 days with no luck.
Thanks in advance

Lord ZdOP•7/10/24, 11:50 AM

Just to add to that I was at one point getting an error about the authentication plugin however I havent been able to recreate this.

Lord ZdOP•7/10/24, 12:07 PM

@RaphaelEtim Hey dude are you able to help on this matter, appologies If i shouldn't of @ you im not sure what the
etiquette is.

RaphaelEtim•7/10/24, 2:21 PM

Do you have special characters in any part of your connection url? If yes, you would need to percent encode them as shown in this part of the documentation

Connection URLs (Reference) | Prisma Documentation

Learn about the format and syntax Prisma ORM uses for defining database connection URLs for PostgreSQL, MySQL and SQLite.

Yetzederixx•7/10/24, 2:39 PM

Randomly generated passwords with special characters is what got me for a bit, went straight alphanumeric and it solved that problem for me.

Lord ZdOP•7/10/24, 2:57 PM

I do not have any special characters in the password as I read something about needing to escape out special chars so for testing purpose I have been using 1175ZE90ss3Kv7weCXsWxOJphj7AJ0REb7

Lord ZdOP•7/10/24, 2:57 PM

I will try using a non random generated one and see if that helps

Yetzederixx•7/10/24, 3:08 PM

Nah, yours should be fine, hrm

Yetzederixx•7/10/24, 3:10 PM

I'm hesitant to ask for your connection string since that'd expose the entire db, but one other problem I had was a copy/paste error that messed with the separator between the user/password

Yetzederixx•7/10/24, 3:11 PM

The easiest way to debug that imo is to copy/paste the string into the postgres, or whatever, command line tool

YYetzederixx I'm hesitant to ask for your connection string since that'd expose the entire db...

Lord ZdOP•7/10/24, 5:30 PM

Hmm yeah I had a feeling that could be an issue where ive been copying from password manager

Lord ZdOP•7/10/24, 6:06 PM

Ive tired hand typed password and connection string and neither worked unfortunately

Yetzederixx•7/10/24, 6:22 PM

I'm gonna be switching jobs, aka rigs, here shortly, I'll come back to this and see what I can think of

Yetzederixx•7/10/24, 6:22 PM

I don't have a prisma project for the one I'm working on currently

Lord ZdOP•7/10/24, 6:45 PM

Much appreciated

Yetzederixx•7/10/24, 6:59 PM

postgresql://DB_USER:DB_PASS@DB_HOST:DB_PORT/DB_NAME

mine conn string has at the end, but psql won't take it, copy everything of yours and issue

and see if you can connect

Yetzederixx•7/10/24, 7:01 PM

Yetzederixx•7/10/24, 7:03 PM

Lord ZdOP•7/10/24, 7:11 PM

Here are some of the variations ive tried I have shortened the hostname as to not expose the db

Lord ZdOP•7/10/24, 7:12 PM

Lord ZdOP•7/10/24, 7:15 PM

YYetzederixx Click to see attachment

Lord ZdOP•7/10/24, 7:20 PM

Im unsure how to replicate this with mysql

Yetzederixx•7/10/24, 7:34 PM

the cli for mysql and psql are very close have you tried?

Yetzederixx•7/10/24, 7:36 PM

unfortunatley I don't have mysql locally, or any remotes, to test this

Yetzederixx•7/10/24, 7:40 PM

it should work actually

https://dev.mysql.com/doc/refman/8.4/en/connecting-using-uri-or-key-value-pairs.html#connecting-using-uri

RaphaelEtim•7/11/24, 5:32 AM

can you please enable debugging to get more detailed logs.
https://www.prisma.io/docs/orm/prisma-client/debugging-and-troubleshooting/debugging#setting-the-debug-environment-variable

Debugging (Reference) | Prisma Documentation

This page explains how to enable debugging output for Prisma Client by setting the environment variable.

YYetzederixx the cli for mysql and psql are very close have you tried? `mysql "mysql://user:...

Lord ZdOP•7/11/24, 10:17 AM

Yeah thats what i did but it said it couldnt connect to the local mysql soc

RRaphaelEtim can you please enable debugging to get more detailed logs. https://www.prisma.io...

Lord ZdOP•7/11/24, 10:18 AM

Okay thanks ill try this today and put an update in here

Lord ZdOP•7/11/24, 2:02 PM

I added DEBUG="prisma*" to my enviroment variables and it didnt change the output of the log

RaphaelEtim•7/11/24, 2:24 PM

Can you please share the log here?

Lord ZdOP•7/11/24, 2:38 PM

Lord ZdOP•7/11/24, 2:45 PM

Ive had a call with AWS support and they have confirmed its not a problem on there end as I am able to connect to the database using heidisql

Lord ZdOP•7/11/24, 2:46 PM

From the research Ive been doing it seems like this is a common problem with deploying prisma to AWS however none of the fixes have worked for me

Lord ZdOP•7/11/24, 2:46 PM

Im going to try setting up an RDS proxy and see if that helps at all and will update with my findings

Yetzederixx•7/11/24, 2:55 PM

Since you can connect with something like dbeaver locally, or mysql/psql command line after ssh'ing into your server rig, and the credentials are gtg I'm at a loss here

Lord ZdOP•7/11/24, 2:56 PM

I had suspicions that it could be to do with root certificates but when I looked into theres no way Heidi would have access to the root cert and that works fine

Lord ZdOP•7/11/24, 2:58 PM

For this deployment RDS is not crucial so if need be I can just setup and host a mysql server but I was planning to upgrade it to high availability in a few months once I start onboarding customers so using RDS out the gate would make this planned upgrade a hell of alot easier

Yetzederixx•7/11/24, 2:59 PM

There really shouldn't be a valid reason why you can't connect from say an ec2 to rds though.

Lord ZdOP•7/11/24, 2:59 PM

I can connect to RDS from EC2 just not using prisma apparently

Lord ZdOP•7/11/24, 3:01 PM

All my testing with HeidiSQL has been using the EC2 instance as a ssh tunnel as the db isnt exposed to the internet

Yetzederixx•7/11/24, 3:02 PM

I mean, as much as I hate what I'm about to write, technically it is connecting... just having the connection request kicked back

Lord ZdOP•7/11/24, 3:02 PM

Well yeah your not wrong its finding the database server

Yetzederixx•7/11/24, 3:02 PM

Yeah, but that's fundamentally using a vpn

Lord ZdOP•7/11/24, 3:03 PM

Im gonna go try find the log from the db side to see if it has anyththing usefull

Lord ZdOP•7/11/24, 3:08 PM

Lord ZdOP•7/11/24, 3:10 PM

Lord ZdOP•7/11/24, 3:10 PM

Well that wasnt very insightfull

Yetzederixx•7/11/24, 3:11 PM

rarely is sadly

Lord ZdOP•7/11/24, 3:24 PM

Tried updating to latest prisma version but no luck gonna try RDS proxy now but I cant see that making a difference

Lord ZdOP•7/11/24, 3:32 PM

Ah apparently I cant use RDS proxy unless im in multiple AZs