Closed pthoelken closed 4 months ago
Hello @pthoelken, the port 443 is not listening because you haven't added certificates, this is a guide how you can do that, after adding certificates restart docker compose and 443 will open.
This works for me, but opens another question from https://github.com/ONLYOFFICE/onlyoffice-owncloud/issues/480
I close this issue. Feel free to comment or reopen it if you got further questions.
Do you want to request a feature or report a bug? Bug report
What is the current behavior? Starting the Docker Environment with the docker-compose.yml below.
to use it in a ownCloud instance. The only thing what I changed was the https exposed port bc the ports was already blocked by another container.
I've started the enviroment and all actually all works fine but the https-site was not started in the onlyoffice-documentserver container. Just the 80 site. This is what you can see with the commands below.
netstat -tulpn
from the container onlyoffice-documentserver here you can see, that only 80 is started.Checks from owncloud instance to reach 80 and 443 to onlyoffice-documentserver
What is the expected behavior? 443 site on container onlyoffice-documentserver is not started. In this case I'm not able to use onlyoffice with ownCloud because ownCloud did not allow mixed connection types (ownCloud URL is HTTPS, onlyoffice URL would then be HTTP (this is mixed connection types))
Did this work in previous versions of DocumentServer? idk - I'm working with onlyoffice since today.
DocumentServer Docker tag: latest
Host Operating System: Debian 12 / Docker Engine