Question

`create-deployment` failing with 504 Gateway-timeout

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?

Show comments

Submit an answer

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!

Sign In or Sign Up to Answer

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.

We are having the same issue, since the same date. It seems to work randomly

Having a similar issue, with a similar error but using managed gitlab runners in our own k8s cluster. docker login -u dokey -p dokey registry.digitalocean.com

Works in CI and from local machine.

docker push registry.digitalocean.com/..... works from local machine, but fails from CI. The CI log is full of retrying in **X** seconds.

Is this a change made on the DO side?

👋 @elliotplant

Please submit a support ticket so our team can take a deeper look at your specific app.