ruby/rubygems · error

RubyGems: failed (#{Explanation.explain_bundler_or_

Error message

RubyGems:      failed     (#{Explanation.explain_bundler_or_rubygems_error(error)})

What it means

Error "RubyGems: failed (#{Explanation.explain_bundler_or_rubygems_error(error)})" thrown in ruby/rubygems.

Source

Thrown at lib/bundler/cli/doctor/ssl.rb:94

        Bundler::Source::Rubygems::Remote.new(bundler_uri)
      ).send(:connection).request(bundler_uri)

      Bundler.ui.info("Bundler:       success")

      true
    rescue StandardError => error
      Bundler.ui.warn("Bundler:       failed     (#{Explanation.explain_bundler_or_rubygems_error(error)})")

      false
    end

    def rubygem_connection_successful?
      Gem::RemoteFetcher.fetcher.fetch_path(uri)
      Bundler.ui.info("RubyGems:      success")

      true
    rescue StandardError => error
      Bundler.ui.warn("RubyGems:      failed     (#{Explanation.explain_bundler_or_rubygems_error(error)})")

      false
    end

    def net_http_connection_successful?
      ::Gem::Net::HTTP.new(uri.host, uri.port).tap do |http|
        http.use_ssl = true
        http.min_version = tls_version
        http.max_version = tls_version
        http.verify_mode = verify_mode
      end.start

      Bundler.ui.info("Ruby net/http: success")
      warn_on_unsupported_tls12

      true
    rescue StandardError => error
      Bundler.ui.warn(<<~MSG)

View on GitHub (pinned to 86cbb817a3)

Solutions

  1. Update RubyGems (`gem update --system`) and ensure OpenSSL/certs are current, as the explanation suggests

When it happens

Trigger: Thrown at lib/bundler/cli/doctor/ssl.rb:94 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of ruby/rubygems@86cbb817a3 (2026-08-23). Data as JSON: /api/errors/33128a642d7a3381. Report an issue: GitHub.