Lychee: Thumbnails and images not displaying
I have an install on a TrueNAS system. Installed with: this
I am running the latest master (4.5.0). I have been successful in uploading images but my front page displays like:
And if I do into unsorted, I see nothing:
Looking in the console logs after entering unsorted, I do see an error:
But no errors on the server side.
Diagnostics
Diagnostics
-------
Warning: Dropbox import not working. dropbox_key is empty.
Info: Latest version of PHP is 8.1
Warning: Default timezone not properly set; you might experience strange results when importing photos without explicit EXIF timezone
System Information
--------------
Lychee Version (git): master (e0c2c8c) - Data not in Cache
DB Version: 4.5.0
composer install: --no-dev
APP_ENV: production
APP_DEBUG: true
System: FreeBSD
PHP Version: 8
PHP User agent: Lychee/4 (https://lycheeorg.github.io/)
Timezone: UTC
Max uploaded file size: 16G
Max post size: 16G
Max execution time: 3600
MySQL Version: 10.3.32-MariaDB
Imagick: 1
Imagick Active: 1
Imagick Version: 1692
GD Version: 2.3.1
[Request space usage]()
Config Information
--------------
version: 040500
check_for_updates: 0
sorting_Photos_col: taken_at
sorting_Photos_order: ASC
sorting_Albums_col: max_taken_at
sorting_Albums_order: ASC
imagick: 1
skip_duplicates: 0
small_max_width: 0
small_max_height: 360
medium_max_width: 1920
medium_max_height: 1080
lang: en
layout: 1
image_overlay_type: desc
default_license: none
compression_quality: 90
full_photo: 1
delete_imported: 0
Mod_Frame: 1
Mod_Frame_refresh: 30
thumb_2x: 1
small_2x: 1
medium_2x: 1
landing_page_enable: 0
landing_owner: John Smith
landing_title: John Smith
landing_subtitle: Cats, Dogs & Humans Photography
landing_facebook: https://www.facebook.com/JohnSmith
landing_flickr: https://www.flickr.com/JohnSmith
landing_twitter: https://www.twitter.com/JohnSmith
landing_instagram: https://instagram.com/JohnSmith
landing_youtube: https://www.youtube.com/JohnSmith
landing_background: dist/cat.jpg
site_title: BKDS
site_copyright_enable: 1
site_copyright_begin: 2022
site_copyright_end: 2022
additional_footer_text:
display_social_in_gallery: 0
public_search: 0
SL_enable: 0
SL_for_admin: 0
public_recent: 0
recent_age: 1
public_starred: 0
downloadable: 0
photos_wraparound: 1
map_display: 0
zip64: 1
map_display_public: 0
map_provider: Wikimedia
force_32bit_ids: 1
map_include_subalbums: 0
update_check_every_days: 3
has_exiftool: 0
share_button_visible: 0
import_via_symlink: 0
has_ffmpeg: 0
location_decoding: 0
location_decoding_timeout: 30
location_show: 1
location_show_public: 0
rss_enable: 0
rss_recent_days: 7
rss_max_items: 100
prefer_available_xmp_metadata: 0
editor_enabled: 1
lossless_optimization: 0
swipe_tolerance_x: 150
swipe_tolerance_y: 250
local_takestamp_video_formats: .avi|.mov
log_max_num_line: 1000
unlock_password_photos_with_url_param: 0
nsfw_visible: 1
nsfw_blur: 0
nsfw_warning: 0
nsfw_warning_admin: 0
map_display_direction: 1
album_subtitle_type: oldstyle
upload_processing_limit: 4
public_photos_hidden: 1
new_photos_notification: 0
legacy_id_redirection: 1
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (10 by maintainers)
Could you access your SQL database via the CLI and delete that photo from the DB manually via
DELETE FROM "photos" WHERE id = 'FMo4_mXNeWHPv7Lp-Wvqnl8Q'?Then check whether everything works again. I guess it should. After that, try to re-upload the photo again. If the error re-appears, have another look in the logs.
Found the problematic entry. The photo with ID
FMo4_mXNeWHPv7Lp-Wvqnl8Qis the reason. This photo hasThis should not happen. At least the original must be there even if the back-end was not able to create the other size variants due to an unsupported file type. So the question is what is so special about photo
FMo4_mXNeWHPv7Lp-Wvqnl8Q?