Recently I successfully installed Backlight on my Synology 923 NAS. Using everything at default settings and using the latest Lightroom Publisher Plug-in 8.0.2 I was able to easily publish an album. Image and thumbnails worked as expected when using the default album/set that came preinstalled. I also was able to use the Backlight Publisher to create and publish a second album (i.e. not Lightroom). All good.
Because this is an entirely new instance and I haven’t modified my existing web hosted site for YEARS, I decided it was time to dive into Kookaburra. So I created Templates for Albums, Album Sets and Page Templates using Kookaburra. Did them all as defaults. Didn’t change anything within those templates.
Next I went to lightroom and deleted the album I had published. I created a new album and selected the Kookaburra default. (And, yes, I realize I could have just changed the album within Lightroom with out deleting and republishing). I published. The album appeared. But no thumbnails. clicking on the missing thumbnail took me to photo page which was also missing. It showed the image description, but no image.
I’ve quickly run out of troubleshooting success. I used Backlight to go in to Publisher and assign the albums back to Default and everything then worked as expected (thumbnails and photos). So clearly it’s something with how I created the Kookaburra default album/set/pages.
Doing a search within the community didn’t seem to result in solutions, but maybe I’m searching incorrectly.
Are you able to inspect the page source and check the image src attribute values for the broken images? I’d like to know what the image paths look like.
Is this the detail you’re asking for, Matthew? The amount of detail is greater than I could paste (and maybe more than you need) so I’ve created a link that - hopefully - you can access.
You’ve got an http / https mismatch. If you visit your gallery using http, the images will load, because they also are referenced using http.
Problem is your site’s URLs are https, but referencing images by http. Probably a misconfiguration someplace on your NAS. @Ben might be able to suggest where to look for such a thing.
Thank you for the quick response, Matthew. I’ll wait to see if @Ben chimes in. For what it’s worth (and clearly ‘worth’ might be questionable where ChatGPT is concerned) ChatGPT had this response:
The likely issue is that Backlight/PHP on the NAS thinks the request is arriving as plain http, because Cloudflare Tunnel terminates HTTPS before forwarding to Synology. So Backlight generates image URLs with http://.
What to check next:
Backlight settings first
Look for any Site URL / Galleries URL / Publisher URL setting and make sure it is:
and that it routes to your NAS origin. If the tunnel service URL points to http://192.168.1.2``..., that may be okay, but Backlight may need a forwarded proto header.
Synology reverse proxy / Apache HTTPS awareness
The missing piece may be that PHP doesn’t know original visitor protocol was HTTPS. We may need a setting/header equivalent to:
X-Forwarded-Proto: https
or a Backlight env.php setting if TTG supports one.
For now, don’t change lots of things. First find every Backlight-configured URL and make sure none are http://.
I took a leap and in Backlight Settings I changed Company URL and Site URL to be https instead of http and that seemed to solve things. Whether that was what I should have done or whether that has broader implications, I’ll see if @Ben can confirm or recommend a better approach.
Yes, and further I made recommended modifications in Cloudflair so that SSL/TLS encryption mode is Full (Strict) and Edge Certificates are set to Always use HTTPS.
So I think this took care of it. As always, very much appreciate the support.
Now…time to dive deeply into how to fully leverage Kookaburra as I’ve been in a Pangolin world forEVER. Need to up my game where Kookaburra is concerned
Hi @scottblackman, that sounds like the right approach to me. I’d imagine that your site is still available directly on the Internet via IP address, so you’d want to run SSL all the way through to it, including via Cloudflare.
