Sorry GamertodArk this issue tracker is for Rubygems, if your problem is not related to Rubygems i must close this issue, we can't help you with MegaSync beacuse we don't know nothing about it. GamertodArk I am not sure if this will help you, but the error message definitely makes it seem like Ruby cannot find the CA certificates, even though you have installed them. You might be able to get more help troubleshooting by going to superuser. Good luck figuring it out!
I had this issue before, and solved it by upgrading rubygems-update from 2. Skip to content. Star 2. New issue. Jump to bottom. Copy link. I don't know anything about ruby and gems, the reason that installed it it's because it is necesary to install sass, but when i run this command gem install sass.
Ok, let's see. Jump to bottom. Labels category: command type: bug report. Copy link. Don't have an account yet? I was already using the latest version. Closing this out. Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment. Linked pull requests. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. On older OSes, this CA bundle can be really old—as in a decade old.
Further complicating things, an otherwise unrelated change months ago lead to a new SSL certificate being issued for RubyGems. Start by running the automatic SSL check , and follow the instructions. You might need to update Bundler , update RubyGems , manually update RubyGems certificates , or perhaps even install new OS certificates.
This error means that your machine was unable to establish a secure connection to RubyGems. OpenSSL 1. To understand why that version is required, keep reading. Over time, researchers discovered flaws in SSL, and network developers responded with changes and fixes. After SSL 3. Over time, TLS was also revised. TLS version 1. Last year, Fastly announced it will deprecate TLS versions 1.
As a result, RubyGems. This means RubyGems. To troubleshoot protocol connection errors, start by running the automatic SSL check , and follow the instructions. You might need to update Bundler , update RubyGems , or even reinstall Ruby you can find reinstallation instructions by version manager or package manager. If that command fails, you can try downloading the latest RubyGems yourself and installing it, using these steps. In this example, we will be downloading and installing RubyGems 2.
If the latest version of RubyGems has changed by the time you are reading this, you will need to change anyplace you see 2. Run gem --version to verify that you are using the latest version of RubyGems. If your system clock is set to a time in the past or future, your machine will not be able to establish a secure connection to RubyGems. To resolve the issue, you will need to set your system clock to the current time.
In Linux, you can update the system clock by running sudo ntpdate ntp. If you have a version of RubyGems new enough version 2. Warning : These instructions will only add new certs; Ruby will be left untouched. To ensure your Ruby version can use TLSv1.
0コメント