upstream image response failed for https://oaidalleapiprodscus.blob.core.windows.net/ 403 (Forbidden) about next.js HOT 7 CLOSED

Hi, if the upstream image is unavailable, unfortunately, there is not much we can do. Make sure the image is public/available:

curl https://oaidalleapiprodscus.blob.core.windows.net/private/org-d56Gy26wIdxhjMRzQ4RCY7oE/user-eVuJbG2XXxpNPnGzFtGaN4z3/img-4X9T7uxzGelYaHPa1sOYa3jQ.png\?st\=2024-02-24T15%3A25%3A31Z\&se\=2024-02-24T17%3A25%3A31Z\&sp\=r\&sv\=2021-08-06\&sr\=b\&rscd\=inline\&rsct\=image/png\&skoid\=6aaadede-4fb3-4698-a8f6-684d7786b067\&sktid\=a48cca56-e6da-484e-a814-9c849652bcb3\&skt\=2024-02-24T15%3A18%3A12Z\&ske\=2024-02-25T15%3A18%3A12Z\&sks\=b\&skv\=2021-08-06\&sig\=SC%2BV4aiR4d02OTPYLw19UtsNmzLDOuGm0h8ir0Phzug%3D -I 
HTTP/1.1 403 Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
Transfer-Encoding: chunked
Server: Microsoft-HTTPAPI/2.0
x-ms-request-id: cb16ff57-101e-0009-4050-6e5cac000000
x-ms-error-code: AuthenticationFailed
Date: Mon, 04 Mar 2024 16:25:56 GMT

As for the bot, as noted in the bug template description as well as the comment, we only allow github.com and codesandbox.com links, and they have to be public! https://github.com/codespaces/verbose-doodle-xv6wgrx7gphq9q gives 404 for me, so it's likely private, which we cannot investigate. So the bot worked as expected.

This doesn't seem like a Next.js bug, so I'm closing for now.

from next.js.

Out of curiosity, what do you expect to happen other than the before mentioned error when a Image src throws an http error? Since on the optimisation side, the Next Image component can't handle the image if this is not available using the given url.

from next.js.

Out of curiosity, what do you expect to happen other than the before mentioned error when a Image src throws an http error?

I expect that you may fix this issue somehow
#56025

from next.js.

@nicitaacom I might be misunderstanding the issue at hand. But from what I see the described behaviour is to be expected if the upstream image can't be reached. So I don't really get what you want to see getting "fixed".

from next.js.

The issue you send in your reply is also unrelated the this current issue.

from next.js.

This doesn't seem like a Next.js bug, so I'm closing for now.

Codesandbox is buggy and slow especially in vs code and codesandbox may be unavailabe in 1 month for example with error like "out of free containers" or something like that

Try this one more time - https://verbose-doodle-xv6wgrx7gphq9q.github.dev/ - I reloaded codespace

Also I agree that it seems like issue from OpenAI
Thank you for response

from next.js.

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

from next.js.