Hi all! Built a site for my friends at Iconique Real Estate a few years back using Nuxt2, Contentful, and Netlify.
Netlify site name: iconiquere.netlify.app
Site domain: iconiquere.com
Node version: 20.x
Site has been working seamlessly for several years, but in the past year or so we have had growing issues where deploys are more frequently failing and timing out.
We have a Netlify buildhook tied to Contentful. They now have over 200 listings (dynamic detail pages for each property listing), which seems like a lot, but all of these site pages are pretty much just text. All videos are hosted on Vimeo, and all images come from Cloudinary (yes, I am using the Contentful Cloudinary App).
When the client publishes a change from Contentful, it seems like 99% of the time, the Netlify buildhook triggers a deploy and it sits anywhere from 15 minutes to an hour, and then it finally fails. Our temporary solution is to Publish changes in Contentful, then jump over to Netlify deploys and cancel the one that is starting to build. Then we manually trigger a new deploy, which seems to work, but even this occasionally fails and we repeat the process of cancelling (or waiting an hour) and then trigger a new deploy.
The strange thing is, when the site deploy does Publish successfully, it only takes 2-3 minutes, so the deploys are relatively quick! I’ve seen other forum articles saying we need to increase our deploy time, but again, a successful build only takes a couple minutes, so a increasing our build time doesn’t seem like the issue.
Please let me know if I can provide any more info, thank you so much for looking into this with us!
Nuxt 2 has reached its End of Life last year: Nuxt 2 End-of-Life (EOL) · Nuxt Blog. We don’t provide tech support for outdated software.
@hrishikesh I have dozens of other sites build from years back on Nuxt2 that work seamlessly still. Let’s imagine I was on Nuxt3.
Feel free to upgrade to Nuxt 3 and we’ll check.
Not sure if you’re aware, but we can check that. You can choose to continue engaging, but we’ll not reply further until you seriously put some efforts to solve the problem, that first step would be the upgrade to a software that’s still supported by its creators (let alone a 3rd party).
@hrishikesh Understandable, but Nuxt isn’t the issue. We have plenty of legacy sites that use Contentful and Netlify buildhooks from years back and those all work great. We don’t have the bandwidth right now to convert Nuxt2 to Nuxt3 on this project.
I’m not saying Nuxt is the issue. It could very well be a Netlify issue, but:
- we won’t be spending time on investigating an issue due to whatever incompatibility has been introduced between Nuxt 2 and Netlify
- maybe the incompatibility has already been changed/fixed/made-compatible in recent Nuxt versions
- maybe something changed on Netlify and now this is broken (not that I’m aware of anything like this, but giving you the benefit of doubt)
In an ideal world, we would love to be able to provide tech support for all versions of all pieces of software, but:
- we’ve limited resoources
- a lot of things keep changing
- the creator of the software itself doesn’t provide any support for it anymore, how fair is it to ask us to support it
Even if we tried investigating it and required some help from Nuxt team, we won’t get that simply because Nuxt has given up on that version. So there’s no point to start digging where we’re aware that there’s a rock bottom.
Since you mention you don’t have bandwidth to convert your projects to Nuxt 3 right now, I assume you can imagine how less bandwidth we’ll have to support those ancient versions with so many things changing so frequently.
I’m afraid there’s not much we can offer here until you choose to upgrade. If your project builds locally, you can continue to deploy using Netlify CLI or use some other platform to build your site (like GithHub Actions) and deploy to Netlify from there.
Hah, ok @hrishikesh. Thank you.
