libssl.so.1.1: cannot open shared object file: No such file or directory

[cyrus01337]

When running Rojo v7.2.1 from the Visual Studio Code extension, I receive the following on Kubuntu 22.04:

/home/cyrus/.config/Code/User/globalStorage/evaera.vscode-rojo/rojo-v7.2.1: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

A number of options appear when searching for libssl through apt (shown below), is there any specific library/package of choice that's recommended for Rojo?

[cyrus01337]

Update/Note: installing libssl3/libssl-dev/both does not resolve this.

[LPGhatguy]

Hello, thanks for the report!

I think I see the issue here. Rojo 7.2.1 is looking for OpenSSL 1.1, which comes installed on Ubuntu 18.04 LTS machines where we build releases. However, your system (and package manager) seem to come with OpenSSL 3.0, which doesn't seem to get loaded.

We downgraded our CI machines in #561 on June 26th. 7.2.0 was the first release to go live with this change.

If you downgrade to Rojo 7.1.1, does this still happen? I'm not sure if older versions link against a newer OpenSSL or not.

[LPGhatguy]

As an alternative workaround, you might be able to install OpenSSL 1.1 on your system: https://askubuntu.com/a/1407024

[Kampfkarren]

Long term Rojo should be using rustls. From some searching around in Cargo.lock, it looks like its only reqwest, which uses OpenSSL by default. This could be fixed by turning off default features and flipping on rustls-tls.

[cyrus01337]

I attempted to downgrade the version of Rojo that the extension uses via the target version setting to no avail:

There was also an attempt at installing OpenSSL v1.1 with the resource sent which failed with the given errors.

Are there any other options?

[LPGhatguy]

It looks like the way to link OpenSSL statically changed at some point, from setting an environment variable to the optional feature native-tls-vendored on reqwest. I think this might be a better approach than trying to jump ship to rustls just yet.

Once the builds are up, you should try out this release: https://github.com/rojo-rbx/rojo/releases/tag/v7.2.1-static-openssl

It should work on systems that have a mismatched OpenSSL version or even no OpenSSL at all.

[LPGhatguy]

Nevermind. It looks like downgrading the build machines means that Foreman (and proabably Wally) no longer runs on them, a knock-on effect of #561.

[cyrus01337]

@LPGhatguy When waiting for the builds, are you referring to all builds or strictly Windows?

[Boegie19]

@cyrus01337 Seems like the release action broke made a pull request to fix it if you want to do it before that you would have to build from source or use a fork.

[LPGhatguy]

I bumped the minimum version of Ubuntu from 18.04 to 20.04 and restarted builds for the static OpenSSL build. It looks like the Linux build succeeded this time around:

https://github.com/rojo-rbx/rojo/releases/tag/v7.2.1-static-openssl

[cyrus01337]

Have had some woes with Grapejuice working so testing this has taken some time. Apologies in advance, will get results out soon as.

[cyrus01337]

It has been a month, the version works as expected. :)

The latest version also did not fix this issue in case this ever comes up.