Retrying fetcher due to error: Bundler::HTTPError | by Christophe Nonato | Medium

Ask questions Research chat →

https://medium.com/@chr.nonato/retrying-fetcher-due-to-error-bundler-httperror-558315f45612 · scraped

deploy

Attachments

Scraped Content

— 205 words · 2026-02-14 03:02:12 UTC ·

Excerpt

Retrying fetcher due to error: Bundler::HTTPError I recently faced a connection error with rubygems.orgPress enter or click to view image in full sizeOMG rubygems, please.After successfully setting up my environment on Ubuntu 20.04 LTS in a new machine, I suddenly faced this error.Commands like bundle install and gem install were not doing their job although network connection was just fine, including normal access to https://rubygems.org/.Googling around, I’ve seen many suggestions like: Changing Gemfile’s source 'https://rubygems.org'to http://Imploding then reinstalling Rbenv / Rvm with my Ruby version again.Checking for active proxies and unset them. Apparently those worked for most people, but no success for me :(— The issue for me was IPv6 address connection to rubygems.orgPress enter or click to view image in full sizewget -6 rubygems.orgPress enter or click to view image in full sizewget -4 rubygems.orgTo solve the problem you can disable IPv6, or even better as proposed by Ale
Retrying fetcher due to error: Bundler::HTTPError I recently faced a connection error with rubygems.orgPress enter or click to view image in full sizeOMG rubygems, please.After successfully setting up my environment on Ubuntu 20.04 LTS in a new machine, I suddenly faced this error.Commands like bundle install and gem install were not doing their job although network connection was just fine, including normal access to https://rubygems.org/.Googling around, I’ve seen many suggestions like: Changing Gemfile’s source 'https://rubygems.org'to http://Imploding then reinstalling Rbenv / Rvm with my Ruby version again.Checking for active proxies and unset them. Apparently those worked for most people, but no success for me :(— The issue for me was IPv6 address connection to rubygems.orgPress enter or click to view image in full sizewget -6 rubygems.orgPress enter or click to view image in full sizewget -4 rubygems.orgTo solve the problem you can disable IPv6, or even better as proposed by Alexei Khlebnikov, lower priority of IPv6 addresses for api.rubygems.org, so that gem install or bundle install will try IPv4 addresses first.Press enter or click to view image in full sizeCheck Alexei Khlebnikov’s solution here: https://stackoverflow.com/questions/49800432/gem-cannot-access-rubygems-org/50349235#50349235This has been an issue for years now, let’s see if it gets fixed someday.I hope I’ve saved you some time :]

Visibility

Visible to everyone

Reading Status

Related Bookmarks

My Note


Saved!

Annotations

Export as Markdown
+ Annotate selection

Add Annotation