Skip to main content ↑ ↓
Topic: Node: libcrypto.So.1.1: can't open shared object file (Read 375 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Node: libcrypto.So.1.1: can't open shared object file

I'm trying to run mcsmanager but then I get this out put from running node
Code: [Select]
❯ node app.js
node: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
I have tired using node before once a few weeks ago but still had the same issue but for a different node app

Code: [Select]
❯ sudo pacman -Syu
:: Synchronizing package databases...
 system is up to date
 world is up to date
 galaxy is up to date
 lib32 is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 universe is up to date
 DEB_Arch_Extra                                                      6.7 KiB  11.0 KiB/s 00:01 [########################################################] 100%
:: Starting full system upgrade...
warning: libreoffice-fresh: local (7.5.2.2-3) is newer than extra (7.5.2-1)
 there is nothing to do

Re: Node: libcrypto.So.1.1: can't open shared object file

Reply #1 –
Can you post the output of pacman -Qi nodejs and ldd $(which node)?
 

Re: Node: libcrypto.So.1.1: can't open shared object file

Reply #2 –
 
 Think I've seen this error recently. The error throws libcrypto.so 1.1 because there's no more of that but only libcrypto.so.3 because openssl that provide libcrypto.so was upgraded recently from version 1.x to 3.x. So you have to upgrade all packages in case you had an ignore package in ur pacman.conf. reinstall all packages/dependencies but don't forget to check if Artix repos are uncommented in your pacman.conf and in the right order Artix repos first Arch last