Status 500 with container registery

[David Ciampi]

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?

[Ben · Accepted solution]

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)