Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

503 (Service Unavailable) #1412

Open
mak33v opened this issue Jul 20, 2024 · 8 comments
Open

503 (Service Unavailable) #1412

mak33v opened this issue Jul 20, 2024 · 8 comments

Comments

@mak33v
Copy link

mak33v commented Jul 20, 2024

I've been experiencing this issue for over a year now, both in development and production mode. Every time the page is reloaded, the images do not load randomly, then one thing or another. What can be wrong?

image

In production mode I see this error, the symptoms are the same as with the 503 error in development.

image

@Lehoczky
Copy link
Contributor

This happens to me constantly as well

@Healios
Copy link

Healios commented Aug 5, 2024

I'm in the middle of redoing a Nuxt 3 project and I also get this error constantly. The error is not present in the old project. The old project uses package version is "^1.0.0-rc.1" and the new uses "^1.7.0".

@AKadochnikov
Copy link

I have a similar problem
nuxt version 3.10.0

@Drstocktor
Copy link

same.. would love to hear if someone figured out a bandaid fix at the very least

@ZnaaMiR
Copy link

ZnaaMiR commented Aug 15, 2024

same.. would love to hear if someone figured out a bandaid fix at the very least

Also experiencing this when using ipx as image provider. You could either temporarily fix it by handling the error like so: <NuxtImg @error="handleImageError" />

const handleImageError = (event) => { event.target.src = "/images/fallback.png"; };
It seems to trigger the image to load correctly after the error happens.

or you can disable ipx as the image provider.

@awdr74100
Copy link

The same thing is happening to me, is it related to multiple images being optimized in runtime at the same time? If this problem is not a bug but a limitation it will make the module completely unusable on any commercial site.

Can anyone confirm that the image component of Next.js has the same problem? It seems to be a similar logic

@bernhardberger
Copy link

Any chance you guys are using SWR? As that breaks ipx when not excluding it from SWR with route rules ( /_ipx/**, { cache: false })

@Healios
Copy link

Healios commented Oct 5, 2024

Any chance you guys are using SWR? As that breaks ipx when not excluding it from SWR with route rules ( /_ipx/**, { cache: false })

I'm not using SWR, unless it's enabled by default?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants