nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Status 500 with container registery

Failed

Status 500: {"message":"Get \"https://xxxx.zzzcr.io/v2/\": dial tcp x.x.x.x:443: connect: connection refused"}

Occassionally, I see my self hosted runner report back with a failed status 500 message.
Is there a work around for this or is there simply an error I need to take up with the regsitry provider?

Accepted answers

Hi David,

The error message relates to unsuccessfully establishing a connection over HTTPS to the destination container registry.

The error 500 indicates that this is occurring on the server-side, so I would suggest reaching out to the registry provider in this instance.

Cheers!

- Ben (Bitbucket Cloud Support)

All comments

Hi David,

The error message relates to unsuccessfully establishing a connection over HTTPS to the destination container registry.

The error 500 indicates that this is occurring on the server-side, so I would suggest reaching out to the registry provider in this instance.

Cheers!

- Ben (Bitbucket Cloud Support)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud