yummiweb
September 2, 2025, 3:43pm
1
SOGO - Customizing theme and logo - Oops…
I just tried to follow the new instructions for customizing SOGo:
# ns8-sogo
This module intends to istall the SOGo groupware : https://www.sogo.nu/
## Install
Instantiate the module with:
add-module ghcr.io/nethserver/sogo:latest 1
The output of the command will return the instance name.
Output example:
{"module_id": "sogo1", "image_name": "sogo", "image_url": "ghcr.io/nethserver/sogo:latest"}
## Get the configuration
You can retrieve the configuration with
api-cli run get-configuration --agent module/sogo1
Original zeigen
I followed the steps exactly as stated, using the specified template as “custom_theme.js” and my own “logo-full.svg” (owner: sogo1). Unfortunately, after restarting SOGo, I always get a “Bad Gateway” error in the browser.
So I undid everything and removed the files – but after restarting SOGo, I still get a “Bad Gateway” error.
This is an excerpt from the service status:
/home/sogo1/.config/state# runagent -m sogo1 systemctl --user status sogo
Sep 02 17:37:38 neth81 systemd[913]: Starting sogo.service - Podman sogo.service…
How do I get SOGo running again without having to roll back to the last snapshot?
Regards Yummiweb
yummiweb
September 2, 2025, 4:02pm
2
Apparently, the SOGo (or another component) has recovered. SOGo is accessible again.
yummiweb
September 2, 2025, 4:38pm
3
I’ve gone through the entire theming process again, and it doesn’t work.
The service initially starts without errors, but it seems to restart after a few seconds.
The status output:
Here are two examples with the details:
Sep 02 18:28:51 neth81 systemd[913]: Starting sogo.service - Podman sogo.service…
Sep 02 18:29:19 neth81 systemd[913]: Starting sogo.service - Podman sogo.service…
The container seems to be constantly restarting.
Has anyone ever managed to get the changes made according to the instructions above to work correctly?
Perhaps a typo in the examples? For example, at one point, sogo2 is mentioned instead of sogo1:
(which doesn’t matter in the context, and these lines only serve to determine the position for insertion anyway)
Regards Yummiweb
yummiweb
September 2, 2025, 5:13pm
4
The cause has been identified and is described here:
f you strictly follow the instructions:
theming doesn’t work.
Instead, SOGo ends up in a restart loop.
The error is here:
The files for the theme custom_theme.js and the logo logo-full.svg to customize the SOGo instance sogo1 need to be located in /home/sogo1/.config/state and owned by user sogo1.
or here:
volume %S/state/sogo-full.svg:/usr/lib/GNUstep/SOGo/WebServerResources/img/sogo-full.svg:Z ${SOGO_SERVER_IMAGE}
At the beginning, it mentions “logo-full.svg”, but later it refers to “…
This thread may therefore be deleted.
1 Like