RubyGems远程gem查询无结果，本地查询正常问题求助

I’ve dealt with exactly this kind of issue on older Ruby/RubyGems setups before— let’s walk through the most likely fixes step by step:

1. Verify Your RubyGems Sources #

First, check what remote sources your gem client is configured to use. Run:

gem sources

• If you don’t see https://rubygems.org/ listed, that’s the core problem. Add the official source with:

  gem sources --add https://rubygems.org/
  

• If there are other invalid/unreachable sources listed, remove them to avoid conflicts:

  gem sources --remove [invalid-source-url]
  

• As a quick diagnostic test (not recommended for long-term use), you can try the HTTP version of the source to rule out SSL issues temporarily:

  gem sources --add http://rubygems.org/
  

  Then re-run gem list -r ra to see if it returns results.

2. Check Network & SSL Certificate Issues #

Remote gem lookups depend on a stable connection to rubygems.org and valid SSL certificates.

• Test connectivity directly with curl to spot network or SSL errors:

  curl -v https://rubygems.org
  

  Watch for red flags like "connection refused", "timeout", or "SSL certificate problem" in the output.
• If you see SSL certificate errors, update your system’s CA certificates (package name varies by distro— e.g., ca-certificates on Debian/Ubuntu).
• You can also temporarily skip SSL verification to confirm it’s the root cause:

  gem list -r --no-ssl-verify ra
  

  If this works, you’ll need to fix your SSL setup (either update certs or ensure RubyGems uses the correct cert store).

3. Update RubyGems to a Compatible Version #

Your RubyGems version (2.7.3) works with Ruby 2.5.0, but older versions can have bugs with remote source resolution. Let’s update to the latest compatible version (Ruby 2.5 doesn’t support RubyGems 4.x+, so we’ll target 3.3.x):

gem update --system 3.3.26

After updating, re-test the remote lookup commands.

4. Check for Misconfigured .gemrc Settings #

Your local ~/.gemrc file might have settings blocking remote lookups. Inspect it with:

cat ~/.gemrc

• Look for lines like disable_fetching: true— this would completely block remote queries, so remove it if present.
• If you’re behind a proxy, ensure the correct http_proxy or https_proxy settings are in place. If you don’t need a proxy, delete any proxy-related lines.

内容的提问来源于stack exchange，提问作者Thomas L. Lucero