On Mon, Sep 22, 2025 at 9:28 AM "Felix" <[email protected]> wrote:
> 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
>
The way I use SOGo, I did not create an independent database for it. I
already had a DB
that I was using to authenticate my users. I let SOGo to ride on this
database.
I created a VIEW that SOGo would use. I also let SOGO write its other
tables to this same DB.
How? You ask.
I use Exim as the MTA, along with some custom PHP scripts for managing
domains/users.
Nothing stops you from using PostfixAdmin to do the same if you use Postfix.
Let me know which one you prefer/use and I will help you with the complete
details of how to configure the DB,
and how to configure SOGo.
> 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" /> " ]
>
This is a small problem that you can fix in your Nginx/Apache configuration.
It's just the incorrect paths.
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 ...
>
Remember SOGo runs based on /etc/sogo/sogo.conf. You must configure
everything there - DB access details and user "Sources".
> 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?
>
You do not need any admin user for SOGo to work. Just your already existing
users.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]
