SOLVED: Blank images on library folders

[cantcurecancer]

Ok so not a big deal at all, but I just got my Jellyfin setup reinstalled via Docker on my headless Linux server and I noticed that the images for the libraries are blank. I can't figure out how to get the Jellyfin-generated images/collages to show up on the "Movies" and "TV" libraries. I'm guessing it's some dumb Linux permissions issue that I've overlooked. Here's what I've done so far:

• Applied permissions for all content/config folders that I'm aware of so that the jellyfin user and media group have full read/write access
  
• Refreshed metadata for all libraries several times, including the option to replace existing metadata
  
• Manually scanned all libraries multiple times
  
• Tried using the NFO option for metadata
  
• Reordered the priority of the image fetchers, metadata sources 
  
• Tried pretty much every metadata option under Admin dashboard > Libraries > Manage library
  
• Cleared browser cache
  
• Tried a different theme
  

This is happening both on web (Chrome) and on the Google TV Jellyfin app. Can't get the images to show up on these folders. Once I go into the "Movies" or "TV" libraries, the movies and shows have all the proper images and data, nothing looks missing or incorrect. Any ideas on what I could've missed or what I can do to troubleshoot this further? Below is an image that clearly shows the problem:


Thanks!

[Efficient_Good_5784]

• Tried a different theme
  

Try running Jellyfin without a theme. Those icons on your library are not blank. They look like custom made images that someone made for their theme.
Go into [dashboard --> general --> custom css code] and see if you are importing any custom theme. If so, delete the lines that do so and save the changes. Then reload the browser (and maybe rescan your libraries again) to see the changes.
Just remember to copy and paste the deleted code onto a separate document if you want to remember how to get back the current theme.

Also, I'm not sure if the custom theme you have running will allow this, but you should still be able to upload a custom image to your library folders in [dashboard --> libraries --> (3-dot menu on libraries "edit images")]

[cantcurecancer]

• Tried a different theme
  

Try running Jellyfin without a theme. Those icons on your library are not blank. They look like custom made images that someone made for their theme.
Go into [dashboard --> general --> custom css code] and see if you are importing any custom theme. If so, delete the lines that do so and save the changes. Then reload the browser (and maybe rescan your libraries again) to see the changes.
Just remember to copy and paste the deleted code onto a separate document if you want to remember how to get back the current theme.

Also, I'm not sure if the custom theme you have running will allow this, but you should still be able to upload a custom image to your library folders in [dashboard --> libraries --> (3-dot menu on libraries "edit images")]

Thanks for your response, but after following your steps and removing the custom CSS code for the theme, the libraries still have blank images. I cleared browser data and restarted the server after removing the theme to verify. I guess I could place my own images on the libraries, but I liked the auto-generated Jellyfin images for my libraries so I'm trying to make that work.

[TheDreadPirate]

If this is a fresh setup and the library is still scanning, it won't create the library images until the scan is complete. Is that the case here?

[cantcurecancer]

Figured it out and it of course was a dumb Linux permissions issue. I dived into the logs and I saw that there was a permission denied error message in there for some image. Went to the subfolder in question inside the cache folder and somehow the 'root' user was the owner and the jellyfin user didn't have permissions. I mistakenly thought that applying the correct permissions to the parent folder would apply to all its children, but not if root is the owner of that subfolder. Not sure why that happened, but after changing the owner and correcting the permissions, I did a refresh on the metadata and scanned the libraries, all good!