You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
zerotier-cli: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
It appears that Debian 12 has libssl version 3 and not version 1.1. If I try to work around this by symlinking libssl.so.3 to libssl.so.1.1 I then I get:
zerotier-cli: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
As Debian 12 has been out for a while now, it would be nice if ZeroTier were compatible with its standard version of libssl.
Any steps to reproduce the error.
Install ZerotierOne on Debian 12(.7) and call zerotier-cli.
Any relevant console output or screenshots.
Console output as above.
What operating system and ZeroTier version. Please try the latest ZeroTier release.
I am using a fresh install of Debian 12.7 (Intel 64-bit). I installed ZerotierOne 1.14.1 using the recommended procedure (install GPG key then use apt).
The text was updated successfully, but these errors were encountered:
zerotier-cli should work on Debian 12.
zerotier-cli: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
It appears that Debian 12 has libssl version 3 and not version 1.1. If I try to work around this by symlinking libssl.so.3 to libssl.so.1.1 I then I get:
zerotier-cli: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
As Debian 12 has been out for a while now, it would be nice if ZeroTier were compatible with its standard version of libssl.
Install ZerotierOne on Debian 12(.7) and call zerotier-cli.
Console output as above.
I am using a fresh install of Debian 12.7 (Intel 64-bit). I installed ZerotierOne 1.14.1 using the recommended procedure (install GPG key then use apt).
The text was updated successfully, but these errors were encountered: