Gokux

Yes, I found that too. I have also adapted the template accordingly with the new "FTLCONF_ " variables. They also work, but in the end it had no effect on the crash problem. I didn't want to downgrade yet. But it might help; this Docker ran for years without any problems. Let's see what else I can find this weekend

I can confirm that. After starting, the container runs for a few hours and then suddenly hangs in the reboot cycle. Funnily enough, if it was switched off for a few hours, I can start it again, but then it only runs again for a few hours.

Hello together I wanted to ask if someone has installed the Pico CMS addon in their Nextcloud Docker and knows how to configure Nginx correctly? The "normal" configurations for Nextcloud Pico CMS and Nginx don't work. Thanks a lot!

I have been using Unraid for almost 4 years. At that time it was a relatively spontaneous decision (Synology vs. Unraid). I just started with NAS functions. Now I have a firewall, media VM and many dockers (Emby, Lets Encrypt, NextCloud etc.) and everything works just fine and fast and updates always work without problems. Thanks for your work and many more birthdays!

I was a little bit surprised, because on Apache virtual hosts, it was never a "problem". I have searched around and found this. So I took just the first part in my site-confs [...] location / { proxy_pass https://192.168.0.100:8920/; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $remote_addr; } [...] and it seems to work.

This Plugin works like a charm , but I have one question: When I connect from my external URL to my application (like emby), the application get only the IP «172.17.0.2 » at every online user, and not the real IP. Is this normal? Thanks and happy new year.