[GH-ISSUE #96 ] &#34;Download failed&#34; after upgrade to onlyoffice - unable to verify the first certificate #52

Author

Owner

@dmkash commented on GitHub (Jul 13, 2018):

I am running into the same problem while setting up local virtual machines in our development environment. For our development virtual machines we use the .test TLD, so need to use self-signed certificates.

The ONLYOFFICE Document Server has been installed on a CentOS 7 virtual machine following the directions here: https://helpcenter.onlyoffice.com/server/linux/document/linux-installation-centos.aspx

I tried adding NODE_TLS_REJECT_UNAUTHORIZED=0 to the /etc/onlyoffice/documentserver/supervisor/onlyoffice-documentserver-docservice.ini but this didn't work, either. I'm seeing the exact same error in /var/log/onlyoffice/documentserver/docservice/out.log as the OP:

[2018-07-13 14:50:22.799] [ERROR] nodeJS - postData error: docId = 2_2_;url = https://testserver.ourdomain.test/path/to/document;data = {"key":"2_2_","status":1,"users":["1"],"actions":[{"type":1,"userid":1}]}
Error: self signed certificate
    at TLSSocket.<anonymous> (_tls_wrap.js:1105:38)
    at emitNone (events.js:106:13)
    at TLSSocket.emit (events.js:208:7)
    at TLSSocket._finishInit (_tls_wrap.js:639:8)
    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)

@dmkash commented on GitHub (Jul 13, 2018): I am running into the same problem while setting up local virtual machines in our development environment. For our development virtual machines we use the .test TLD, so need to use self-signed certificates. The ONLYOFFICE Document Server has been installed on a CentOS 7 virtual machine following the directions here: https://helpcenter.onlyoffice.com/server/linux/document/linux-installation-centos.aspx I tried adding `NODE_TLS_REJECT_UNAUTHORIZED=0` to the /etc/onlyoffice/documentserver/supervisor/onlyoffice-documentserver-docservice.ini but this didn't work, either. I'm seeing the exact same error in /var/log/onlyoffice/documentserver/docservice/out.log as the OP: ``` [2018-07-13 14:50:22.799] [ERROR] nodeJS - postData error: docId = 2_2_;url = https://testserver.ourdomain.test/path/to/document;data = {"key":"2_2_","status":1,"users":["1"],"actions":[{"type":1,"userid":1}]} Error: self signed certificate at TLSSocket.<anonymous> (_tls_wrap.js:1105:38) at emitNone (events.js:106:13) at TLSSocket.emit (events.js:208:7) at TLSSocket._finishInit (_tls_wrap.js:639:8) at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38) ```

kerem commented

Author

Owner

@agolybev commented on GitHub (Jul 16, 2018):

Hi Dana, try turning off validating certificate by Document Server. Set services.CoAuthoring.requestDefaults.rejectUnauthorized=false in /etc/onlyoffice/documentserver/defaults.json file and restart documentserver serviceis with supervisorctl restart all.

@agolybev commented on GitHub (Jul 16, 2018): Hi Dana, try turning off validating certificate by Document Server. Set `services.CoAuthoring.requestDefaults.rejectUnauthorized=false` in `/etc/onlyoffice/documentserver/defaults.json` file and restart documentserver serviceis with `supervisorctl restart all`.

kerem commented

Author

Owner

@inpos commented on GitHub (Aug 24, 2018):

Unfortunately, node.js don't use system ca-certs and this issue can't be fixed by adding local CA cert to system bundle. Workaround by @agolybev work, but breaks SSL security due to allow connections to unauthorized ssl servers.

@inpos commented on GitHub (Aug 24, 2018): Unfortunately, node.js don't use system ca-certs and this issue can't be fixed by adding local CA cert to system bundle. Workaround by @agolybev work, but breaks SSL security due to allow connections to unauthorized ssl servers.

kerem commented

Author

Owner

@thomaswollburg commented on GitHub (Sep 26, 2018):

The workaround does work, but pretty pretty please update your documentation as I have tried all -e SSL_VERIFY_CLIENT="off" -e NODE_TLS_REJECT_UNAUTHORIZED=0 and what not to make this work. Can I invoice these useless hours of frustration somewhere? Even set up chain file and gave it the recommend name and everything. Nothing helped here.

@thomaswollburg commented on GitHub (Sep 26, 2018): The workaround does work, but pretty pretty please update your documentation as I have tried all -e SSL_VERIFY_CLIENT="off" -e NODE_TLS_REJECT_UNAUTHORIZED=0 and what not to make this work. Can I invoice these useless hours of frustration somewhere? Even set up chain file and gave it the recommend name and everything. Nothing helped here.

kerem commented

Author

Owner

@ibnpetr commented on GitHub (Sep 26, 2018):

@thomaswollburg
Next version of the DocumentServer container will include node.js v8, it does use system CA bundle, you will be able to import your certificates without having to disable verification.

@ibnpetr commented on GitHub (Sep 26, 2018): @thomaswollburg Next version of the DocumentServer container will include node.js v8, it does use system CA bundle, you will be able to import your certificates without having to disable verification.

kerem commented

Author

Owner

@changchichung commented on GitHub (Oct 30, 2018):

@ibnpetr is there any schedule for next release ?

@changchichung commented on GitHub (Oct 30, 2018): @ibnpetr is there any schedule for next release ?

kerem commented

Author

Owner

@skuep commented on GitHub (Jan 15, 2019):

@ibnpetr
I am curious, are you already using node v8? When I execute the following in the onlyoffice docker container, I get:

docker exec <id> node -v
v8.14.0

However I am having the exact same issues as above. Also tried every workaround given above.

@skuep commented on GitHub (Jan 15, 2019): @ibnpetr I am curious, are you already using node v8? When I execute the following in the onlyoffice docker container, I get: `docker exec <id> node -v` `v8.14.0` However I am having the exact same issues as above. Also tried every workaround given above.

kerem commented

Author

Owner

@mrwormo commented on GitHub (Jun 26, 2019):

Hi,
I'm using the latest docker image with Traefik as reverse proxy, and i have the same problem.

The trick to turning off validating certificate by Document Server works great :

Set services.CoAuthoring.requestDefaults.rejectUnauthorized=false in /etc/onlyoffice/documentserver/defaults.json file and restart documentserver serviceis with supervisorctl restart all.

But how can i modify the default.json when the container starts ? services.CoAuthoring.requestDefaults.rejectUnauthorized seems to not be modified by an environment variable (https://github.com/ONLYOFFICE/Docker-DocumentServer#available-configuration-parameters).

@mrwormo commented on GitHub (Jun 26, 2019): Hi, I'm using the latest docker image with Traefik as reverse proxy, and i have the same problem. The trick to turning off validating certificate by Document Server works great : > Set `services.CoAuthoring.requestDefaults.rejectUnauthorized=false` in `/etc/onlyoffice/documentserver/defaults.json` file and restart documentserver serviceis with `supervisorctl restart all`. But how can i modify the default.json when the container starts ? `services.CoAuthoring.requestDefaults.rejectUnauthorized` seems to not be modified by an environment variable (https://github.com/ONLYOFFICE/Docker-DocumentServer#available-configuration-parameters).

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Jun 26, 2019):

@mrwormo Hi, you're are right, not all options from default.json can be configured by params.
But you can use something like this after starting container

docker exec -it containerID /var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false'

(I didn't check this exact command, but you should get an idea

@ShockwaveNN commented on GitHub (Jun 26, 2019): @mrwormo Hi, you're are right, not all options from `default.json` can be configured by params. But you can use something like this after starting container ``` docker exec -it containerID /var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' ``` (I didn't check this exact command, but you should get an idea

kerem commented

Author

Owner

@mrwormo commented on GitHub (Jun 27, 2019):

Hi @ShockwaveNN,
This command works just fine. Many thx !
Now i need to run the command when the container starts. I tried to put this line at the end of the Docker-compose.yml, but it doesn't work.
I continue to search a solution to automate this...

@mrwormo commented on GitHub (Jun 27, 2019): Hi @ShockwaveNN, This command works just fine. Many thx ! Now i need to run the command when the container starts. I tried to put this line at the end of the Docker-compose.yml, but it doesn't work. I continue to search a solution to automate this...

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Jun 27, 2019):

@mrwormo I think there is no elegant way to use this command witho Docker Compose, you can modify https://github.com/ONLYOFFICE/Docker-DocumentServer/blob/master/run-document-server.sh to add this command and rebuild image locally

@ShockwaveNN commented on GitHub (Jun 27, 2019): @mrwormo I think there is no elegant way to use this command witho Docker Compose, you can modify https://github.com/ONLYOFFICE/Docker-DocumentServer/blob/master/run-document-server.sh to add this command and rebuild image locally

kerem commented

Author

Owner

@mrwormo commented on GitHub (Jun 27, 2019):

@ShockwaveNN I actually thought about modifying https://github.com/ONLYOFFICE/Docker-DocumentServer/blob/master/run-document-server.sh, and build my own image, but that means that we would have to rebuild the image each time we update.

@mrwormo commented on GitHub (Jun 27, 2019): @ShockwaveNN I actually thought about modifying [https://github.com/ONLYOFFICE/Docker-DocumentServer/blob/master/run-document-server.sh](https://github.com/ONLYOFFICE/Docker-DocumentServer/blob/master/run-document-server.sh), and build my own image, but that means that we would have to rebuild the image each time we update.

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Jun 27, 2019):

@mrwormo I think you can try to move running run-document-server.sh command to docker-compose.yml file and add something like

command: >
    bash -c "/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false'
    && bash /app/onlyoffice/run-document-server.sh"

I didn't test it through

@ShockwaveNN commented on GitHub (Jun 27, 2019): @mrwormo I think you can try to move running `run-document-server.sh` command to `docker-compose.yml` file and add something like ``` command: > bash -c "/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' && bash /app/onlyoffice/run-document-server.sh" ``` I didn't test it through

kerem commented

Author

Owner

@mrwormo commented on GitHub (Jul 1, 2019):

@ShockwaveNN Thx for the time spent, but it doesn't work. Dont't bother, i will continue to edit the file after the container has started...

@mrwormo commented on GitHub (Jul 1, 2019): @ShockwaveNN Thx for the time spent, but it doesn't work. Dont't bother, i will continue to edit the file after the container has started...

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Jul 10, 2019):

This issue is closed, seems original problem was resolved via update of nodejs to version 8
If not - I think it's better to create new issue

@ShockwaveNN commented on GitHub (Jul 10, 2019): This issue is closed, seems original problem was resolved via update of nodejs to version 8 If not - I think it's better to create new issue

kerem commented

Author

Owner

@ReinerNippes commented on GitHub (Nov 11, 2019):

@ShockwaveNN

This issue is closed, seems original problem was resolved via update of nodejs to version 8
If not - I think it's better to create new issue

no. it's still not possible to use selfsigned certifcates.
and the workaround to change the file /etc/onlyoffice/documentserver/default.json inside the container would not survive an update. or?

@ReinerNippes commented on GitHub (Nov 11, 2019): @ShockwaveNN > This issue is closed, seems original problem was resolved via update of nodejs to version 8 > If not - I think it's better to create new issue no. it's still not possible to use selfsigned certifcates. and the workaround to change the file `/etc/onlyoffice/documentserver/default.json` inside the container would not survive an update. or?

kerem commented

Author

Owner

@jcklpe commented on GitHub (Dec 13, 2019):

Can confirm that Reiner is correct. This issue wasn't fixed until I used the temporary fix.

@jcklpe commented on GitHub (Dec 13, 2019): Can confirm that Reiner is correct. This issue wasn't fixed until I used the temporary fix.

kerem commented

Author

Owner

@zner0L commented on GitHub (Jan 31, 2021):

There actually is a way to do this properly and without disabling certificate verification. You can add your own CAs (or rather, replace nodejs' CA store) by adding them in the agentOptions of request, which takes in the options you can define in the TLS Secure Context:

"services.CoAuthoring.requestDefaults" {
    "agentOptions": {
        "ca": "<your pem style CA cert>"
    }
}

@zner0L commented on GitHub (Jan 31, 2021): There actually is a way to do this properly and without disabling certificate verification. You can add your own CAs (or rather, replace nodejs' CA store) by adding them in the `agentOptions` of `request`, which takes in the options you can define in the [TLS Secure Context](https://nodejs.org/api/tls.html#tls_tls_createsecurecontext_options): ```json "services.CoAuthoring.requestDefaults" { "agentOptions": { "ca": "<your pem style CA cert>" } } ```

kerem commented

Author

Owner

@nmaludy commented on GitHub (Feb 5, 2021):

@mrwormo I think you can try to move running run-document-server.sh command to docker-compose.yml file and add something like
command: >
    bash -c "/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false'
    && bash /app/onlyoffice/run-document-server.sh"
I didn't test it through

I got this working using a modified version of this suggestion, basically inserting the edit in the docker run command. Problem in the example above is trying to use /var/www/onlyoffice/documentserver/npm/node_modules/.bin/json that doesn't exist. Instead need to use /var/www/onlyoffice/documentserver/npm/bin/json:

docker run -i -t -d -p 8443:443  -v /var/www/onlyoffice/Data:/var/www/onlyoffice/Data \
  --entrypoint "/bin/bash" \
  onlyoffice/documentserver \
  -c "/var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' && /app/ds/run-document-server.sh"

@nmaludy commented on GitHub (Feb 5, 2021): > @mrwormo I think you can try to move running `run-document-server.sh` command to `docker-compose.yml` file and add something like > > ``` > command: > > bash -c "/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' > && bash /app/onlyoffice/run-document-server.sh" > ``` > > I didn't test it through I got this working using a modified version of this suggestion, basically inserting the edit in the docker run command. Problem in the example above is trying to use `/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json` that doesn't exist. Instead need to use `/var/www/onlyoffice/documentserver/npm/bin/json`: ``` docker run -i -t -d -p 8443:443 -v /var/www/onlyoffice/Data:/var/www/onlyoffice/Data \ --entrypoint "/bin/bash" \ onlyoffice/documentserver \ -c "/var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' && /app/ds/run-document-server.sh" ```

kerem commented

Author

Owner

@lgzcoollg commented on GitHub (Jan 9, 2022):

@mrwormo I think you can try to move running run-document-server.sh command to docker-compose.yml file and add something like
command: >
    bash -c "/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false'
    && bash /app/onlyoffice/run-document-server.sh"
I didn't test it through
I got this working using a modified version of this suggestion, basically inserting the edit in the docker run command. Problem in the example above is trying to use /var/www/onlyoffice/documentserver/npm/node_modules/.bin/json that doesn't exist. Instead need to use /var/www/onlyoffice/documentserver/npm/bin/json:
docker run -i -t -d -p 8443:443  -v /var/www/onlyoffice/Data:/var/www/onlyoffice/Data \
  --entrypoint "/bin/bash" \
  onlyoffice/documentserver \
  -c "/var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' && /app/ds/run-document-server.sh"

Docker tag:6.4, input command after docker run.and it work

@lgzcoollg commented on GitHub (Jan 9, 2022): > > @mrwormo I think you can try to move running `run-document-server.sh` command to `docker-compose.yml` file and add something like > > ``` > > command: > > > bash -c "/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' > > && bash /app/onlyoffice/run-document-server.sh" > > ``` > > > > > > > > > > > > > > > > > > > > > > > > I didn't test it through > > I got this working using a modified version of this suggestion, basically inserting the edit in the docker run command. Problem in the example above is trying to use `/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json` that doesn't exist. Instead need to use `/var/www/onlyoffice/documentserver/npm/bin/json`: > > ``` > docker run -i -t -d -p 8443:443 -v /var/www/onlyoffice/Data:/var/www/onlyoffice/Data \ > --entrypoint "/bin/bash" \ > onlyoffice/documentserver \ > -c "/var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' && /app/ds/run-document-server.sh" > ``` Docker tag:6.4, input command after docker run.and it work

kerem commented

Author

Owner

@lgzcoollg commented on GitHub (Jan 25, 2022):

@mrwormo I think you can try to move running run-document-server.sh command to docker-compose.yml file and add something like
command: >
    bash -c "/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false'
    && bash /app/onlyoffice/run-document-server.sh"
I didn't test it through
I got this working using a modified version of this suggestion, basically inserting the edit in the docker run command. Problem in the example above is trying to use /var/www/onlyoffice/documentserver/npm/node_modules/.bin/json that doesn't exist. Instead need to use /var/www/onlyoffice/documentserver/npm/bin/json:
docker run -i -t -d -p 8443:443  -v /var/www/onlyoffice/Data:/var/www/onlyoffice/Data \
  --entrypoint "/bin/bash" \
  onlyoffice/documentserver \
  -c "/var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' && /app/ds/run-document-server.sh"

not work in docker image tags 7.0.0

@lgzcoollg commented on GitHub (Jan 25, 2022): > > @mrwormo I think you can try to move running `run-document-server.sh` command to `docker-compose.yml` file and add something like > > ``` > > command: > > > bash -c "/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' > > && bash /app/onlyoffice/run-document-server.sh" > > ``` > > > > > > > > > > > > > > > > > > > > > > > > I didn't test it through > > I got this working using a modified version of this suggestion, basically inserting the edit in the docker run command. Problem in the example above is trying to use `/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json` that doesn't exist. Instead need to use `/var/www/onlyoffice/documentserver/npm/bin/json`: > > ``` > docker run -i -t -d -p 8443:443 -v /var/www/onlyoffice/Data:/var/www/onlyoffice/Data \ > --entrypoint "/bin/bash" \ > onlyoffice/documentserver \ > -c "/var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' && /app/ds/run-document-server.sh" > ``` not work in docker image tags 7.0.0

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Jan 25, 2022):

You can now use docker env key USE_UNAUTHORIZED_STORAGE

@ShockwaveNN commented on GitHub (Jan 25, 2022): You can now use docker env key `USE_UNAUTHORIZED_STORAGE`

kerem commented

Author

Owner

@lgzcoollg commented on GitHub (Jan 25, 2022):

You can now use docker env key USE_UNAUTHORIZED_STORAGE

Seccused!
-e USE_UNAUTHORIZED_STORAGE=true

@lgzcoollg commented on GitHub (Jan 25, 2022): > You can now use docker env key `USE_UNAUTHORIZED_STORAGE` Seccused! -e USE_UNAUTHORIZED_STORAGE=true

kerem commented

Author

Owner

@mrwormo commented on GitHub (Feb 28, 2022):

You can now use docker env key USE_UNAUTHORIZED_STORAGE

Yeah ! It's working with tag:6.4.2.
Not tested with tag:7

@mrwormo commented on GitHub (Feb 28, 2022): > You can now use docker env key `USE_UNAUTHORIZED_STORAGE` Yeah ! It's working with tag:6.4.2. Not tested with tag:7

kerem commented

Author

Owner

@webagroprom commented on GitHub (May 25, 2022):

 #- LARGER_FILE_LIMITS=true
    ports:
      - '9050:80'
      - '9000:443'
    stdin_open: true
    restart: always
    stop_grace_period: 120s
    command: bash -c "/var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' && bash /app/onlyoffice/run-document-server.sh"
    volumes:

Added to configuration docker-compose.yml launched container docker-compose up -d

nextcloud: Error while downloading the document file to be converted.) (версия 7.1.0.215)

What am I doing wrong ? How to solve this error?

@webagroprom commented on GitHub (May 25, 2022): ``` #- LARGER_FILE_LIMITS=true ports: - '9050:80' - '9000:443' stdin_open: true restart: always stop_grace_period: 120s command: bash -c "/var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' && bash /app/onlyoffice/run-document-server.sh" volumes: ``` Added to configuration docker-compose.yml launched container docker-compose up -d nextcloud: **Error while downloading the document file to be converted.) (версия 7.1.0.215)** What am I doing wrong ? How to solve this error?

kerem commented

Author

Owner

@webagroprom commented on GitHub (May 26, 2022):

@mrwormo I think you can try to move running run-document-server.sh command to docker-compose.yml file and add something like
command: >
    bash -c "/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false'
    && bash /app/onlyoffice/run-document-server.sh"
I didn't test it through
I got this working using a modified version of this suggestion, basically inserting the edit in the docker run command. Problem in the example above is trying to use /var/www/onlyoffice/documentserver/npm/node_modules/.bin/json that doesn't exist. Instead need to use /var/www/onlyoffice/documentserver/npm/bin/json:
docker run -i -t -d -p 8443:443  -v /var/www/onlyoffice/Data:/var/www/onlyoffice/Data \
  --entrypoint "/bin/bash" \
  onlyoffice/documentserver \
  -c "/var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' && /app/ds/run-document-server.sh"
Docker tag:6.4, input command after docker run.and it work

Can you show an example of how to correctly add (as you added) data to the docker-compose.yml configuration file ?

@webagroprom commented on GitHub (May 26, 2022): > > > @mrwormo I think you can try to move running `run-document-server.sh` command to `docker-compose.yml` file and add something like > > > ``` > > > command: > > > > bash -c "/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' > > > && bash /app/onlyoffice/run-document-server.sh" > > > ``` > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I didn't test it through > > > > > > I got this working using a modified version of this suggestion, basically inserting the edit in the docker run command. Problem in the example above is trying to use `/var/www/onlyoffice/documentserver/npm/node_modules/.bin/json` that doesn't exist. Instead need to use `/var/www/onlyoffice/documentserver/npm/bin/json`: > > ``` > > docker run -i -t -d -p 8443:443 -v /var/www/onlyoffice/Data:/var/www/onlyoffice/Data \ > > --entrypoint "/bin/bash" \ > > onlyoffice/documentserver \ > > -c "/var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/default.json -I -e 'this.services.CoAuthoring.requestDefaults.rejectUnauthorized=false' && /app/ds/run-document-server.sh" > > ``` > > Docker tag:6.4, input command after docker run.and it work **Can you show an example of how to correctly add (as you added) data to the docker-compose.yml configuration file ?**

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (May 26, 2022):

@webagroprom I think for you it's better to create new discusttion\new issue since your problem doesn't seem any relation to original issue with certificate verification

@ShockwaveNN commented on GitHub (May 26, 2022): @webagroprom I think for you it's better to create new discusttion\new issue since your problem doesn't seem any relation to original issue with certificate verification

kerem commented

Author

Owner

@ghost commented on GitHub (Jun 7, 2022):

Hello,

To resolve the same problem with Let's encrypt cert, I didn't modify onlyoffice configuration file default.json.
I only change ssl_certificate in nginx configuration file /etc/nginx/conf.d/ds.conf (onlyoffice general server block) :
ssl_certificate /etc/ssl/certs/fullchain.pem;
ssl_certificate_key /etc/ssl/private/privkey.pem;

pem files are from let's encrypt folder, I just copied them in /etc/ssl/certs/ and /etc/private/
When having the problem, I used cert.pem, now I use fullchain.pem and problem is gone.

See attachment : ds.conf.txt

@ghost commented on GitHub (Jun 7, 2022): Hello, To resolve the same problem with Let's encrypt cert, I didn't modify onlyoffice configuration file default.json. I only change ssl_certificate in nginx configuration file /etc/nginx/conf.d/ds.conf (onlyoffice general server block) : ssl_certificate /etc/ssl/certs/fullchain.pem; ssl_certificate_key /etc/ssl/private/privkey.pem; pem files are from let's encrypt folder, I just copied them in /etc/ssl/certs/ and /etc/private/ When having the problem, I used cert.pem, now I use fullchain.pem and problem is gone. See attachment : [ds.conf.txt](https://github.com/ONLYOFFICE/Docker-DocumentServer/files/8852952/ds.conf.txt)

kerem commented

Author

Owner

@douglascrp commented on GitHub (Jun 14, 2022):

You can now use docker env key USE_UNAUTHORIZED_STORAGE

Seccused! -e USE_UNAUTHORIZED_STORAGE=true

Yes, it works

@douglascrp commented on GitHub (Jun 14, 2022): > > You can now use docker env key `USE_UNAUTHORIZED_STORAGE` > > Seccused! -e USE_UNAUTHORIZED_STORAGE=true Yes, it works

kerem commented