Thank you for this hint. I changed the tmpl and add 301 redirect for root in the 00-default.ssl.conf and everything works.
-----Ursprüngliche Nachricht----- Von: Michael Hölzle <[email protected]> Gesendet: Montag, 30. August 2021 16:37 An: [email protected] <[email protected]> Betreff: Re: [SOGo] No css/image on login screen, white page/refresh sometimes helps Hi Michael, It looks like you are using iRedMail, if your are try using `/etc/nginx/templates/sogo.tmpl` over the subdomain one. and then restart `sogo`, `nginx` and for any cache `memcached` -- Hilsen / Regards Christian M. Jensen Den 30-08-2021 kl. 15:18 skrev [email protected]: > Attached you find the current nginx configuration files > > Kind regards, > Michael > > -----Ursprüngliche Nachricht----- > Von: Michael Hölzle <[email protected]> > Gesendet: Montag, 30. August 2021 09:43 > An: [email protected] > Betreff: Re: [SOGo] No css/image on login screen, white page/refresh > sometimes helps > > Hello > > Perhaps you should show us your proxy configuration (apache2 or nginx) > in order for us to provide any help. > > > Kind regards, > Christian Mack > > Am 27.08.21 um 17:39 schrieb [email protected]: >> Hello all, >> >> I'm new in SOGo and like to replace zimbra systems with it. >> >> The system is running on a 4Core,8GB vServer. Only Nextcloud is also > running >> on the same box. At the moment I only have two active mail users and >> one active nextcloud user. >> >> In the morning I start a browser and enter the SOGo-Login page and >> see a page without any css/images (you can see it in the attached screenshot). >> Pressing F5 (refresh) a few times will bring the "right" content. >> After logging in, and switching to calendar or contacts or email I >> only get a blank page. Sometimes it works, sometimes not. >> >> When I open the image placeholder in a new tab, I get the following > message: >> Resource not found >> Name: sogo-full.svg >> Languages: (img, img) >> ResourceManager: <0x0x55cc55f25840[WEResourceManager]:> >> >> After restarting the server (or sogo and nginx) the issue seems to be >> gone for a while. >> >> It feels like a caching problem on the server side. >> >> Can someone point me to the right direction how to eliminate this issue? >> Which logs can I use to find any helpful information's? >> >> Michael >> -- [email protected] https://inverse.ca/sogo/lists -- [email protected] https://inverse.ca/sogo/lists
