Next Image Vercel - Error 502

Kellokes commented 1 year ago

Verify canary release

[X] I verified that the issue exists in the latest Next.js canary release

Provide environment information

Hi Guys,

Was there any update on vercel yesterday related to the image optimization component?  I haven't made any changes to my code for over a week and yesterday all new images optimized via the Next.js Image component started to break, here's the evidence.

IMAGE URL: https://www.postforge.app/_next/image?url=https://cdn.midjourney.com/0396d1da-905b-49c8-9047-a2534fb287cd/0_0.png&w=828&q=75

Which area(s) of Next.js are affected? (leave empty if unsure)

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

Screenshot_20230629-101852 Screenshot_20230629-101846

Expected Behavior

Image appears correctly

Which browser are you using? (if relevant)

Chrome

How are you deploying your application? (if relevant)

Vercel

balazsorban44 commented 1 year ago

Hi, it's unclear from the provided information what could have happened here. Can you link to a minimal reproduction repository? You can first also make sure that you have the latest version of next installed in case an issue related has already been fixed.

The issue might have different reasons, one is that the original image needs authorization, just like in the case of #42776.

We can investigate more with more details. :pray:

github-actions[bot] commented 1 year ago

We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate.

Why was this issue marked with the `please add a complete reproduction` label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository (template for pages, template for App Router), but you can also use these templates: CodeSandbox: pages or CodeSandbox: App Router.

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue.

Please test your reproduction against the latest version of Next.js (next@canary) to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the please add a complete reproduction label that receives no meaningful activity (e.g. new comments with a reproduction link) are automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the :+1: reaction on the topmost comment (please do not comment "I have the same issue" without reproduction steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

flosrn commented 1 year ago

I am experiencing the exact same issue. All of my new images, whether optimized with next/image or next/legacy/image, are encountering problems.

styfle commented 1 year ago

Closing since https://www.postforge.app doesn't exist anymore.

If you are having problems with Next.js, please provide the code to reproduce using next build && next start.

If the problem only happens on Vercel deployments, please create a support case here: https://vercel.com/help#issues

github-actions[bot] commented 1 year ago

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.

vercel / next.js