-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Error when filtering using referrer after update to 2.16.1 #3255
Comments
Seeing the same thing 👀 |
I also experienced this with v2.16.0 and am using v2.15.1 for now |
Same here, different query string tho: ⨯ Error [PrismaClientKnownRequestError]:
Invalid `prisma.$queryRawUnsafe()` invocation:
Raw query failed. Code: `1054`. Message: `Unknown column 'session.hostname' in 'where clause'`
at qn.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7315)
at qn.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6640)
at qn.request (/app/node_modules/@prisma/client/runtime/library.js:121:6347)
at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9616)
at async g (/app/.next/server/app/api/websites/[websiteId]/metrics/route.js:1:2515)
at async te.do (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:18:17826)
at async te.handle (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:18:22492)
at async doRender (/app/node_modules/next/dist/server/base-server.js:1455:42)
at async responseGenerator (/app/node_modules/next/dist/server/base-server.js:1814:28)
at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/next/dist/server/base-server.js:1824:28) {
code: 'P2010',
clientVersion: '6.1.0',
meta: [Object]
} |
I went ahead and backed out of 2.15.1 and it's working fine. |
harryo
added a commit
to harryo/umami
that referenced
this issue
Feb 27, 2025
harryo
added a commit
to harryo/umami
that referenced
this issue
Feb 27, 2025
harryo
added a commit
to harryo/umami
that referenced
this issue
Feb 27, 2025
Solved in #3278 |
mikecao
added a commit
that referenced
this issue
Feb 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
After updating Umami to version 2.16.1 using
docker compose pull
, attempting to filter data by referrer results in error, the UI displays "Something went wrong" and the server responds with a 500 Internal Server Error.Database
PostgreSQL
Relevant log output
Which Umami version are you using? (if relevant)
2.16.1
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
Docker
The text was updated successfully, but these errors were encountered: