Hey all 🙂 I’m trying to get my Prisma server up, but I’m having some trouble. The DB is AWS Aurora, and I’m hosting the server on Zeit Now. I’ve been using the new guide for deploying to Zeit Now (https://www.prisma.io/docs/tutorials/deploy-prisma-servers/zeit-now-and-google-cloud-sql-mohj5eiwot#1.-mysql), but even though the deploy is succesful, it can’t reach my DB for some reason. I get an output like this:

> Successfully built 086ddb645f20
> Successfully tagged registry.now.systems/now/8c565a120ef9e162cfb024f678f1e2411044ae28:latest
> ▲ Storing image
> Build completed
> Verifying instantiation in bru1
> [0]   at com.zaxxer.hikari.pool.HikariPool.createTimeoutException(HikariPool.java:548)
> [0] Exception in thread "main" java.sql.SQLTransientConnectionException: database - Connection is not available, request timed out after 5000ms.
> [0]   at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:83)
> [0]   at slick.jdbc.hikaricp.HikariCPJdbcDataSource.createConnection(HikariCPJdbcDataSource.scala:14)
> [0]   at slick.jdbc.JdbcBackend$BaseSession.<init>(JdbcBackend.scala:453)
> [0]   at slick.jdbc.JdbcBackend$DatabaseDef.createSession(JdbcBackend.scala:46)
> [0]   at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:145)
> [0] Exception in thread "main" java.sql.SQLTransientConnectionException: database - Connection is not available, request timed out after 5001ms.

I triple-checked the credentials and host, and I’m able to connect to the DB just fine using MySQL Workbench with the same credentials, which to me indicates that the credentials and host URL/port is fine, and that the DB accepts outside connections just fine as well. Any ideas / help would be much appreciated. 😄

I came here with the exact same issue. I used a Google Cloud DB but get the same results. I can even navigate to my now.sh site and it opens the playground but I get a "Server cannot be reached" error.

The GQL server (showing the playground) and the Prisma server are separate issues. Can you access your Prisma server? Perhaps at the

management

endpoint?

I'm not sure what you mean. There shouldn't be anything to see on the Prisma side being that we are using now.sh to host correct?

ah yes. thanks for the clarification. I am able to hit the management endpoint and look into the schema

And doing

now ls

shows the deployment has 0 instances, most likely because it cannot connect

so maybe a slightly different issue then

Then the issue is separate 🙂 You probably haven’t pointed your GQL server to the correct Prisma server

would you mind pointing me to some example of how that should be setup?

Go to your

prisma.yml

in your GQL server project and make sure the endpoint is corrrect. Then run prisma deploy

I think that should be correct. I setup a now alias for it so it would remain the same

Then IDK, I haven’t gotten that far yet 😉

and the endpoint reflects the endpoint alias

I’m using Amazon Aurora, so the setup is a bit different I think 🙂

oh ok. just thought I would mention it 🙂

Sure, thank you for trying! ❤️

@halborg: i think @Gabe is spot on with this comment. The RDS wizard on AWS is very confusing. When you create a database and make it publicly available, they still create a restriction that only your current IP can access the database.

It would seem that it did have something to so with it. I’ve chronicelled my explorations here: https://www.prisma.io/forum/t/unable-to-connect-to-aurora-db-through-zeit-now-hosted-docker-prisma-server/4134/3