upstream image response failed for https://oaidalleapiprodscus.blob.core.windows.net/ 403 (Forbidden)

[nicitaacom]

Link to the code that reproduces this issue

https://github.com/nicitaacom/acc2-mvp-upstream-image-response-failed
https://verbose-doodle-xv6wgrx7gphq9q.github.dev/

To Reproduce

1. Open github codespace

or

1. Paste this code in created Next.js project with pnpx create-next-app@latest .

 <Image
        className="cursor-pointer max-h-[32px] w-auto h-auto"
        src="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"
        alt="logo"
        width={300}
        height={32}
        priority
      />

Current vs. Expected behavior

Then you will see this error (also related to this and this issue)

https://private-user-images.githubusercontent.com/39565703/309553012-76f87054-12a8-42ac-b4c9-7d9ebced6886.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDk0NzI4NjEsIm5iZiI6MTcwOTQ3MjU2MSwicGF0aCI6Ii8zOTU2NTcwMy8zMDk1NTMwMTItNzZmODcwNTQtMTJhOC00MmFjLWI0YzktN2Q5ZWJjZWQ2ODg2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAzMDMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMzAzVDEzMjkyMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWEyZTc5MDIyMTA0NTQ1OTI0Zjk2YzcwOTlhZjBhODM0ZDllZjQ3ZmI4NmJlYjNmYWIzNWE5YjU2MDU3ZjY2NTImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.nDiTcapHxm6nsxKJ0u7FJ8fF5qiwHf0wZsxTUfPWBwE

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #19~22.04.1-Ubuntu SMP Wed Jan 10 22:57:03 UTC 2024
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.15.1
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Image optimization (next/image, next/legacy/image)

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I opened this issue because #53715 issue was automatically closed

https://private-user-images.githubusercontent.com/39565703/309552329-2a783cc8-4aa6-48ab-bb28-1b70321c74c2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDk0NzI4NjEsIm5iZiI6MTcwOTQ3MjU2MSwicGF0aCI6Ii8zOTU2NTcwMy8zMDk1NTIzMjktMmE3ODNjYzgtNGFhNi00OGFiLWJiMjgtMWI3MDMyMWM3NGMyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAzMDMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMzAzVDEzMjkyMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRlNDg2Yzc3ZDQ4ODZlOGYwYzBmMjRlMTQ0YWE0ODliZjFkNjkwNDViY2NmYTY0ZTUzYmQ0N2JiMGRhZDA4Y2QmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.e9g8T0Y9nGHgb_rs5zNvu75mBo9YH5Z_SQGnq-YumNQ

Fix your bot!

[JesseKoldewijn]

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.

[nicitaacom]

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

[JesseKoldewijn]

@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".

[JesseKoldewijn]

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

[balazsorban44]

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.

[nicitaacom]

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

[github-actions]

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.