Hello,
Did you set an apache/nginx server?
You must configure them to correctly redirect the resource files like this
Alias /SOGo.woa/WebServerResources/
/usr/local/lib64/GNUstep/SOGo/WebServerResources/
Alias /SOGo/WebServerResources/
/usr/local/lib64/GNUstep/SOGo/WebServerResources/
Regards,
--
Quentin Hivert || Alinto || R&D Lead Developer
19 Quai Perrache 69002 Lyon
www.alinto.com
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of "Felix"
Sent: samedi 20 septembre 2025 08:32
To: [email protected]
Subject: [SOGo] significant problems with new install of SOGo nightly on
Rocky 9
Apologies in advance if this is not a place to ask for help with
installation / configuration of SOGo nightly. I can not find any other
resource and on GitHub, "Issues are disabled for the selected repository"
I have installed SOGo on metal on RockyLinux 9 using the nightlies (a fresh
update was pulled today). MariaDB is on ANOTHER host with tables created
using the SQL file mysql-utf8mb4.sql
sogod is running using the service file provided, and the log (turned on via
the debug section in sogo.conf) does not show any obvious errors related to
the empty database.
No matter WHAT I do, virtually all assets (css, images, etc) required for
proper running of SOGo are 404 and the app (while it runs) provides no
"style"
and the login page has unfilled template placeholders like {{ item.label }}
-- and no buttons, etc.
The problem seems to be that there is no SOGo.woa folder, but that the
required assets are ACTUALLY in /usr/lib64/GNUstep/SOGo/WebServerResources
while the main page for the app indicates it is likely trying to pull
relevant resources from /usr/lib64/GNUstep/SOGo.woa/WebServerResources
[ from the served page I see:
" <link
href="/SOGo.woa/WebServerResources/img/sogo.ico?lm=1758319824"
rel="shortcut icon" type="image/x-icon" />
<link href="/SOGo.woa/WebServerResources/css/theme-default.css?
lm=1758319824" rel="stylesheet" type="text/css" />
<link
href="/SOGo.woa/WebServerResources/css/styles.css?lm=1758319824"
rel="stylesheet" type="text/css" /> " ]
SOGo looks like the real deal(1) and I would gladly purchase a support
contract in the future, but I FIRST need to have some idea that I can get it
to work at *all* in any way. The PDF documentation is pretty good, but it
talks about LDAP authentication rather than authentication by DB and it also
does not surface any issues such as missing resources for pages ...
Before I can get endpoints for (cal,card}dav, surely I need to get the basic
page working.
By the way, I have ALSO tried running SOGo in a podman/distrobox container [
https://github.com/sonroyaalmerol/docker-sogo ] with the same issue of
"missing" resource files.
Does an admin user need to be created FIRST or am I missing some other
detail?
Thank you in advance for any possible help!
