prisma: 403 when trying to download prisma engine

Bug description

calling https://binaries.prisma.sh/all_commits/06fc58a368dc7be9fbbbe894adf8d445d208c284/debian-openssl-3.0.x/schema-engine.gz.sha256

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

Most upvoted comments

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:

https://binaries.prisma.sh/all_commits/8047c96bbd92db98a2abc7c9323ce77c02c89dbc/debian-openssl-1.1.x/libquery_engine.so.node.sha256

😠 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

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.

#20021 (comment)

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:

$ prisma generate
Error: Failed to fetch sha256 checksum at https://binaries.prisma.sh/all_commits/11f085a2012c0f4778414c8db2651556ee0ef959/debian-openssl-1.1.x/libquery_engine.so.node.gz.sha256 - 403 Forbidden
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
Error: Process completed with exit code 1.

Edit: adding PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING=1 dont help.

$ cross-env PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING=1 prisma generate

Error: Failed to fetch the engine file at https://binaries.prisma.sh/all_commits/11f085a2012c0f4778414c8db2651556ee0ef959/debian-openssl-1.1.x/libquery_engine.so.node.gz - 403 Forbidden

Is CDN dead?

My meme submission: ā€œPartial outageā€

Image

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

Please fix it soon, I have an assignment for an interview, and they gave me 3 days to do i

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

# URL to monitor
$url = "https://binaries.prisma.sh/all_commits/8047c96bbd92db98a2abc7c9323ce77c02c89dbc/windows/query_engine.dll.node.sha256"

# Infinite loop to check the URL
while ($true) {
    try {
        # Attempt to get the HTTP response
        $response = Invoke-WebRequest -Uri $url -Method Head -ErrorAction Stop
        # If no exception, the request succeeded (not 403)
        $statusCode = $response.StatusCode
        Write-Host "URL is accessible! Status Code: $statusCode" -ForegroundColor Green
        [Console]::Beep(500, 1000)  # Beep at 500 Hz for 1000 ms (1 second)
        break  # Exit loop once accessible
    } catch {
        # Handle the exception
        if ($_.Exception -is [System.Net.WebException]) {
            $statusCode = [int]$_.Exception.Response.StatusCode
            if ($statusCode -eq 403) {
                Write-Host "Still getting 403 Forbidden. Checking again..." -ForegroundColor Yellow
            } else {
                Write-Host "Unexpected status code: $statusCode" -ForegroundColor Red
                [Console]::Beep(500, 1000)  # Optional: Beep for other unexpected statuses
                break
            }
        } else {
            Write-Host "Error checking URL: $_" -ForegroundColor Red
        }
    }

    # Wait for 30 seconds before next check
    Start-Sleep -Seconds 30
}

perfect lets add to their troubles with a DDOS attack

Do not forget to:

Image

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

who else is trying to deploy on a Friday???

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.x

please

please fix it!!

who knows maybe we’ll see a fireship video about this lol

Definitely someones Cursor agent going cd s3 and remove all the old builds

Investor demo in 4 hours and can’t deploy the hotfixes.

Se nem o prisma trabalha na sexta quem sou eu nƩ

Come on, guys. Come back to the office and work on the fix!

Oh we are here don’t you worry!

Lol imagine an ORM bringing down your whole CI pipeline. We can’t deploy a hotfix because of this

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

Yep, I’m the developer behind this masterpiece. AI told me Friday is the perfect day to deploy, so I listened — because what could possibly go wrong? We don’t waste time with staging or tests; production is our testing ground. If your CI pipelines are crying, just think of it as a free resilience drill. You’re welcome, world. šŸ˜ŽšŸ”„

@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?

Image

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

So it wasn’t my fault this time…?

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

const adapter = new PrismaPg({ connectionString: envSchema.DATABASE_URL });

const prisma = new PrismaClient({
  adapter,
  log,
  transactionOptions: {
    maxWait: 5000, // default: 2000
    timeout: 10000, // default: 5000
  },
});

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!!

Image

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

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=1 that 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…

šŸ”„ This issue is highly active. Reconsider commenting unless you have read all the comments and have something to add.

but mommmm i wanna be in the screenshotttt

Looking at the error, seems like the bucket storing this has a bad permission policy 😦

someone did commit n push n vent home on a friday

It’s been a pleasure to talk with you guys, until we meet on Prisma issue again.

🫔

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!

https://www.youtube.com/watch?v=dQw4w9WgXcQ

Can’t believe I still fell for it

Hi Prisma team,

I’m experiencing a persistent issue when trying to run npx prisma generate on a Windows environment. The client fails to download the required engines and throws the following error:

Error: Failed to fetch sha256 checksum at binaries.prisma.sh/all_commits/…/windows/query_engine.exe.sha256 - 403 Forbidden

This seems to be related to Prisma trying to fetch a binary that either doesn’t exist anymore or isn’t accessible due to permissions on your CDN.

This issue does not happen on my local Ubuntu development environment. However, it completely blocks deployment on Windows servers, even with all recommended env variables like PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING=1 or PRISMA_CLIENT_ENGINE_TYPE=binary.

I’ve followed all troubleshooting steps, cleared the cache, and even tried hardcoding binaryTargets in the schema.prisma, but nothing seems to work.

Please fix this as soon as possible — it’s affecting production deployments and seems to be a server-side issue on your end.

Thanks in advance.

any other requests, sir?

Let the AI agents deploy their changes, they said…

Why does prisma download this stuff at runtime? I would prefer prisma-engines to be versioned and downloaded from NPM (I trust npm much more than Prisma hosted CDN)

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

Image

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

Looks like it’s working again, update your dependency to the latest

lies and deceipt

Image

Good time to test Drizzle?

I was hoping to add PRISMA_ENGINES CHECKSUM IGNORE MISSING=1 and 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

just sitting here scrolling through memes up and down and don’t know what to do šŸ˜„

Idk about you but that’s literally what my job is

o chefe do @nurul3101 chegando com uma pizza no escritório daqui a pouco

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!

Works now!

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

Image

NOOOOOOO

same here `ai-toolkit-ui@0.1.0 update_db

npx prisma generate && npx prisma db push

Downloading Prisma engines for Node-API for windows [ ] 0%Error: Failed to fetch sha256 checksum at https://binaries.prisma.sh/all_commits/acc0b9dd43eb689cbd20c9470515d719db10d0b0/windows/query_engine.dll.node.gz.sha256 - 403 Forbidden

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)

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

@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 šŸ˜†

If there was a viable mirror, we could just set the PRISMA_ENGINES_MIRROR env

prisma/packages/fetch-engine/src/utils.ts

Line 68 in ae2f2e4

process.env.PRISMA_ENGINES_MIRROR || 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 prisma/prisma-engines

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_MIRROR env

https://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

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

Looks like everything in their AWS S3 bucket for binaries are gone after 2020-10-29 binaries.prisma.sh

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:

Downgrade Prisma:

npm install prisma@5.10.2 @prisma/client@5.10.2

Update schema.prisma:

generator client { provider = ā€œprisma-client-jsā€ binaryTargets = [ā€œnativeā€, ā€œdebian-openssl-3.0.xā€] }

Generate Prisma Client with both macOS and Linux binaries:

rm -rf node_modules/.prisma PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING=1 npx prisma generate

Make sure your build script copies the generated binaries:

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.

My boss tried to fired me until I told him that it was not my fault! 😢

I can give you a note if you need

Back ! It’s working again

Image

Failing for debian-openssl-3.0.x

debian-openssl-1.1.x too

Prisma 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

https://www.youtube.com/watch?v=dQw4w9WgXcQ

I love that we’re still doing this in 2025.

I was hoping to add PRISMA_ENGINES CHECKSUM IGNORE MISSING=1 and it would work 😦

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… šŸ˜…šŸ˜…šŸ˜…

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/

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

# URL to monitor
$url = "https://binaries.prisma.sh/all_commits/8047c96bbd92db98a2abc7c9323ce77c02c89dbc/windows/query_engine.dll.node.sha256"

# Infinite loop to check the URL
while ($true) {
    try {
        # Attempt to get the HTTP response
        $response = Invoke-WebRequest -Uri $url -Method Head -ErrorAction Stop
        # If no exception, the request succeeded (not 403)
        $statusCode = $response.StatusCode
        Write-Host "URL is accessible! Status Code: $statusCode" -ForegroundColor Green
        [Console]::Beep(500, 1000)  # Beep at 500 Hz for 1000 ms (1 second)
        break  # Exit loop once accessible
    } catch {
        # Handle the exception
        if ($_.Exception -is [System.Net.WebException]) {
            $statusCode = [int]$_.Exception.Response.StatusCode
            if ($statusCode -eq 403) {
                Write-Host "Still getting 403 Forbidden. Checking again..." -ForegroundColor Yellow
            } else {
                Write-Host "Unexpected status code: $statusCode" -ForegroundColor Red
                [Console]::Beep(500, 1000)  # Optional: Beep for other unexpected statuses
                break
            }
        } else {
            Write-Host "Error checking URL: $_" -ForegroundColor Red
        }
    }

    # Wait for 30 seconds before next check
    Start-Sleep -Seconds 30
}

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

@mmahalwy I was wondering the same thing, we moved to the new adapter method in order to avoid this exact dependency

Are you looking for a job? P.S.: Just kidding lol

use prisma they said, it is going to be fun… they said…

I still prefer it over Drizzle ORM šŸ¤·ā€ā™‚ļø

Cheers šŸ»

No SMS today

just sitting here scrolling through memes up and down and don’t know what to do šŸ˜„

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 Forbidden

Lol. 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 script formatfailed 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

> npx prisma generate --no-hints
Error: Failed to fetch sha256 checksum at https://binaries.prisma.sh/all_commits/acc0b9dd43eb689cbd20c9470515d719db10d0b0/debian-openssl-3.0.x/libquery_engine.so.node.gz.sha256 - 403 Forbidden
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
 ELIFECYCLE  Command failed with exit code 1.

This is not solved! My app is TOTALLY down for a couple of hours.

PrismaClientKnownRequestError: 
Invalid `prisma.candidate.findMany()` invocation:
This 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: Internal Server Error"}} (The request id was: 9614cd9fe4204fb3)

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.x now.

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 Prisma devs must return to office on monday

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.

prisma generate && prisma migrate deploy Error: Failed to fetch sha256 checksum at https://binaries.prisma.sh/all_commits/xxxxx/linux-musl-arm64-openssl-3.0.x/libquery_engine.so.node.gz.sha256 - 403 Forbidden 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

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.

Use prisma, they said, it’ll be fun… they said… šŸ˜…šŸ˜…šŸ˜…

Are you not having a blast reading through memes?

So it wasn’t my fault this time…?

Tell this to my 3 commits before i realised…

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!

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

const adapter = new PrismaPg({ connectionString: envSchema.DATABASE_URL });

const prisma = new PrismaClient({ adapter, log, transactionOptions: { maxWait: 5000, // default: 2000 timeout: 10000, // default: 5000 }, });

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

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. #20021 (comment)

Don’t do this in production! It could result in you having a hacked or vulnerable engine

I tried this and didn’t work for me at all.

Why does prisma download this stuff at runtime? I would prefer prisma-engines to 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

Image

Super Sextaaaaaa

+1

cheeeeeese XDDDD

@GorlikItsMe I wanna be in the screenshot

+1

Same here

> Downloading Prisma engines for Node-API for darwin-arm64 [                    ] 0%Error: Failed to fetch sha256 checksum at https://binaries.prisma.sh/all_commits/8047c96bbd92db98a2abc7c9323ce77c02c89dbc/darwin-arm64/libquery_engine.dylib.node.sha256 - 403 Forbidden