App Platform: Unexpected error on this mornings deployments

Posted on November 5, 2024

Hello, we have several nuxt.js apps deployed using App Platform. Starting from few hours ago all new deployments fail in the “app upload” phase.

Here is the error from the build log:

╭──────────── app upload ───────────╼
[2024-11-05 11:31:33] │  › uploading app container image to DOCR
[2024-11-05 11:31:34] │ Adding layer 'heroku/nodejs-engine:nodejs'
[2024-11-05 11:31:37] │ Adding layer 'heroku/nodejs-engine:yarn'
[2024-11-05 11:31:43] │ Adding 2/2 app layer(s)
[2024-11-05 11:31:43] │ Adding layer 'launcher'
[2024-11-05 11:31:43] │ Adding layer 'config'
[2024-11-05 11:31:43] │ Adding label 'io.buildpacks.lifecycle.metadata'
[2024-11-05 11:31:43] │ Adding label 'io.buildpacks.build.metadata'
[2024-11-05 11:31:43] │ Adding label 'io.buildpacks.project.metadata'
[2024-11-05 11:31:43] │ Saving <image-1>...
[2024-11-05 11:31:43] │ *** Images (sha256:f2443266697fa0158b12ebedbd9ae41eed97232703a7465d4eacc8b1574daa1f):
[2024-11-05 11:31:43] │       <image-2> - HEAD <registry-uri-3> unexpected status code 401 Unauthorized (HEAD responses have no body, use GET for details)
[2024-11-05 11:31:43] │ ERROR: failed to export: failed to write image to the following tags: [<image-4>: HEAD <registry-uri-5> unexpected status code 401 Unauthorized (HEAD responses have no body, use GET for details)]
[2024-11-05 11:31:43] │ 
[2024-11-05 11:31:43] │ command exited with code 246

It then tries 3 more times, with the same error.

DO status page says everything is ok…

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.

Bobby

November 5, 2024

Hey @davidecattani,

Indeed there are no reported incidents about this.

If you are still seeing this error, I would recommend reaching out to the DigitalOcean support team directly who will be able to further investigate this for you: