Images using next/image suddenly stopped working

Hi,

Just checked my companies website this morning and all of a sudden pretty much all images are returning 500 errors. Hadn’t triggered a build or made any code changes and suddenly, no images.

I’m using next/image and the source of the images are coming from Contentful (images.ctfassets.net). Funny enough, working fine locally but the live site is not.

Anyone else getting these sudden issues? what’s changed?

website: https://brightsignals.co.uk/

1 Like

I’m seeing this:

We’re also running into this in our end. No changes had occurred from us and not sure when this exactly started. Seeing 500 responses when using the next/image component to load external assets.

Website: https://seedhealth.com

Exact same as OP-- Contentful images work fine locally, passing the file url to next/image, but getting 500 on netlify. I’ll add that next/image loading from Cloudinary is working fine on the same site.

1 Like

Hi all, thank you so much for reporting this! Looks like something is going on. I’m passing this over to our dev team to investigate, and will most likely be back here shortly for more details! Thanks everyone!

Hello again! @mellis84 and @bayphillipsseed - this should be resolved for both of you now, so please inform us if you are still receiving any errors.

@Timmehs if you could send us your site or site ID, I can make sure your site is on the correct feature flag to resolve this. Thanks!

2 Likes

Hi @charlottechhum, we are experiencing the same issue (just starting with Netlify for our company website). The URL for now is https://fsi-next-drupal-website.netlify.app. Would we be able to get that fixed as well? Thank you very much.

1 Like

Should be resolved for you as well.

Hi Charlotte,

Seems to be fine now thank you, I got so nervous wondering what had happened. Thanks again!

I have the same issue, may I please have it resolved for my site?

Thanks very much

Just checking that it does seem to work with the netlify url just not my custom domain cglife.studio

Not sure what the issue is.

Hi @CGLIFE7,

Thanks for reaching out and welcome to Netlify’s Support Forums!

This should be resolved for you now. Can you let us know if you’re still having issues?

Cheers it has been resolved. Thanks


Hello, it seems I’ve encountered a similar issue. Many images on the website have started returning 503 errors. I think I first noticed this about a week ago. Could you please check on your side if everything is okay? https://mana-flood.ru/farseek

This should now be resolved.

1 Like

Hi I have two projects in nextjs that have the same issue, Can you tell us how to fix that? And is this going to be an issue when I switch it to my custom domains for those projects?

After reading those comments here, It looks like problem is with netlify and to get this fixed you need to post your website url here so Support goes and fixes it? Is that the procedure? What is the actual solution for this issue?

My two websites are:
First website
Second website

Thank you

I’m not seeing any failing images on your site. Could you show me the problem?

Happening to me now.

Why do responses only say ‘should be fixed for you now?’ Where is information and transparency?? What caused this? Clearly this is an on-going issue affecting many customers - it should really be better addressed. This is the third ‘random error’ I’ve encountered on Netlify in the last three days. Starting to consider moving everything to a new host.

The information is available to read:

As for:

The last verified issue was in October 2024, so this is clearly not ongoing. Plus, you’ve provided no details for anyone to be able to check your site or provide any help.

Not the last verified issue, the last post in this thread.. Also, I’ ended up having to change my entire codebase, as it’s a very well-known issue (amongst devs, anyway, though you seem to be trying to cover this up, for some reason) that Netlify hates dynamic sites and Nextjs. I literally had to turn the entire site to a static site for anything to display. You have problems with your infrastructure, and it would serve you better to own up to it and fix things rather than try to attack customers that report problems. You incurred hours more work for me to change my codebase, and I’ve started moving some work to a new host. Really, get your act and attitude in better order..