Unable to connect to https://rubygems.org


#1

Hi,

At the moment after running “bundle install” on my rails app, it seems I cannot connect to rubygems.org with following error.

Fetching source index from https://rubygems.org/
Retrying source fetch due to error (2/3): Bundler::HTTPError Could not fetch specs from https://rubygems.org/

Anyone experiencing similar issue? Thanks.


#2

See if you can curl google.com to make sure you have an internet connection from within the workspace and then post the results back here.


#3

Hey,

I am seeing a similiar issue with with npm and github etc., I can’t install any package or clone a repo. I tried curl google.com I got this curl: (7) Failed to connect to google.com port 80: Connection refused. This happened to me twice already. I moved to another workspace when it happened first time. This is the ourput of curl --verbose google.com

* Rebuilt URL to: google.com/
* Hostname was NOT found in DNS cache
*   Trying 64.233.182.100...
*   Trying 2607:f8b0:4001:c02::64...
* Immediate connect fail for 2607:f8b0:4001:c02::64: Network is unreachable
* connect to 64.233.182.100 port 80 failed: Connection refused
*   Trying 64.233.182.102...
* connect to 64.233.182.102 port 80 failed: Connection refused
*   Trying 64.233.182.113...
* connect to 64.233.182.113 port 80 failed: Connection refused
*   Trying 64.233.182.139...
* connect to 64.233.182.139 port 80 failed: Connection refused
*   Trying 64.233.182.138...
* connect to 64.233.182.138 port 80 failed: Connection refused
*   Trying 64.233.182.101...
* connect to 64.233.182.101 port 80 failed: Connection refused
* Failed to connect to google.com port 80: Connection refused
* Closing connection 0
curl: (7) Failed to connect to google.com port 80: Connection refused

Can you tell me how to fix this? I have already written support but no reply yet.


#4

@vramana just checked out your workspaces now and they’re good. That’s not satisfactory to just have it fix itself after a little while so if you or anyone else sees this in the future please mention @bradydowling and I can notify the right engineer for him to troubleshoot this.