Getting error in launcher rebuild app

today I am getting errors in trying to rebuild the app and nothing I try has any effect. In particular the error I am getting is:

I, [2023-03-18T16:41:52.325609 #1]  INFO -- : > cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
ERROR:  Could not find a valid gem 'bundler' (= 2.4.4), here is why:
          Unable to download data from https://rubygems.org/ - Errno::EADDRNOTAVAIL: Failed to open TCP connection to rubygems.org:443 (Cannot assign requested address - connect(2) for "rubygems.org" port 443) (https://rubygems.org/specs.4.8.gz)

There was a short blip earlier where rubygems really had a problem, but as far as I can tell thats no longer the case. I can download everything here, just when trying to run through the launcher it does not work.

Any hints for a ruby dummy?

1 Like

Did you see this earlier similar-looking problem, where the solution was related to ipv6?
Build Fails on New Host

Thanks, yes I did see that, and while I do have IPv6 enabled on that host it is enabled since the forum was born.

I specifically looked and in docker there is no IPv6 enabled, and rubygems.org resolv just fine to an ipv4 address.

Maybe try

wget -O /dev/null https://rubygems.org

and see what happens. I’m not absolutely sure if this should be tried on the host or inside the container - for me, in both cases it works OK.

2 Likes

Thanks Ed, that gets us closer to the root cause.

rubygems.org - works on host, inside the container:

Connecting to rubygems.org (rubygems.org)|151.101.1.227|:443... failed: No route to host.

But

wget -O /dev/null https://google.com

Works just as it should. Mayhaps rubygems still has a problem. I guess I am going to try on Monday again.

Since google works, I think I can assume the setup is correct, meaning the problem seems to be outside of my control.

Thanks again for the troubleshooting help.

2 Likes

Did you find any solution to this problem? (Rebuild unable to reach rubygems website)

Yes, I did find a solution. it seems as if rubygem did have a problem at the time. I started the rebuild again the next morning and it went through just as it was supposed to.

Since I did not change anything and my internet connection was up and running (being my own ISP does have advantages) my only guess is that rubygems did in fact really have a problem.

Thanks again for the help

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.