Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #3181] [BUG]: Incompatible Prisma Client versions - Debian #2045

New Issue
Closed
opened 2026-02-22 18:27:53 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:27:53 -05:00
Owner
Copy Link
Copy Source

Originally created by @bobo-byte on GitHub (Feb 12, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3181

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

Observed: Attempt to create a new workspace failed, with the following error:

Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "debian-openssl-1.1.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "debian-openssl-1.1.x". Add "debian-openssl-1.1.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-1.1.x"] } The following locations have been searched: /tmp/.mount_Anythie17Uvh/resources/backend/node_modules/.prisma/client /tmp/.mount_Anythie17Uvh/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_Anythie17Uvh/resources/backend/prisma

Expected: Workspace to be created.

Release version: v1.7.3-r2

System: Ubuntu 24.04.2 LTS

Are there known steps to reproduce?

No response

Originally created by @bobo-byte on GitHub (Feb 12, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3181 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? Observed: Attempt to create a new workspace failed, with the following error: ``` Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "debian-openssl-1.1.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "debian-openssl-1.1.x". Add "debian-openssl-1.1.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-1.1.x"] } The following locations have been searched: /tmp/.mount_Anythie17Uvh/resources/backend/node_modules/.prisma/client /tmp/.mount_Anythie17Uvh/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_Anythie17Uvh/resources/backend/prisma ``` Expected: Workspace to be created. Release version: v1.7.3-r2 System: Ubuntu 24.04.2 LTS ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:27:53 -05:00
yindo closed this issue 2026-02-22 18:27:54 -05:00
yindo commented 2026-02-22 18:27:54 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 12, 2025):

If you open the application contents (not your storage) and edit resources/backend/prisma/schema.prisma and edit the top of the file to

generator client {
  provider = "prisma-client-js"
  binaryTargets = ["debian-openssl-1.1.x"]
}

It will resolve the file on boot. We likely wont pre-include every distribution into the build since this since the special native prisma binary target is the default - which means it must have had some issue during detection on your OS.

Note: The native binary target is the default. You can set it explicitly if you wish to include additional binary targets for deployment to different environments.

@timothycarambat commented on GitHub (Feb 12, 2025): If you open the application contents (not your storage) and edit `resources/backend/prisma/schema.prisma` and edit the top of the file to ``` generator client { provider = "prisma-client-js" binaryTargets = ["debian-openssl-1.1.x"] } ``` It will resolve the file on boot. We likely wont pre-include every distribution into the build since this since the special `native` prisma binary target is the default - which means it must have had some issue during detection on your OS. > Note: The native binary target is the default. You can set it explicitly if you wish to include additional [binary targets](https://www.prisma.io/docs/orm/reference/prisma-schema-reference#binarytargets-options) for deployment to different environments.
yindo changed title from [BUG]: Incompatible Prisma Client versions - Debian to [GH-ISSUE #3181] [BUG]: Incompatible Prisma Client versions - Debian 2026-06-05 14:44:13 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2045
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?