Incomplete SSL Tutorial and Errors When Accessing Example After Deploying onlyoffice:8.2 with Docker

[ybg163yx]

Hello, I only found a "new topic" button on the official forum, but no place to ask a question directly. Therefore, I am posting my issue here.

Environment: Ubuntu 24.10 + Docker + onlyoffice/documentserver:8.2

While following the official tutorial (https://helpcenter.onlyoffice.com/installation/docs-community-install-docker.aspx) to deploy ONLYOFFICE Document Server, I encountered the following issues:

If SSL is enabled and configured as prompted, it also needs -p 443:443 to be specified, which was not mentioned in the tutorial.
After correctly configuring SSL, when using https://192.168.66.138 to test access with the example, it is not possible to create or download files, and an error occurs.
My deployment command:

sudo docker run -i -t -d -p 80:80 -p 443:443 --restart=always \
-v onlyoffice_logs:/var/log/onlyoffice \
-v onlyoffice_data:/var/www/onlyoffice/Data \
-v onlyoffice_lib:/var/lib/onlyoffice \
-v onlyoffice_db:/var/lib/postgresql \
-v onlyoffice_custom:/usr/share/fonts/truetype/custom \
-v onlyoffice_rabbitmq:/var/lib/rabbitmq \
-v onlyoffice_redis:/var/lib/redis \
--env-file=onlyoffice.env --name=onlyoffice onlyoffice/documentserver:8.2

[ybg163yx]

supplement
root@ubuntu20241:/var/snap/docker/common/var-lib-docker/volumes# cat onlyoffice.env JWT_SECRET=my_jwt_secret #DB_TYPE=mysql #DB_HOST=192.168.66.138 #DB_PORT=3306 #DB_NAME=onlyoffice #DB_USER=root #DB_PWD=123456 #REDIS_SERVER_HOST=192.168.66.138 #REDIS_SERVER_PORT=6379 #REDIS_SERVER_PASS=123456

[igwyd]

Hello @ybg163yx.

If SSL is enabled and configured as prompted, it also needs -p 443:443 to be specified, which was not mentioned in the tutorial.

This is specified in the command where we show how to run with https - Running ONLYOFFICE Docs using HTTPS.

After correctly configuring SSL, when using https://192.168.66.138/ to test access with the example, it is not possible to create or download files, and an error occurs.

Show please the error what you saw in the browser and the container logs.