Cannot configure Document Editing Service address - NC13.0.2/OnlyOffice/nginx in docker

I just upgraded (reinstalled) NC13.0.2 including OnlyOffice and nginx using Docker. With my previosu installation (NC13.0.0) I managed to get OO running. But in this installation I am asked to enter the Document Editing Service Adress. How can I find that out?

I open the advanced option and enter the Server address for internal requests from the Document Editing Service. I get a message that the configuration has been updated, but no change is taking place.

Hello @rollanders, Document Editing Service Address is the address of your Document Server.

Please enter the address of the Document Server to the field Document Editing Service Address and save the settings. Try to open the file after that.

1 Like

Thank you. I reinstalled and did run the bash set_configuration.sh this time.
When opening the OnlyOffice configuration page the following settings was preset

Document Editing Service address - /ds-vpath/

Document Editing Service address for internal requests from the server -> http://onlyoffice-document-server/
Server address for internal requests from the Document Editing Service - > http://nginx-server/

Change the first window to https://cloud.mydomain.se/ds-vpath/

when saving I get an error - CommandRequest on check error: Error occurred in the document service: Error while downloading the document file to be converted.

I have made an issue report - see this issue https://github.com/ONLYOFFICE/docker-onlyoffice-owncloud/issues/18

@rollanders, please delete addresses for internal requests and do not use advanced settings section. Please see the attached screenshot.

Wen deleting and saving, the settings reappear and same error. Should I edit some configuration file?

Please specify is there is any firewall in your system enabled.

Specify also the exact OS of your server, so we can reproduce the mentioned issue.

Windows 10 - updated, no firewall except windows own, Chrome webbbrowser.
We can continue on https://github.com/ONLYOFFICE/docker-onlyoffice-owncloud/issues/18

Have you been able to reproduce this issue?