• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Plesk Sogo webinterface settings are ignored

bit

New Pleskian
Server operating system version
Debian 13.7
Plesk version and microupdate number
18.0.81 Update #2
Hi togehter,

Debian Server: 13.7
Plesk: 18.0.81 Update #2

We faced an issue with the settings in Plesk Sogo extentions webinterface settings.
 When we set in Sogo the "Maximum Amount of SOGo-Worker" form 3 to 12 it will be ignored.

We can see that with systemctl status sogo.service
After set to 12 worker and restart the Sogo daemon it still runs with 3 Worker:

sogo.service - SOGo is a groupware server
Loaded: loaded (/usr/lib/systemd/system/sogo.service; enabled; preset: enabled)
Active: active (running) since Wed 2026-10-21 08:05:04 CEST; 1min 26s ago
Invocation: d8953345001a4c95bc31346b598117ca
Docs: Installation and Configuration Guide
Process: 338508 ExecStart=/usr/sbin/sogod -WOWorkersCount ${PREFORK} -WOPidFile /run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log (code=exited, status=0/SUCCESS)
Main PID: 338517 (sogod)
Tasks: 4 (limit: 9272)
Memory: 47.4M (peak: 48M)
CPU: 746ms
CGroup: /system.slice/sogo.service
├─338517 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log
├─338519 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log
├─338520 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log
└─338521 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log


This leads in our case to a Sogo exception:
2026-10-21 05:50:48.402 sogod[239077:239077] EXCEPTION: <MySQL4CouldNotOpenChannelException: 0x56475952f770> NAME:NoMoreConnections REASON:cannot open a additional connection ! INFO:(null)

At another customer server we have the same situation.

regards,
Norman
 
Back
Top