#next/image does not work when upgrading from 13.4 to 13.5

13 messages · Page 1 of 1 (latest)

lost mauve
#

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 [email protected] @next/[email protected] [email protected] @next/[email protected]

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

📎 server.log
Fotograf Florian Reisinger
worldly hingeBOT
#
Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

vivid obsidian
#

I'm also having this issue, but only when I change the quality prop in next/image

Works fine

<Image
  className="-z-10 object-cover"
  src={background.src}
  alt="background"
  fill
/>

Experiences the same error @lost mauve has

<Image
  className="-z-10 object-cover"
  src={background.src}
  alt="background"
  quality={100}
  fill
/>
vivid obsidian
#

bump

vivid obsidian
#

Bump

vivid obsidian
#

bump

vivid obsidian
#

Bump

lost mauve
#

My issue has been resolved by using a not optimized docker container script

vivid obsidian
tribal patrol
#

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

vivid obsidian
#

Good news, a maintainer has seen the issue on GitHub and assigned a label

vestal fox
#

would be nice to see the issue here

vivid obsidian