Resolving MySQL2 Gem's Obsession with OpenSSL 1.0 instead of 1.1

Описание: Struggling with the MySQL2 gem insisting on OpenSSL `1.0`? Discover a straightforward solution to ensure your Rails app uses OpenSSL `1.1` instead.
---
This video is based on the question https://stackoverflow.com/q/62406726/ asked by the user 'Cameron' ( https://stackoverflow.com/u/302533/ ) and on the answer https://stackoverflow.com/a/62408861/ provided by the user 'Cameron' ( https://stackoverflow.com/u/302533/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: mysql2 gem insisting on using openssl 1.0 instead of 1.1

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Resolving MySQL2 Gem's Obsession with OpenSSL 1.0 instead of 1.1

If you're a Ruby on Rails developer, you might occasionally encounter frustrating compatibility issues between gems and dependencies. One common problem arises when the MySQL2 gem insists on using OpenSSL 1.0, even after you've upgraded to OpenSSL 1.1. This guide will guide you through understanding the issue and provide you with a straightforward solution to get everything running smoothly.

Understanding the Problem

Recently, you may have upgraded OpenSSL to version 1.1 and reinstalled Ruby 2.5.3 for your Rails application. However, when you attempt to run your application or a command like bundle install, you might receive an error message indicating that the MySQL2 gem is trying to load the old OpenSSL 1.0 library.

The error you might see looks something like this:

[[See Video to Reveal this Text or Code Snippet]]

This suggests that the MySQL2 gem has hardcoded paths or dependencies that still point to the older version of OpenSSL, causing your application to malfunction.

Solution: Quick Fix

The good news is that solving this issue is simple! Here’s how you can fix the problem without the need for reinstalling the MySQL2 gem with additional flags.

Steps to Resolve

Source Your Shell Configuration:
The key step you might be missing is refreshing your shell configuration. Depending on whether you're using Zsh or Bash, run one of the following commands:

[[See Video to Reveal this Text or Code Snippet]]

or

[[See Video to Reveal this Text or Code Snippet]]

Re-run Bundle Install:
After sourcing your configuration, simply navigate to your Rails application directory and run:

[[See Video to Reveal this Text or Code Snippet]]

Why This Works

By sourcing your shell configuration file, you're ensuring that the environment variables you set (pointing to the correct OpenSSL version) are active in your current shell session. This eliminates the need for additional flags during gem installation, as the installation process can now correctly locate OpenSSL 1.1.

Conclusion

Dealing with dependency issues can frustrate even experienced developers. However, by following the steps outlined above, you'll be able to sidestep the MySQL2 gem's insistence on using OpenSSL 1.0, ensuring a smoother development experience.

Remember, whenever you make changes to your environment variables in your shell configuration file, don't forget to source it for the current terminal session to reflect those changes!

Now you're all set to continue developing your Rails app without the headache of older OpenSSL versions getting in the way.

Happy coding!