Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
o0Ignition0o opened this issue Feb 16, 2023 · 2 comments · Fixed by #2689
Closed

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

o0Ignition0o opened this issue Feb 16, 2023 · 2 comments · Fixed by #2689
Assignees
@Geal

Comments

@o0Ignition0o
Copy link
Contributor

This pinned issue shows you how to work around a temporary openssl related issue.
Ubuntu 22.XX doesn't provide libssl@1.1 anymore. The router will fail to start and show this error:

error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

This happens because ubuntu only ships libssl 3.X:

$ openssl version
OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)

A known workaround is to manually install libssl 1.1 as explained in this stackoverflow issue by following the steps outlined in the answer.

We will keep this issue open for discoverability purposes, until we completely move to rustls.
@o0Ignition0o o0Ignition0o pinned this issue Feb 16, 2023
@o0Ignition0o o0Ignition0o mentioned this issue Feb 21, 2023
Merged
o0Ignition0o added a commit that referenced this issue Feb 21, 2023
@o0Ignition0o
Ban openssl in cargo-deny (#2638)
4f61bbf 
Ban openssl in cargo-deny

Part of a fix for #2623 

This change introduces a ban of openssl-sys in the project, with
exceptions on redis and redis-cluster-async.

This will allow us to prevent us from mistakenly reintroducing it in the
future.
@mabuyo
Copy link

mabuyo commented Feb 24, 2023

I came across this issue trying to host the router on Heroku! Heroku 22 uses Ubuntu 22.04 (which has the same issues as described above). I had to downgrade the Heroku stack from 22 to 20 using this command:

heroku stack:set heroku-20 -a <APP_NAME>

Hope it helps someone else!

@Geal Geal mentioned this issue Feb 27, 2023
Merged
6 tasks
@Geal Geal closed this as completed in #2689 Mar 9, 2023
Geal added a commit that referenced this issue Mar 9, 2023
@Geal
Use the fred Redis client (#2689)
818620d 
Fix #2623
Fix #2606

This replaces our usage of the `redis` and `redis-cluster-async` crates
with `fred`, which comes with support for Redis cluster and rustls out
of the box. Rustls support is only available in fred 6.0.0-beta.2
though, not in a stable release.
@o0Ignition0o o0Ignition0o unpinned this issue Mar 10, 2023
@dvileta
Copy link

dvileta commented May 24, 2024

Thanks for documenting this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Geal Geal

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use the fred Redis client apollographql/router
4 participants
@Geal @dvileta @mabuyo @o0Ignition0o