500 Internal Server Error from Pulse console setup
I am trying to configure Pulse for my existing Prisma project, but when I put in my details and hit "Enable Pulse" from the
console.prisma.io/PROJECTID/pulse/setup I get a 500 Internal Server Error every time, despite Prisma Pulse being up according to the status site here https://www.prisma-status.com/.
I'm not sure what other information you'd need to diagnose this, so let me know if you need more than the following:
- Request that's failing: https://console.prisma.io/PROJECTID/pulse/setup?_data=routes%2F_app.%24organizationId_.%24projectId_.%24environmentId.pulse.setup
- My database is Vercel Postgres databasePrisma Data Platform Status
Welcome to Prisma Data Platform's home for real-time and historical data on system performance.
4 Replies
Database connection string is not currently supporting public connections.
This definitely should not cause Prisma Pulse to display a 500 Internal Server Error in my opinion; instead it should be telling me that connecting with the connection string failed. Hopefully this can be handled properly soon for the next people who invitably come across this!Hey @Josiah
If I understand correctly, this was caused because your database was not publicly accessible, right? If you make your database public the error goes away?
And yes, the console should never throw a 500 Console error, I'll report this to the team and we will sort it out. Thanks for reporting 🙏
Yes, I believe so. I'm using Vercel Postgres though, so I wasn't able to actually fix the issue and confirm. I have moved to a different technology instead of Pulse for that reason
We have fixed the 500 Console error that you reported. It would be great if you could try it out.
The requirement to have publicly accessible database is temporary, we are working on adding Static IPs to Pulse, which should allow using Pulse with Private Databases as well.