Status 500 with container registery

David Ciampi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 6, 2023
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?

1 answer

1 accepted

1 vote
Answer accepted
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 7, 2023

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)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events