prisma: 403 when trying to download prisma engine
Bug description
and getting 403 error
Severity
šØ Critical: Unable to run new builds
Reproduction
curl --location 'https://binaries.prisma.sh/all_commits/06fc58a368dc7be9fbbbe894adf8d445d208c284/debian-openssl-3.0.x/schema-engine.gz.sha256'
Expected vs. Actual Behavior
expected 200 but getting 403
Frequency
Consistently reproducible
Does this occur in development or production?
All envs
Workaround
No workaround
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 365
- Comments: 362 (11 by maintainers)
Commits related to this issue
- there is why the 'do not deploy on fridays' rule exists: https://github.com/prisma/prisma/issues/27700 — committed to alexanderbrv/customer-management-api by alexanderbrv a year ago
Who is here!? respond with the reaction!
š Iām a developer at work impacted by it š Iām a developer at school impacted by it š Iām devops, and my team is impacted by it š Iām here for media reasons ā¤ļø Iām here for the lulz š other reason
We are aware of the issue and are working on fixing this ASAP š
Folks this should be fixed now! Thank you for your patience while we worked on this.
We are working on this.Apologies for inconvenience, Iāll inform as soon as itās resolved.
use prisma they said, it is going to be fun⦠they saidā¦
Divided by countries, united by Prisma outages. Developers assemble! š»ā”
i am impressed with github issues realtime updates⦠props to whichever developer built this!
To provide additional context for the incident: We use R2 for storing query engine binaries which has a DNS failover to duplicates stored in S3. The failover triggered this evening and it seems there was an authorization issue preventing binaries from being downloaded.
We have overridden the failover which is why binaries downloads are now working and will run a postmortem to understand and fix the authorization. š
Works now! Darwin,
prisma 6.3.0ā Also getting this error in CI (Render.com), local US-based ISP, and various VPN endpoints.
Example:
š prisma friday deploy broke my friday deploy plans
Whilst all these cracked devs are assembled here I would like to announce that we are hiring cracked UK-based devs at Lawhive - referral link here: https://jobs.ashbyhq.com/lawhive?utm_source=Mj9QYeR36P
Thank goodness the SEO on this thread is already up to date!
Ill be honest who ever has the best meme might get some swag or something. These are hilarious. Thanks for being understanding everyone. We will update ASAP. The team is all hands on deck working on a solution.
We continue to work on resolving the issue, you can also find the latest status on https://www.prisma-status.com
Donāt do this in production! It could result in you having a hacked or vulnerable engine
who else is trying to deploy on a Friday???
I have simillar issue, but with diffrent URL:
Edit: adding
PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING=1dont help.Is CDN dead?
My meme submission: āPartial outageā
Tomorrow @codediodeio (Fireship) will make video about it. Say everyone cheese šø
How backend development gaslit me into thinking this was again another one of my faults for the past hour
Well, lets open a beer and wait š„ Its friday, my friends
#prayforprisma
Stop complaining and come here to the war room to help
Lol imagine an ORM bringing down your whole CI pipeline. We canāt deploy a hotfix because of this
https://www.instagram.com/reel/DMQvsAgvJ06/?igsh=MWJramhhcmR0bml1OA==
perfect lets add to their troubles with a DDOS attack
Do not forget to:
I really need a prisma dev to come in and say āworks on my machineā and leave
How to I tell to the CEO that the whole pipeline is down because of prisma
Thanks for being a great community everyone! Iāll miss the memes!
Itās been a pleasure to talk with you guys, until we meet on Prisma issue again.
just sitting here scrolling through memes up and down and donāt know what to do š
TEMP FIX:
Had this also and had to run the migration manually (
npx prisma migrate deploy), you can also add PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING env var.https://github.com/prisma/prisma/issues/20021#issuecomment-1680234475
apparently, everyone here
Sextou amigos šššš
good opportunity to look into drizzle
The only thing worse than a prisma is a broken prisma. rip Friday devs
F to pay respects
guys, office party on second floor when ci passes! ššš
Failing for
debian-openssl-3.0.xplease
please fix it!!
who knows maybe weāll see a fireship video about this lol
Definitely someones Cursor agent going
cd s3and remove all the old buildsInvestor demo in 4 hours and canāt deploy the hotfixes.
Se nem o prisma trabalha na sexta quem sou eu nƩ
Oh we are here donāt you worry!
Junior Dev pushed a critical bug to production that brought down all of our async workers⦠and now we canāt fix them because Prisma
@prisma-ai-developer You made an account just for this huh? I guess what else better do we have to do until itās fixed?
Iāll just wait for the fireship video š
se eu for demitido pq escolhi o prisma como ORM e meu chefe viu o github actions vermelho em plena sexta, vou ficar bem puto
send me the war room link to join pls
Tell this to my 3 commits before i realisedā¦
So it wasnāt my fault this timeā¦?
On a serious note though, why are we affected by this? We updated to use the pg adapter so we donāt use these binaries anymore
SE O PRISMA FAZ DEPLOY NA SEXTA PQ NOIS N PODE?
Looks like they are working on it. https://x.com/MarcHessDev/status/1946280102431486152
my $100M pre-revenue AI wrapper calorie calculator app lives for another day. Cheers!!
Just wait until they figure it out!! Letās be nice!!
https://www.prisma-status.com/
All Prisma devs must return to office on monday
https://www.youtube.com/watch?v=dQw4w9WgXcQ
Yikes. This is why you donāt release a javascript package with dependencies on a centrally hosted collection of pre-built binaries, kids. Single point of failure for one of the most popular DB libraries is a recipe for a bad time.
o chefe do @nurul3101 chegando com uma pizza no escritório daqui a pouco
make prisma functional again
fixed by prisma team.
cause: Unknown - we know that their binaries bucket was missing all binaries since 2020
Everyone can remove the
PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING=1that did nothing and get back to work š«”This board update faster than my discord chat šš¤£
Seems like the issue is fixed, it works for me now!
Seriously, these binaries need to be hosted somewhere else or packaged on npm. I am not letting my ability to deploy production, respond to security incidents, or revert critical bugs be completely blocked by some sketchy third party CDN hostingā¦
but mommmm i wanna be in the screenshotttt
someone did commit n push n vent home on a friday
š«”
It is already working! Thanks to my CTO! š LETS GOOOOOOOOOOOOOOO!
Looks like itās working again, update your dependency to the latest
hi fireship community!
Canāt believe I still fell for it
any other requests, sir?
Let the AI agents deploy their changes, they saidā¦
Hopefully from now on they wonāt do this anymore
@tavoyne On it! Prisma Accelerate should also be back up very shortly. We have identified what is preventing the issue to be fully resolved for Accelerate.
{ āstatusā: āerrorā, āmessageā: ā\nInvalid
prisma.diagnosticCentre.findUnique()invocation:\n\n\nThis request could not be understood by the server: {"type":"UnknownJsonError","body":{"code":"P6008","message":"Accelerate was not able to connect to your database. The underlying error is: Engine did not respond in time."}} (The request id was: 9614049ec9565d68)ā }Please look into prisma posgres
Can confirm. Our hotfix built and deployed!
My boss tried to fired me until I told him that it was not my fault! š¢
prisma broke my heart more than anything did
lies and deceipt
Good time to test Drizzle?
I was hoping to add
PRISMA_ENGINES CHECKSUM IGNORE MISSING=1and it would work š¦time to touch grass
might be a good time to go for a walk
this is now my new favorite chatting app
MAPA
Make Available Prisma Again
Idk about you but thatās literally what my job is
i can bring drinks!
i love prisma
Iām the QA waiting for the deployment to test and open a bug on Friday night
Come on, guys. Come back to the office and work on the fix!
It might depend on which binary your build is trying to access, because mine definitely isnāt working.
Please donāt make me go back to typeorm
NOOOOOOO
this worked for me: https://www.youtube.com/watch?v=35XFAkwmU4c
same here `ai-toolkit-ui@0.1.0 update_db
If you need to ignore this error (e.g. in an offline environment), set the PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING environment variable to a truthy value. Example: PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING=1`
On a serious note, the CDN is not down. looks like just some paths were deleted. You can enumerate the other available paths here: https://binaries.prisma.sh/
wen fix sir (jk)
@mmahalwy I was wondering the same thing, we moved to the new adapter method in order to avoid this exact dependency
I canāt believe so many people are using Prisma and deploying at the same time lol
I need save this memes for my monday daily to tell what happend š
thanks, but itās better to stay here and follow the comments
If there was a viable mirror, we could just set the
PRISMA_ENGINES_MIRRORenvhttps://github.com/prisma/prisma/blob/ae2f2e4617405e217c219af6b52176c1d6c811f5/packages/fetch-engine/src/utils.ts#L68
If you search GitHub there are a few semi-sketchy ones, looking to see how much work it is to build the prisma engines manually https://github.com/prisma/prisma-engines
+1
F
I was there when prisma went down
Can Prisma team please get their act together? Our engineering team is blocked on releasing any backend changes and we like to work on Fridays.
Please fix it soon, I have an assignment for an interview, and they gave me 3 days to do i
+3, Iāll let you know if I find any more coworkers who are stuck because of this
accidentally purged new builds instead of old ones š
On this day, I was here as well.
Now I have to get to work š
WORKAROUND: Fix Prisma CDN 403 Errors on Render (Mac + Linux)
If youāre getting this error when deploying to Render:
Failed to fetch the engine file at ā¦/debian-openssl-3.0.x/⦠- 403 Forbidden
Hereās what worked for us:
npm install prisma@5.10.2 @prisma/client@5.10.2
generator client { provider = āprisma-client-jsā binaryTargets = [ānativeā, ādebian-openssl-3.0.xā] }
rm -rf node_modules/.prisma PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING=1 npx prisma generate
cp -r prisma dist/ cp -r src/generated/prisma dist/src/generated/prisma/
This ensures both darwin and debian binaries are included and fixes the deployment error on Render.
I can give you a note if you need
Back ! Itās working again
debian-openssl-1.1.xtooPrisma is having problems āConnection errors to databases and Prisma ORM engine binariesā
You can check it here: https://www.prisma-status.com/
Hi Mom, Iām on The Code Report from Fireship!
Hello Friday deployers
I love that weāre still doing this in 2025.
the only way out is to pray
Thatās the most exciting friday of this year š
It seems like a simple issue with S3 access to files. I think Iāll download the binaries later and self-host.
whatās up guys
I panic thought I did something stupidā¦
Use prisma, they said, itāll be fun⦠they saidā¦ š š š
Yes, someone checked and you can use version from year 2020 or something
seriously, why there shouldnāt be alternative cdn with github or something
Are you looking for a job? P.S.: Just kidding lol
I still prefer it over Drizzle ORM š¤·āāļø
Cheers š»
No SMS today
thats essentially all of us š
even ignore checksum with PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING=1 as workaround not help.
engine binary also gone.
Error: Failed to fetch the engine file at https://binaries.prisma.sh/all_commits/acc0b9dd43eb689cbd20c9470515d719db10d0b0/debian-openssl-3.0.x/libquery_engine.so.node.gz - 403 ForbiddenLol. This is hilarious. Iāve been facing the exact same issue for about an hour now, and I was starting to think I had messed something up. I tried all sorts of thingsādowngrading to an even older version, removing queryCompiler, deleting prisma.config.tsābut nothing worked. I was actually in the middle of writing up an issue when I saw this one pop up, so I gave up on raising mine.
Iām in South Korea, and itās 4 AM on a Saturday now. What a fun surprise.
npm error Error: Failed to fetch sha256 checksum at https://binaries.prisma.sh/all_commits/8047c96bbd92db98a2abc7c9323ce77c02c89dbc/windows/query_engine.dll.node.sha256 - 403 Forbidden npm error npm error If you need to ignore this error (e.g. in an offline environment), set the PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING environment variable to a truthy value. npm error Example: PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING=1 npm error npm error Lifecycle scriptformatfailed with error: npm error npm error code 1 npm error npm error path C:\Users\Sunny\Desktop\VENDIT\CodeBase\vcms-universe\packages\planet npm error npm error workspace @vcms-io/planet@0.1.0 npm error npm error location C:\Users\Sunny\Desktop\VENDIT\CodeBase\vcms-universe\packages\planet npm error npm error command failed npm error npm error command C:\WINDOWS\system32\cmd.exe /d /s /c concurrently --raw "biome check --write" "prisma format"trying to push a hotfix so i dont get smited by ratelimits š having an amazing time prisma!
Looking at the error, seems like the bucket storing this has a bad permission policy š¦
Seeing the same issue as well
This is not solved! My app is TOTALLY down for a couple of hours.
Please they should also check prisma-postgres, it is not working
Great, it started to work right after I cancelled my plans
it worked finally
posting just to leave my mark in this historical chat
Can confirm itās working on
linux-musl-openssl-3.0.xnow.Bye guys
thats how long it takes to recompile all binaries and upload to the bucket
debian-openssl-3.0.x worked now on latest version
Iām just bootstraping a project with this ORM, i feel bad for everyoneās critical deployments xD
Its friday, friday, gotta bring prisma down on fridayyyyyyyyyyy. Everyone is looking forward to the weekend
Itās calm
I donāt see why a missing file in aws s3 is related to a database
All of them must be running to the office right now!
will spend the rest of my day migrating to Typeorm
Great opportunity to look at Prisma alternatives š¶āš«ļø
@halkony Fireship:
Prisma - In 60 seconds,
An ORM ⦠403 Forbidden.
Getting the same error! Everything was fine hours ago and then spent most of my hours try to figure this out, thought Iām losing my mind! šµ
Well Iāve tried to do a speculative fix to my app and now I canāt revert because of this. Oh no.
Are you not having a blast reading through memes?
Only 3? Suddenly I think I took too long to realize. I blamed the host. š
*sigh āOvertime request submitted.ā
Ah, nice to see a big thread here with people who have the same issue. šš PRISMA HEEEELP
Fridays my beloved!
I was wondering similar! Weāre using the Neon Adapter⦠so we shouldnāt need the binary, right? If I use ENV to disable binary download that breaks it in a different way.
Prisma not you !
same error here
I tried this and didnāt work for me at all.
Why does prisma download this stuff at runtime? I would prefer
prisma-enginesto be versioned and downloaded from NPM (I trust npm much more than Prisma hosted CDN)I was like panicking, like why the hell are my migrations failing š
I believe in you guys
Fridayzzz
Permissions issue when attempting to download the Prisma engine binariesā¦
So, uh, howās that TypeScript rewrite coming along, guys? š
Guess I chose a bad time to start a new project with prisma
Super Sextaaaaaa
+1
cheeeeeese XDDDD
@GorlikItsMe I wanna be in the screenshot
+1
Same here