Creating a deployment with the
doctl cli is failing with a “504 Gateway-timeout” error. We are seeing this error on both
github deploys and when we try to push images to
registry.digitalocean.com. It has been happening since September 22.
We are confident our authentication is working because
doctl auth init outputs
Validating token... OK.
Is there a larger outage or is this specific to our DigitalOcean account?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
It turns out this issue was caused by our Digital Ocean Container Registry being “full”. We were on the free plan, and I was under the impression that we would just be charged for usage over the 5gb limit, but it turns out that DO responds with this 504 error instead of letting you continue to fill your registry.
To fix this issue, collect all the garbage in your registry and delete your unused images. If you can afford it, upgrade to the paid plan so you don’t have to empty your registry as frequently.
We are having the same issue, since the same date. It seems to work randomly
The push refers to repository [registry.digitalocean.com/****/*****] 1c273ad9: Preparing 49bba3d9: Preparing e36718e0: Preparing b205f993: Preparing bf18a086: Preparing 2936d803: Preparing 3a384ae2: Preparing 978997d5: Preparing 465fddf0: Preparing 64e55619: Preparing received unexpected HTTP status: 524 Exited with code exit status 1
CircleCI received exit code 1