Closed sloniupl closed 8 months ago
You should try the tag 5.0.0 instead. I don't think nightly has been updated correctly yet.
Can you check your developer console in your browser what is blocking the css and JS ? That smells like CSP.
In the mean time you can disable the new front-end by setting in your .env
:
LIVEWIRE_ENABLED=false
Thanks for quick reply, i was trying to set up image: lycheeorg/lychee:v5.0.0 and as you suggested LIVEWIRE_ENABLED=false in env but still not working. Interesting when i try to open it using the direct port for local network bypasing Nginx Proxy Manager looks like it is working but not via nginx proxy manager translation. This is how it looks when accessing directly via local ip:port :
Looks like i needed to add to my compose yaml file this option:
Now the page loads correctly but when i wan to open as a not logged user an album that is set to public and password protected i get this:
Hoho, I'll check that one.
BTW from the broken thumbnails, it seems that your APP_URL are not set properly or that you have LYCHEE_UPLOAD_URL=
left empty in your .env
.
Now it works correctly after i added
TRUSTED_PROXIES=*
Before it was not working as i was testing it from container ip:port and not the domain it is configured for that is specified in Nginx Proxy Manager. Now it loads correctly:
The only issue is that i can't access public albums that are password protected (if album is not password protected it works correctly):
On some lychee galleries that i host i had to also do fastcgi_param HTTPS on;
in manually /etc/nginx/nginx.conf as suggested here:
https://github.com/LycheeOrg/Lychee/issues/2106#issuecomment-1869746168
Despite already adding TRUSTED_PROXIES=*
in my compose yaml file.
After doing those two things my galleries started working with only the password protected issue that you are working on already.
Hope this info will help and maybe we can add fastcgi_param HTTPS on;
to nginx.conf
maybe we can add
fastcgi_param HTTPS on;
to nginx.conf
I'm not ruling it out, but certainly not adding it yet. That and the `TRUSTED_PROXIES=*" are workarounds, not solutions.
I'm using watchtower to update my containers and all containers of lychee (image: lycheeorg/lychee:latest) that i have are broken since update yesterday.
containers are starting correctly but the website is displayed like that (on every instance):
I did try to get it back to version v4.13.0 but it's only showing migrate website and not working also.
Any ideas what changed and why it's not working correctly now. Logs don't show anything wrong: