Prisma error with wasp 0.14.0
Hi everyone,
I have an issue with wasp 0.14.0 and building the docker image:
2025-11-18T13:39:07.867396909Z [inf] [server-builder 8/11] RUN npm install && cd .wasp/build/server && npm install
2025-11-18T13:39:07.869242083Z [inf] [server-builder 9/11] COPY db/schema.prisma .wasp/build/db/
2025-11-18T13:39:08.368385799Z [inf] [server-builder 9/11] COPY db/schema.prisma .wasp/build/db/
2025-11-18T13:39:08.371296265Z [inf] [server-builder 10/11] RUN cd .wasp/build/server && npx prisma generate --schema='../db/schema.prisma'
2025-11-18T13:39:09.503658394Z [inf] Error: Failed to fetch sha256 checksum at https://binaries.prisma.sh/all_commits/4bc8b6e1b66cb932731fb1bdbbc550d1e010de81/linux-musl-openssl-3.0.x/migration-engine.sha256. 500 Internal Server Error
----
Apparently the URL Prisma is using to download the engine checksum (https://binaries.prisma.sh/all_commits/4bc8b6e1b66cb932731fb1bdbbc550d1e010de81/linux-musl-openssl-3.0.x/migration-engine.sha256) now returns a 500 error from Prisma’s servers, which causes npx prisma generate to fail during the Docker build, even though my app code, Prisma version (4.16.2) and Wasp version (0.14.0) haven’t changed since the last time this project deployed successfully
5 Replies
Wohooo @Jorge, you just became a Waspeteer level 5!
Hi @Jorge. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but the knowledge sources provided do not contain information about the specific Prisma error you are encountering with Wasp 0.14.0—namely, the 500 Internal Server Error when fetching the migration engine checksum from Prisma’s servers during Docker build.
However, there are related issues in the knowledge sources about Prisma engine binary download problems and Docker builds, often linked to platform compatibility (e.g., OpenSSL versions) or changes in Prisma or Node.js versions. For example, previous issues have been caused by mismatches between the expected OpenSSL version and what is available in the Docker image, or by Prisma not supporting certain OpenSSL versions on Alpine Linux, which required workarounds like installing compatibility packages or updating Wasp/Prisma versions to resolve them. But none of the sources mention a 500 error from Prisma’s binary server or provide a solution for it in the context of Wasp 0.14.0 or Prisma 4.16.2.
Given this, I recommend checking Prisma’s status page or GitHub issues for any ongoing outages or changes to their binary hosting, as this appears to be a server-side issue outside of Wasp’s direct control. If the problem persists, you may want to open an issue on the Wasp GitHub repository with the details you provided.
If you need more targeted help, please provide additional context or check for updates from Prisma regarding their binary hosting infrastructure.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Jorge, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
This is related to Cloudflare being down: https://www.cloudflarestatus.com/
Nothing we can do expect wait for them to get back online 🙂
Cloudflare Status
Welcome to Cloudflare's home for real-time and historical data on system performance.
Wow you are right 😄 thanks a lot for your help
