Prisma cannot find the required `libssl` system library in your system. Please install openssl-3.0.x
Getting a new error on my deployments that I've not seen before
104 Replies
Project ID:
f0b123dd-49d4-4bfc-b063-9a5238f876efRailway
404 - Page not found
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
Confused because this didn't used to happen 
Same error using it with bun, looks like a few others have had this error too - doesn't seem to have a great solve
dang, i was deploying fine a few days ago, what changed?
I tried the various solutions in the different related threads (adding openssl to nixlibs), symlinking files, adding node,etc, no luck
I think my next step is to create a Dockerfile specifically? Although am gonna need to learn how to do this for my monorepo (turborepo) using npm running bun
i am in a very very similar boat, however with pnpm instead of npm.
i have a turborepo with one 'project' using bun, and i got that working before but now prisma is giving me the exact same error
same setup on my end, i have a turborepo, with one of my apps being a websocket server with bun
the other being a nextjs application
i use npm as package manager because bun doesn't fully support monorepos yet
and only recently had this issue before
Though I haven't encounter this issue yet, you should be able to temporary fix this by running the service via Dockerfile.
currently figuring out how to make one
I've used dockerfiles before but the part I'm trying to figure out here is how to best handle turborepo's filtering that's recommended
also if I need npm to install, but need bun to run, what's the best image to work off here
and also I think i'll need to make a dockerfile for this app specifically and adjust where railway is point to so it gets the right one
tbh, I never use turbo so I can't give you any feedback on that, but if possible, use the the alpine image. I was able to reduce my memory usage from 200 to around 70.
alpine image of node?
oh alpine linux
alpine - Official Image | Docker Hub
A minimal Docker image based on Alpine Linux with a complete package index and only 5 MB in size!
?
ye, the reducing will vary, but should be less than if you use nix.
awesome, ty
@Harris please let me know if you find a dockerfile that works
When did this start happening?
Previously I had it working on the 13th for sure
https://discord.com/channels/713503345364697088/1173859037612343368/1173871855631859712
I don’t know what changed but I only noticed it 2-3 days ago
couple days ago
What version of prisma are you using?
Can you trying adding a
railway.toml file with the contents
5.5.2
my current nixpacks.toml
should i make a railway.toml to go along with it?
We can try a few things to debug what is happening. First, can you try removing the
[phases.setup] sectionsure
I'm trying to reproduce using the latest version of prisma but am unable to. So I beleive it is a config error
i am on bun as well
building 👍
Can you please share the link
Railway
404 - Page not found
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
error because bun cant be found
oh right, you can add that section back. But not the archive bit
ok
building
Prisma cannot find the required 'libssl' system library in your system. Please install openssl-3.0.x and try again.
(same issue as before)yup interesting. Trying to reproduce with the same settings locally. In the meantime can you try this https://canary.discord.com/channels/713503345364697088/1175401667978604575/1176271639961419876
building
weirdly this time it tried to build prisma from the root and failed
that looks to have worked?
yes give me a second im testing something
yup working
thanks!!
cool. np! I'll take a look at why it is failing with the latest version
Hello friends, I am running into the same error. I've noticed since a few days
Also using bun and prisma 5.5.0, I had updated to 5.6.0 which was released a week ago and then I reverted back because I thought that this might be a Prisma error, but it's still hapenning on Prisma 5.5.0
ah I think the issue is with node 21 which is now added to nixpacks. I recommend specifying the node version you would like in the
package.json file.
If your specified version is something like > 18 then the latest version will be usedI tried this and it seems to have fixed it: https://discord.com/channels/713503345364697088/1175401667978604575/1176271639961419876
I believe it has also to do with the new node js version and the culprit does indeed seem to be nixpacks, because that's the only thing that probably changed in the last few days. I did not change anything in the codebase
Thanks a lot!
oh wait, what was the change?
Ah ok, so adding a railway.tomml to specify a nixpacks version fixes it?
Which solution is preferred? @L4TRIO suggests that it was fixed by specifying 1.17 for nixpack in the railway.toml as mentioned above, but is the node engine specification a better solution, or are both needed?
Does nixpacks adhear to the engine version in the package.json?
the solution jr proposed is a far better solution than pinning your nixpacks version
makes sense, will go ahead and try this
this saves me the time of trying to make a docker file to handle this weird case
so ty ❤️
just to clarify (i'm still learning js ecosystem stuff) is this engines field only used by npm?
setting my node engine to 18.x did not work
though I'd just simply put 18, not too sure why jr put 18.x
had to go back to the nixpacks version pinning
when you set your engines.node to 18, can you confirm that the build did in fact use node 18?
this would be printed in the build logs at the top in the build table
yup can confirm
currently building, will see result
publishing image
that seems to have worked for me
weird - only i thing i changed was removing the railway.toml file and pinning the version
I don't have a railway.toml
only the nixpacks.toml
previously the prisma error would only appear on server start, so I think it's gone on my end?
awesome, I see you have openssl in the setup, crscd, do you have openssl listed there?
this is my nixpacks.toml
i was told to remove the archive line
nixLibs under the start phase is not valid syntax and won't do anything, otherwise you're good
my nixpacks.toml
ah good to know
perhaps try adding nixLibs openssl?
can you add openssl as nixLibs under the setup phase like in the nixpacks.toml Harris shows?
haha exactly my thoughts
@Brody do you if there would be a way to have the latest bun version for the nixarchive? I think there's a bot that always pushes that latest version to docker images, but could there be something similar for nixarchives?
building
cause I think the archive is 1.0.11 but bun canary is .13
i think its because your archive is pinned? try removing that line
oh do I not need to specify it?
it would then default to a much older version
oh really?
yes, since internally nixpacks has a nixarchive that it will use by default
you are right, bun is version 1.0.13 right now, but nixpacks only has 1.0.12
https://github.com/NixOS/nixpkgs/commits/master/pkgs/development/web/bun/default.nix
the archive to use for 1.0.12 is
f53263caceb5f2a92eb2269e8eed9ef7a065fb7a (its just the commit id)
https://github.com/NixOS/nixpkgs/commit/f53263caceb5f2a92eb2269e8eed9ef7a065fb7agithub action to run
updateScript = writeShellScript "update-bun" '' on new bun commit 👀 ?this pr just needs to be merged and then nixpacks will have bun 1.0.13 https://github.com/NixOS/nixpkgs/pull/268524
once thats done you can grab the commit id in the same way i showed above
working!!
awsome
@jr adding openssl in nixLibs worked to fix this issue, perhaps auto adding openssl as a nixlib if the build uses bun?
yup good idea. It was likely this PR that broke things https://github.com/railwayapp/nixpacks/pull/986
great to know that adding it in this case fixed it. We can def add when using bun
thats for sure what broke it 🤣
time to add another test case!
kind of curious, what caused it to go 3 weeks unnoticed?
cause oct 16 -> nov 16th roughly
ohhh wait
was it this + the node 20 change?
causing it to trigger a few days ago
The PR was merged a few weeks ago, but nixpacks on Railway was only recently updated
yep github release does not always mean railway will use the latest release
phrased it weird, but just trying to learn 🙂 Nixpacks was developed by Railway, right?
why delete, that was a good question.
yes nixpacks was developed by railway, some other platforms use it too, but maybe most notably, hop.io uses it
forgot the exact wording of it now lol, but how big is Nixpacks outside of Railway? is it used by a ton of folks and so therefore it has a bit of a slower adoption by railway?
kind of seperation of concerns almost
yep developed by railway, used by others, dont know why railway doesnt use the latest version automatically
i wish railway let you deploy stuff on your own aws/gcp - would make my life a lot cheaper haha
they will at one point, though it would likely be limited to enterprise customers
aw
that's what PipeOps is for though
yeah im aware of the several alternatives however none are as nice to use as railway
so true
flightcontrol, easypanel, pipeops (just the ones that use nixpacks) all feel janky in one way or another
I agree, but you didn't hear me say that
coolify especially
i really want to love coolify but it’s just not there yet
hop is pretty good but i want to use my aws credits
I getcha
my struggles
the firstest of worlds
either way, happy this is fixed for the both of you!
thank you!
For me the error happened anywhere I invoked Prisma to add/modify data in the database