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.

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

ruby-packer fails with SSL error #141

Open
d4rky-pl opened this issue Dec 14, 2020 · 1 comment · May be fixed by #154
Open

ruby-packer fails with SSL error #141

d4rky-pl opened this issue Dec 14, 2020 · 1 comment · May be fixed by #154

Comments

@d4rky-pl
Copy link

When trying to build the application with latest ruby-packer, it fails on running the bundle install step with Could not verify the SSL certificate.

This happens both locally and on CI.

-> CI=true PATH=/var/folders/kc/w3zg_rmd6vnd_5w22fw154yh0000gn/T/rubyc/ruby_install/bin:/__enclose_io_memfs__/lib/ruby/gems/2.7.0/bin:/Users/matyas/.asdf/shims:/usr/local/opt/asdf/bin:/Users/matyas/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/matyas/.ht/bin ENCLOSE_IO_USE_ORIGINAL_RUBY=true ENCLOSE_IO_RUBYC_1ST_PASS=true ENCLOSE_IO_RUBYC_2ND_PASS='' /var/folders/kc/w3zg_rmd6vnd_5w22fw154yh0000gn/T/rubyc/ruby_install/bin/bundle install
Fetching source index from https://rubygems.org/

Retrying fetcher due to error (2/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.

Retrying fetcher due to error (3/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.

Retrying fetcher due to error (4/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.

Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA
certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect
without using SSL, edit your Gemfile sources and change 'https' to 'http'.
Failed running [{"CI"=>"true", "PATH"=>"/var/folders/kc/w3zg_rmd6vnd_5w22fw154yh0000gn/T/rubyc/ruby_install/bin:/__enclose_io_memfs__/lib/ruby/gems/2.7.0/bin:/Users/matyas/.asdf/shims:/usr/local/opt/asdf/bin:/Users/matyas/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/matyas/.ht/bin", "ENCLOSE_IO_USE_ORIGINAL_RUBY"=>"true", "ENCLOSE_IO_RUBYC_1ST_PASS"=>"true", "ENCLOSE_IO_RUBYC_2ND_PASS"=>nil}, "/var/folders/kc/w3zg_rmd6vnd_5w22fw154yh0000gn/T/rubyc/ruby_install/bin/bundle", "install"]

It seems that RubyGems have been messing with their certificates (rubygems/rubygems/pull/4105, rubygems/rubygems/pull/4100, rubygems/rubygems/issues/4099) which may be causing this isssue

@64kramsystem 64kramsystem linked a pull request Feb 17, 2021 that will close this issue
@64kramsystem
Copy link
Contributor

@d4rky-pl Closed by #154.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants