https://www.prisma.io/ logo
Join Slack
Powered by
Having an issue with prisma on a new laptop ubuntu...
# orm-help
k
Having an issue with prisma on a new laptop ubuntu 22.04
Copy code
Error: Get Config: Unable to establish a connection to query-engine-node-api library. It seems there is a problem with your OpenSSL installation!
Details: Unable to require(`/home/kay/checkpoint/nft-api/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node`)
 libssl.so.1.1: cannot open shared object file: No such file or directory

Prisma CLI Version : 4.0.0
Copy code
whereis node
node: /home/kay/.nvm/versions/node/v16.16.0/bin/node
Copy code
whereis openssl
openssl: /usr/bin/openssl /home/linuxbrew/.linuxbrew/bin/openssl /usr/share/man/man1/openssl.1ssl.gz
any ideas?
👀 1
n
Hey 👋 Did you try specifying 
binaryTargets
in the generator block? You could specify binaryTarget as 
debian-openssl-1.1.x
Copy code
generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native","debian-openssl-1.1.x"]
}
k
Hi
Let me try that
Btw i just started a discussion here -https://github.com/prisma/prisma/discussions/14356
with more details
Setting the binary did not work
Copy code
binaryTargets = ["native","debian-openssl-1.1.x"]
n
I see you have commented on this related GitHub Issue, just to confirm this solution didn’t work for you, right?
k
It did work but i could only get that working temporarily
i dont know if thats the correct solution
There are so many posts about thiso n github with different answers, some saying the message is even misleading
i didint want to go and alter my path, if i didint have to because im not familiar with doing that
n
How are you installing node in your system?
If you are using snap to install node or openssl it might cause an issue as described here. Could you try installing openssl with 
apt
as mentioned in the comment?
k
Im not using snap
I am using nvm
n
Could you try using fnm or apt to install node version and see if it works in that case? It’s an alternative to nvm and it seems to be working when node is installed through these tools.
k
The solutions presented were to use a manager like nvm
your suggestion does not work
If you read my discussion - https://github.com/prisma/prisma/discussions/14356 you can see this problem specifically is with the openssl version installed
but looking at this issue already created
its a false positive and not really about openssl
it has nothing to do with my node installation
A lot of different solutions to the same probem it seems because of a bad error message? i dont know
n
That’s strange, I asked my colleague and it seemed to work for them 🤔
k
Well what environment are they using
I want to say if you installed ubuntu 22.04, nvm - node version 16 and then any prisma sample nodejs application. You will recreate this issue
The main thing here is having ubuntu 22.04
n
Thank you for pointing to the GitHub Issue, it indeed is reported by our engineering team mate and they are tackling it in this sprint
9 Views
Open in Slack
PreviousNext
Powered by