Prisma not connecting to external MySQL

[AlexNordic]

I’m trying to run a nodejs app with Prisma, that should connect to an external MySQL database. I have added Fly’s ipv4 ip to the allow list of the external host, but Prisma is not able to connect to it. I guess that’s the incoming ip.

The error is:

Can't reach database server at `77.x.x.x`:`3306` (ip redacted)

I’ve double checked all ip and they are all correct, I’m guessing that as stated here, I have no way to know what outgoing ip Fly is trying to use? (reference: Connect GCP MYSQL to fly not working - #5 by greg). Is that the case, or is it something different that I should change?

[greg]

Hi,

Ah, yep, it sounds like you are running into that mentioned issue:

Connect GCP MYSQL to fly not working

@soloski123 Hi, It sounds like you have run into the problem I mentioned. You don’t know what outgoing IP Fly will use to connect to your database (the IP Fly shows you in its UI/CLI is the incoming one - the one you set e.g for your DNS to point to it). And so the connection is refused.

You can’t whitelist an IP address in an external database’s firewall (such as AWS RDS or GCP CloudSQL) since you won’t know what it will be.

If your database is in GCP, you could use their Cloud proxy to get around the issue. If it’s in Fly, of course it’s not an issue. But if it’s e.g AWS RDS … not sure. Someone may have an idea in one of the threads about this e.g

Set/get outgoing IP address for whitelisting on external APIs/Hosts

Hi there, I don’t think this is something that Fly currently does, but is there any way to set an IP address (or a list/range) that a fly app will use to make requests to external hosts? I’d really like to be able to reliably whitelist Fly apps by IP/list/range/whatever. I run reverse proxies, and occasionally one or more Fly IPs will get blacklisted by an external host. Since some requests go out through different Fly IP addresses to the external host, we get an intermittent “sometimes it mak…