next/image does not work when upgrading from 13.4 to 13.5
Unanswered
Saltwater Crocodile posted this in #help-forum
Saltwater CrocodileOP
Hi,
I have to say this only happens in production and not locally.... However I hope to have helpful error messages..... (as they are long, you can see them in the end)
My setup is: I have a VPS with Plesk. I have a docker container started through plesk and also have a proxy rule configured. So https://reisinger.pictures is proxied to docker to next running on localhost:3000 (which you cannot access)...
I used the following command to downgrade:
npm i next@13.4 @next/mdx@13.4 eslint-config-next@13.4 @next/eslint-plugin-next@13.4
I have no idea how to upgrade as I have a valid lets encrypt ssl cert, but honestly the nginx reverse proxy handles https. In any case the source file can be accessed using the browser.....
Attached is the error in the server console log.... Most important part:
and in the browser the following error message: "url" parameter is valid but upstream response is invalid
I have to say this only happens in production and not locally.... However I hope to have helpful error messages..... (as they are long, you can see them in the end)
My setup is: I have a VPS with Plesk. I have a docker container started through plesk and also have a proxy rule configured. So https://reisinger.pictures is proxied to docker to next running on localhost:3000 (which you cannot access)...
I used the following command to downgrade:
npm i next@13.4 @next/mdx@13.4 eslint-config-next@13.4 @next/eslint-plugin-next@13.4
I have no idea how to upgrade as I have a valid lets encrypt ssl cert, but honestly the nginx reverse proxy handles https. In any case the source file can be accessed using the browser.....
Attached is the error in the server console log.... Most important part:
at async /app/node_modules/next/dist/server/response-cache/index.js:102:36 {
cause: [Error: 584B4B3E647F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:
] {
library: 'SSL routines',
reason: 'wrong version number',
code: 'ERR_SSL_WRONG_VERSION_NUMBER'
}
}and in the browser the following error message: "url" parameter is valid but upstream response is invalid
12 Replies
Turkish Angora
I'm also having this issue, but only when I change the quality prop in next/image
Works fine
Experiences the same error @Saltwater Crocodile has
Works fine
<Image
className="-z-10 object-cover"
src={background.src}
alt="background"
fill
/>Experiences the same error @Saltwater Crocodile has
<Image
className="-z-10 object-cover"
src={background.src}
alt="background"
quality={100}
fill
/>Turkish Angora
bump
Turkish Angora
Bump
Turkish Angora
bump
Turkish Angora
Bump
Saltwater CrocodileOP
My issue has been resolved by using a not optimized docker container script
@Saltwater Crocodile My issue has been resolved by using a not optimized docker container script
Turkish Angora
Are you sure it's resolved? In my experience this issue will suddenly flare up after like 5 days of error free operation
Mossyrose gall wasp
its happens to me too i just revert back to previous version. i see this is bug that issues created in github. iirc it happens because of type lol
Turkish Angora
Good news, a maintainer has seen the issue on GitHub and assigned a label
would be nice to see the issue here
@aardani would be nice to see the issue here
Turkish Angora
Turkish Angora
@Saltwater Crocodile Try canary 16, it's too early to say but I think the issue is fixed with the revert drop ipc headers fix