Thanks again and others for your help.

Biggy for me was thanks to your replies I did some comparisons where I found on Rocky Linux SOGo was set to look at /usr/lib/sogo using the past server (CentOS 6) and the github examples. On Rocky Linux the correct path /usr/lib64/sogo needed to be modified - all came up in an instant.

Key was in /etc/httpd/conf.d/SOGo.conf:

Directory path references for /usr/lib/GNUstep/SOGo

needed to be:

Alias /SOGo.woa/WebServerResources/ \
      /usr/lib64/GNUstep/SOGo/WebServerResources/
Alias /SOGo/WebServerResources/ \
      /usr/lib64/GNUstep/SOGo/WebServerResources/

<Directory /usr/lib64/GNUstep/SOGo/>

All so very simple in the end.

Thanks again and please mark this case/ticket/request as closed.... or advise me on how to do that from here if that is how it works?

I do have another question but will ask it in another config question e-mail.

On 7/5/25 16:38, qhivert ([email protected]) wrote:
Hello,
You should check your browser console to see where it requests the static file 
like this
GET 
https://demo.sogo.nu/SOGo.woa/WebServerResources/css/styles.css?lm=1746518478

And then check the url is correctly delivered to the static file by your 
apache/nginx config, something like this -> 
https://github.com/Alinto/sogo/blob/bc4c9ba0e64b8745064c040bf98c19456680be8b/.devcontainer/conf/httpd/httpd.conf#L566

Beware that your static files path depends on your OS, but will end with 
"GNUstep/SOGo/WebServerResources".

Cheers

--

As always, I remain at your service.

Kindest Regards,
David.M.Clark (Senior Linux/UNIX Consultant)
Company: Davrom Consulting (ABN: 81096990804)
Mobile: 0418763124
Website: http://davrom.com
Specialising in: Rocky Linux, RedHat/CentOS, Ubuntu, SCO, shell/PHP
=-----------------------------------------------------------------=
Please note: Any e-mail communication bearing this signature is
for the exclusive purpose of the sender and is not for publication
without the expressed permission of the sender or respective
sender's organisation.
=-----------------------------------------------------------------=

Reply via email to