Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically logging out and making database go down after migration from 2.13.2 to 2.17 #3297

Open
DarkAbhi opened this issue Mar 10, 2025 · 3 comments

Comments

@DarkAbhi
Copy link

Describe the Bug

Database - Supabase postgres

Everything was working fine before migration

Error that pops up after migrating and opening umami last visited site.
Image
Error logs on vercel console
Image
Video showcasing error fetching info on umami
https://github.com/user-attachments/assets/d22257be-084b-46c4-abf8-4eca5ef20423

Database

PostgreSQL

Relevant log output

⨯ Error [PrismaClientInitializationError]: 
Invalid `prisma.user.findUnique()` invocation:


Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`

Please make sure your database server is running at `aws-0-ap-south-1.pooler.supabase.com:5432`.
    at qn.handleRequestError (/var/task/node_modules/@prisma/client/runtime/library.js:121:7615)
    at qn.handleAndLogRequestError (/var/task/node_modules/@prisma/client/runtime/library.js:121:6640)
    at qn.request (/var/task/node_modules/@prisma/client/runtime/library.js:121:6347)
    at async l (/var/task/node_modules/@prisma/client/runtime/library.js:130:9616)
    at async g (/var/task/.next/server/app/api/websites/[websiteId]/metrics/route.js:1:5693)
    at async c (/var/task/.next/server/app/api/websites/[websiteId]/metrics/route.js:1:9078)
    at async g (/var/task/.next/server/app/api/websites/[websiteId]/metrics/route.js:1:2016)
    at async te.do (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:18:17826)
    at async te.handle (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:18:22492)
    at async eB (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:2871:21083) {
  clientVersion: '6.1.0',
  errorCode: undefined
}

Which Umami version are you using? (if relevant)

2.17

Which browser are you using? (if relevant)

Chrome

How are you deploying your application? (if relevant)

Vercel

@L1H0n9Jun
Copy link

Migrating Supabase to Vercel's Neon doesn't seem to have this issue.
But it should be a problem introduced by the Umami update.

@DarkAbhi
Copy link
Author

@L1H0n9Jun True, I gave up and migrated all my projects to neon for the time being.

@mikecao
Copy link
Collaborator

mikecao commented Mar 14, 2025

We use Prisma for database connections. You can try searching their issues too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants