08.10.25, 09:16 +0200, gluonman ([email protected]):
> I actually just caught onto that shortly before your reply. I kept
> researching and messing around with the nginx config, reviewing tons of
> examples online, and I started to get a creeping hunch that it probably
> isn't the nginx config that's been the problem, which may be why I've
> been confused about re-writing the config exactly the way it had been
> back when I briefly had it working, and yet I couldn't get it to work
> again. I finally caught a sogod error in running "systemctl status
> sogo," and so now I'm aware it isn't the nginx config, but sogo isn't
> actually running properly,
That was already clear from your last post.
> and now I've turned my attention toward
> figuring out why. It appears that the sogod service is running,
No, it isn't. And that's the problem.
> but
> with the following error:
>
> Oct 08 01:44:55 host.{REDACTED}.{TLD} systemd[1]: Starting sogo.service
> - LSB: SOGo server...
> Oct 08 01:44:56 host.{REDACTED}.{TLD} sogo[11780]: * Starting SOGo sogo
> Oct 08 01:44:56 host.{REDACTED}.{TLD} sogo[11851]: 2025-10-08
> 01:44:56.073 sogod[11851:11851] File NSDictionary.m: 671. In -
> [NSDictionary initWithContentsOfFile:] Contents of file '/etc/sogo/
> sogo.conf' does not contain a dictionary
> Oct 08 01:44:56 host.{REDACTED}.{TLD} sogo[11851]:
> <0x0x560409ae2410[SOGoStartupLogger]> Cannot read configuration from '/
> etc/sogo/sogo.conf'. Aborting
> Oct 08 01:44:56 host.{REDACTED}.{TLD} sogo[11780]: ...done.
> Oct 08 01:44:56 host.{REDACTED}.{TLD} systemd[1]: Started sogo.service -
> LSB: SOGo server.
sogod aborts because your sogo.conf is malformed.
Is the content of the file enclosed between '{' and '}'?
If that's not the problem, post your sogo.conf here. Someone will likely
spot the error.
--
Regards
mks
