No images on overview

[X-static]

Describe the bug
The movie posters images are not showing on the overview page.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Overview'
2. There are no pictures on movies

Expected behavior
Movie posters being visible.

Screenshots
If applicable, add screenshots to help explain your problem.

Device (please complete the following information):

• OS: Ubuntu
• Version 18.4
• docker container

Additional context
Add any other context about the problem here.

[jorenn92]

Hey, thanks for your report.

Maintainerr needs internet access to fetch images from tmdb. Is it possible that Maintainerr is running in a subnet without an outside connection?

[X-static]

Hi. Does seem to be the case. I just pinged google.com inside the container console and reached it successfully.

[jorenn92]

That's odd, could you check the network requests in your browser's developer console? Each image should be a server request. What's the response & response code?

Are you using the amd64(x86) version of the images? Or are you running an arm device?

If you're using the amd64 version, you could temporarily use the 'develop' docker tag, there's an unreleased fix that adds the UI's error logs to the container output. There's no database changes yet, so if you're currently running latest, you could change it back afterward without issues. (staying on develop could cause issues in the future though)

[X-static]

I'm using amd64. I tried the develop tag but no changes.

I quickly checked the developer console on my PC and the images have a failed to load resource error with the code ERR_CONNECTION_RESET if I recall correctly. Is there anything you'd like me should check when I'm back on PC?

[jorenn92]

Hey, sorry for this late reply.

You could try to copy the URL of an image request and paste it in another browser tab. Do you see the image or does that also fail?
Does this happen on each device you try to open Maintainerr's UI?

[X-static]

Not sure if this is just the console or the actual URL, but the special characters are showing as the encoded hexadecimal equivalent.

I only tested on a windows pc and android phone, but is happening on both.

[jorenn92]

That's the correct URL, The encoded chars in the dev tool are normal.
When you copy the full URL and paste it in a new browser window, do you see the image?

You could also try to only copy the value after 'url=' from this url, that's the call the server actually makes to tmdb (this is the real image source). Does that return an image?

[X-static]

The full URL doesn't work. The part after 'url=' and before '&w=1080&q=75' works if I replace the encoded characters with the correct ones.

[jorenn92]

I'm not sure if this could be a possible solution, but i implemented the change documented in https://nextjs.org/docs/app/api-reference/components/image#remotepatterns. Maintainerr was still using the 'domains' approach, but that'll be deprecated in NextJS 14.

Could you try the develop image and report back? Thanks in advance!

If this doesn't work, I'm actually at a loss. This is something on NextJS's side (I just use their image optimization/caching mechanism), but I can't figure out what's going wrong.

[X-static]

I tried the develop image and still no pictures.

[jorenn92]

That's too bad. You mentioned earlier that you didn't receive a response for the URL when used in your browser, pasting this URL in a new tab should return an image: http://192.168.1.21:8154/_next/image?url=https://image.tmdb.org/t/p/w300_and_h450_face/u3G2gF7M9dmH4Vcs54PUjieOi0C.jpg&w=1920&q=75

If it doesn't, you could try to update to the latest develop image again. I added a console log line that should contain the error message. I don't really know what to try anymore… It's hard to diagnose when I can't replicate it myself.

[jorenn92]

This addresses a Next/image issue observed in certain installations, where the server crashes and instantly reboots upon requesting a cached image. Although the exact trigger is not definitively identified, I have introduced a solution that allows users to configure the image caching behavior (078625e). By disabling this setting, images will now be sourced directly from tmdb rather than being cached by next/image.

[X-static]

It's working now. Thank you so much!

[X-static]

You might need to do the same thing here. Inside the collection it's working.

[jorenn92]

Oh i see, thanks for the heads up!

[jorenn92]

Fixed in 1.6.10