Error Updating and installing certificates

Hello everyone,

I just installed a fresh version of OnlyOffice Workspace Community-Edition on a Debian 12(.9) virtual machine.
I used the docker option for running all services.

So, the installation works fine without any errors.

But if I try to install a certificate I get an error:

How to reproduce:

  1. Take a clean installation of debian 12
  2. Download the installation script of onlyoffice workspace
  3. execute the script: bash ./workspace-install.sh -ism false
  4. Wait until installation has finished
  5. open your browser and navigate to the server-url
  6. fillout all necessary options
  7. go to settings → control → https
  8. try to install an own certificate

If I trie to update your onlyoffice workspace installation, I also get an error.

The installed docker version:

Client: Docker Engine - Community
Version: 29.0.3
API version: 1.52
Go version: go1.25.4
Git commit: 511dad6
Built: Thu Nov 20 16:45:02 2025
OS/Arch: linux/amd64
Context: default

Server: Docker Engine - Community
Engine:
Version: 29.0.3
API version: 1.52 (minimum version 1.44)
Go version: go1.25.4
Git commit: 1fa8a31
Built: Thu Nov 20 16:45:02 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v2.1.5
GitCommit: fcd43222d6b07379a4be9786bda52438f0dd16a1
runc:
Version: 1.3.3
GitCommit: v1.3.3-0-gd842d771
docker-init:
Version: 0.19.0
GitCommit: de40ad0

Best regards
OliKaa

Hello @OliKaa
Please reproduce the situation and record a video file. Once the situation is reproduced, please collect entire Community server and Control Panel logs folders. They’re located here:
/app/onlyoffice/CommunityServer/logs/
/app/onlyoffice/ControlPanel/logs/
Also please go to the host and show us the docker ps command output result.

One more thing. Is it possible to check whether LE certificate works correctly? This way we will check whether the issue is related to your own certificates or to HTTPS enablement in general. We need this additional information since on the test servers I haven’t faced issues with HTTPS enabling.