My SOGo 5.8.0 is generating a wrong URL for Main.js:
<script type=“text/javascript” src=“/SOGo?ReturnUrl=%2Fwmidentity%2Fconnect%2Fauthorize%2Fcallback%3Fresponse_mode%3Dform_post%26response_type%3Dcode%2520id_token%26redirect_uri%3Dhttps%253A%252F%252Fwebmail.woa/WebServerResources/js/Main.js?lm=1672013019"></script>

And that URL returns a 404 error. And the page goes blank.

The problem can be solved restarting SOGo but I'm wondering why is it happening?

It's also happening with the logo:
<img src="/SOGo?ReturnUrl=%2Fwmidentity%2Fconnect%2Fauthorize%2Fcallback%3Fresponse_mode%3Dform_post%26response_type%3Dcode%2520id_token%26redirect_uri%3Dhttps%253A%252F%252Fwebmail.woa/WebServerResources/img/sogo-full.svg?lm=1672013019" class="md-margin" alt="*" />

Other resources are being loaded fine!

After restarting SOGo, it loads the js fine, as follow:
<script data-ch="3" type="text/javascript" src="/SOGo.woa/WebServerResources/js/Main.js?lm=1672013019"></script>

I'm loading SOGo using a nginx reverse proxy and accessing it with the URL: https://webmail.domain.com/SOGo

This is how Im setting the nginx reverse proxy:

location ^~ /SOGo {

proxy_pass http://127.0.0.1:20000;

proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;

proxy_set_header x-webobjects-server-port $server_port;
proxy_set_header x-webobjects-server-name $host;
proxy_set_header x-webobjects-server-url  https://$host;

proxy_set_header x-webobjects-server-protocol HTTP/1.0;

proxy_busy_buffers_size   64k;
proxy_buffers             8 64k;
proxy_buffer_size         64k;

}

In other server with the same SOGo version, I experienced the same problem but this one has the URL SOGo?_task=mail&_action=refresh.woa/WebServerResources/css/styles.css?lm=1672013019

that "_task=mail&_action=refresh" string is used by Roundcube (also running in the same server).

This problem is happening randomly, a SOGo restart will fix it but it will come back later.

Thank you!