Issue #1906 resolved

abort: error: Connection refused

David Vega avatarDavid Vega created an issue

I have been getting the following error message all day for *all* my repositories when trying tu push/pull/clone as usual:

abort: error: Connection refused

Have not seen anyone tweet about this, so I think it might be a bug with my account?.

Comments (2)

  1. Jesper Nøhr

    Resolved, as per #1905. Copy/paste:

    Seems a load balancer was firewalling HTTPS (443) after Amazon decommissioned the instance. I've started the tunnel again, and added a probe in our monitoring to automatically alarm of of these again.

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.