Activating SOGo later: Unauthorized

muhlba91 · 2025-03-31T16:31:56+00:00

Hi,

until now, I have run mailcow with SKIP_SOGO=y due to resource constraints.
Today, I tried to enable SOGo by setting SKIP_SOGO=n and restarting mailcow.

It seems as if SOGo doesn’t get configured properly or if I missed something (probably pretty obvious) because when trying to login I receive a 403 Unauthorized error. The SOGo container doesn’t really log anything useful.

Does anyone have ideas on how SOGo can be enabled afterward?

esackbauer · 2025-03-31T16:37:26+00:00

Did you properly restart your mailcow afterwards?

docker compose down
docker compose up -d

Just restarting is not enough.
You need to do it with docker compose or else the configuration change is not applied.

muhlba91 · 2025-03-31T16:43:01+00:00

Yes, multiple times by now with no effect.

Is there a way to increase the log level for the SOGo container?
The SOGo’s container logs are not really useful in this case:

sogo-mailcow-1  | 2025-03-31 16:40:34,517 INFO Set uid to user 0 succeeded
sogo-mailcow-1  | 2025-03-31 16:40:34,519 INFO supervisord started with pid 1
sogo-mailcow-1  | 2025-03-31 16:40:35,524 INFO spawned: 'processes' with pid 7
sogo-mailcow-1  | 2025-03-31 16:40:35,531 INFO spawned: 'syslog-ng' with pid 8
sogo-mailcow-1  | 2025-03-31 16:40:35,537 INFO spawned: 'bootstrap-sogo' with pid 9
sogo-mailcow-1  | Uptime: 0  Threads: 2  Questions: 1  Slow queries: 0  Opens: 17  Open tables: 10  Queries per second avg: 0.000
sogo-mailcow-1  | DB schema is 27012025_1555
sogo-mailcow-1  | [2025-03-31T16:40:35.592046] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!;
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 syslog-ng[8]: syslog-ng starting up; version='3.38.1'
sogo-mailcow-1  | patching file /usr/lib/GNUstep/SOGo/Templates/UIxTopnavToolbar.wox
sogo-mailcow-1  | Syncing web content with named volume
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: version 5.11.2 (build @2bb892454cf4 202503240145) -- starting
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: vmem size check enabled: shutting down app when vmem > 384 MB. Currently at 88 MB
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6525fa30[SOGoProductLoader]> SOGo products loaded from '/usr/lib/GNUstep/SOGo':
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6525fa30[SOGoProductLoader]>   Contacts.SOGo, MailerUI.SOGo, Appointments.SOGo, AdministrationUI.SOGo, MainUI.SOGo, ActiveSync.SOGo, CommonUI.SOGo, Mailer.SOGo, ContactsUI.SOGo, MailPartViewers.SOGo, SchedulerUI.SOGo, PreferencesUI.SOGo
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: All products loaded - current memory usage at 95 MB
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> listening on 0.0.0.0:20000
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> watchdog process pid: 9
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x79bcefa1f460[WOWatchDogChild]> watchdog request timeout set to 30 minutes
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> preparing 20 children
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 48
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 49
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 50
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 51
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 52
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 53
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 54
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 55
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 56
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 57
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 58
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [51]: <0x0x56aa6525ce90[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 59
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 60
sogo-mailcow-1  | Mar 31 16:40:35 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 61
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 62
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [52]: <0x0x56aa654b1fb0[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 63Mar 31 16:40:36 sogod [56]: <0x0x56aa6525cdc0[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 64
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [50]: <0x0x56aa6525ce90[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [48]: <0x0x56aa6525ce90[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [55]: <0x0x56aa6525cdc0[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 65
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 66
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [54]: <0x0x56aa6525ce90[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [59]: <0x0x56aa653c01d0[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [57]: <0x0x56aa6525ce90[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [53]: <0x0x56aa653a3f10[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [9]: <0x0x56aa6528f040[WOWatchDog]> child spawned with pid 67
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [49]: <0x0x56aa65286500[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [58]: <0x0x56aa653c01d0[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [60]: <0x0x56aa6525ce90[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [63]: <0x0x56aa6525ce00[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [61]: <0x0x56aa654b1fb0[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [64]: <0x0x56aa6525ce90[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [62]: <0x0x56aa65247c40[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [65]: <0x0x56aa6525ce90[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [66]: <0x0x56aa653c01d0[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | Mar 31 16:40:36 85469bed8ef8 sogod [67]: <0x0x56aa6525ce90[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow-1  | 2025-03-31 16:40:37,272 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
sogo-mailcow-1  | 2025-03-31 16:40:37,272 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
sogo-mailcow-1  | 2025-03-31 16:40:37,272 INFO success: bootstrap-sogo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
sogo-mailcow-1  | Mar 31 16:41:37 85469bed8ef8 sogod [67]: <0x0x56aa65230670[SOGoCache]> Cache cleanup interval set every 900.000000 seconds
sogo-mailcow-1  | Mar 31 16:41:37 85469bed8ef8 sogod [67]: <0x0x56aa65230670[SOGoCache]> Using host(s) 'memcached' as server(s)
sogo-mailcow-1  | Mar 31 16:41:37 85469bed8ef8 sogod [67]: [WARN] <0x0x79bcefa40bc0[WOxElemBuilder]> could not locate builders: WOxExtElemBuilder,WOxExtElemBuilder
sogo-mailcow-1  | Mar 31 16:41:37 85469bed8ef8 sogod [67]: mailcow-watchdog-mailcow-1.mailcow_mailcow-network "GET /SOGo.index/ HTTP/1.1" 200 2581/0 0.116 - - 4M - 11
sogo-mailcow-1  | Mar 31 16:41:38 85469bed8ef8 sogod [67]: 172.18.0.4 "GET /SOGo/so HTTP/1.0" 302 0/0 0.027 - - 384K - 11
sogo-mailcow-1  | Mar 31 16:41:38 85469bed8ef8 sogod [67]: 172.18.0.4 "GET /SOGo/so/ HTTP/1.0" 403 12/0 0.003 - - 0 - 12
sogo-mailcow-1  | Mar 31 16:41:39 85469bed8ef8 sogod [67]: 172.18.0.4 "GET /SOGo/so/ HTTP/1.0" 403 12/0 0.002 - - 0 - 12
sogo-mailcow-1  | Mar 31 16:41:39 85469bed8ef8 sogod [67]: 172.18.0.4 "GET /SOGo/so/ HTTP/1.0" 403 12/0 0.002 - - 0 - 12

esackbauer · 2025-03-31T16:55:52+00:00

Which mailcow version is installed?

muhlba91 · 2025-03-31T16:59:13+00:00

2025-03a; so the newest one.

esackbauer · 2025-03-31T17:01:38+00:00

and you are logging in via mail.yourdomain.de, without /sogo behind that?

muhlba91 · 2025-03-31T17:12:27+00:00

Yes, I am logging in with mail.domain.com using a mailbox user, but I disabled the automated forwarding to SOGo in the user’s settings. On the user dashboard, I clicked on Webmail.

Partial success!
I just tried setting this to enabled, and suddenly, it works. Now, when I disable this setting again and click Webmail in the user dashboard, it also works without problems!

However, any other user does not work…
So, I guess the auto-redirect performs some “magic” that authorizes the user in SOGo.

esackbauer · 2025-03-31T17:16:03+00:00

muhlba91 So, I guess the auto-redirect performs some “magic” that authorizes the user in SOGo.

Yes authorization is only possible via mailcow UI, since the latest update.
Clearing browser cache might also help. And of course I guess you must enable “Direct Access in SOGo” for each user.
I don’t know if this setting is still there, I am still on 2025-02.

muhlba91 · 2025-03-31T17:57:26+00:00

As far as I can tell, each user has only the option Direct forwarding to SOGo (After logging in, the user is automatically redirected to SOGo).

Enabling this once and logging in, the user performs an auto-redirect after logging into Mailcow to SOGo.
After a redirect happens once, I can disable this setting, and SOGo login also works.