Rvm update certificates

Learn more. Asked 3 years, 11 months ago. Active 3 years, 11 months ago. Viewed 1k times. Even though I'm on, and have defaulted to ruby 2. I had found that link and tried implementing the instructions but the result is that patch is no longer available.

I have come to the conclusion that at the moment January you cannot install ruby 2. I gave up and went to 2. Show 1 more comment. I got the same error if I use xenial. Sorry, something went wrong.

We're also experiencing the same issue with Ruby 3. We were already using the. Changing our dist to focal was enough to solve the problem temporarily.

I'm not sure if this is relevant but I am seeing log messages suggesting that some SSL certs expired:. I am wondering if it's related to this. The answer to this question suggests that the built-in curl binary on Mac OS The comments above about Ubuntu xenial would also make sense since xenial is probably old enough to have one of the buggy versions of OpenSSL. Temporarily passing -k fixes the issue as expected though it's insecure and OpenSSL would need to be upgraded instead :.

Happens for me as well on amazon-linux-2 , we are developing inside docker containers, so rvm is part of Dockerfile. I reached out to Travis support regarding this issue, and I was advised to do the following:.

All of this to say - I'm sure something is going awry on rvm 's end that needs to be addressed at least as far a xenial is concerned , but at least now we have a workaround from the Travis end. So the certificate is definietly correct. Can you check if your system time is set properly? Maybe this is the issue? Yeah, I also double checked the cert is valid, so double check the system time on a pipeline.

This also applies when setting a default Ruby. Below is an example of what I mean:. Minor version. For example, if you only have 2. This behaviour may, or may not, be what you want. If its not, then be sure to include the patch level when you specify which Ruby RVM should use when setting a default. Minor e. RVM does not go by what you have installed for this reason.

It goes by what is maintained in those two files. Ruby Semantic Versioning. To be able to "use" your system ruby you can tell RVM to undo the environment changes that it has applied, as follows.

In this case, you can see that RVM has, in fact, 'hidden' itself from the system, and given you access back to the system installed Ruby. Hidden does not mean RVM is gone, instead, what is done is the system environment and related variables are set back to what the system Ruby would expect them to be as if RVM were not installed at all. The current equivalent of latest is stable and should be used instead. When updating very old versions head should be used and can be followed by stable.

If you can help or wish to become one of the maintainers - just start helping. Love RVM?