#224 - [GH-ISSUE #441] Error while downloading the document file to be converted.) (версия 7.1.0.215) - docker docker-compose - starred/Docker-DocumentServer-ONLYOFFICE

Owner

Originally created by @webagroprom on GitHub (May 26, 2022).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/441

Originally assigned to: @igwyd on GitHub.

Nextcloud Hub II 23.0.5 + Onlyoffice

Open Nexcloud's config.php (by defauld /var/www/nextcloud/config/config.php)
Add this to the 2nd last line (before the line with );) and paste in your secret (3rd last line)

'onlyoffice' =>
   array (
     "jwt_secret" => "123123123",
     "jwt_header" => "AuthorizationJwt"
 )

create openssl self-signed certificate
mkdir /app/onlyoffice/DocumentServer/data/certs
cp /app/onlyoffice/DocumentServer/data/certs/onlyoffice.crt
cp /app/onlyoffice/DocumentServer/data/certs/onlyoffice.key
Edit file docker-compose.yml4.

      - JWT_ENABLED=true
      - JWT_SECRET=123123123
      - JWT_HEADER=AuthorizationJwt
      - JWT_IN_BODY=true

full file docker-compose.yml

version: '2'
services:
  onlyoffice-documentserver:
    image: jiriks74/onlyoffice-documentserver:latest
    container_name: onlyoffice-documentserver
    depends_on:
      - onlyoffice-postgresql
      - onlyoffice-rabbitmq
    environment:
      - DB_TYPE=postgres
      - DB_HOST=onlyoffice-postgresql
      - DB_PORT=5432
      - DB_NAME=onlyoffice
      - DB_USER=onlyoffice
      - AMQP_URI=amqp://guest:guest@onlyoffice-rabbitmq
      # Uncomment strings below to enable the JSON Web Token validation.
      - JWT_ENABLED=true
      - JWT_SECRET=123123123
      - JWT_HEADER=AuthorizationJwt
      - JWT_IN_BODY=true
      # Uncomment the line below to set larger file limits (about 1GB)
      #- LARGER_FILE_LIMITS=true
    ports:
      - '9050:80'
      - '9000:443'
    stdin_open: true
    restart: always
    stop_grace_period: 120s
    volumes:
       # Uncomment the line below to get access to the slide themes directory.
       # To use the themes, copy them to the slideThemes directory and run `docker exec -it <container-name> /usr/bin/documentserver-generate-allfonts.sh`
       #- ./slideThemes:/var/www/onlyoffice/documentserver/sdkjs/slide/themes/src
       #- /var/www/onlyoffice/Data
       #- /var/log/onlyoffice
       #- /var/lib/onlyoffice/documentserver/App_Data/cache/files
       #- /var/www/onlyoffice/documentserver-example/public/files
       #- /usr/share/fonts
        - /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice
        - /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data
        - /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice
        - /app/onlyoffice/DocumentServer/db:/var/lib/postgresql

  onlyoffice-rabbitmq:
    container_name: onlyoffice-rabbitmq
    image: rabbitmq
    restart: always
    expose:
      - '5672'

  onlyoffice-postgresql:
    container_name: onlyoffice-postgresql
    image: postgres:9.5
    environment:
      - POSTGRES_DB=onlyoffice
      - POSTGRES_USER=onlyoffice
      - POSTGRES_HOST_AUTH_METHOD=trust
    restart: always
    expose:
      - '5432'
    volumes:
      - postgresql_data:/var/lib/postgresql

volumes:
  postgresql_data:

run docker-compose onlyoffice -
docker-compose up -d
I go to the browser: https://localhost:9000
open: ONLYOFFICE Docs Community Edition installed
I go to the browser and enter the nextcloud settings, I press the save button, it gives an error:
Error while downloading the document file to be converted.) (версия 7.1.0.215)

https://github.com/jiriks74/Docker-DocumentServer ( full instruction )

What could be causing the error, how can it be solved??

Originally created by @webagroprom on GitHub (May 26, 2022). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/441 Originally assigned to: @igwyd on GitHub. Nextcloud Hub II 23.0.5 + Onlyoffice 1. Open Nexcloud's config.php (by defauld /var/www/nextcloud/config/config.php) Add this to the 2nd last line (before the line with );) and paste in your secret (3rd last line) ``` 'onlyoffice' => array ( "jwt_secret" => "123123123", "jwt_header" => "AuthorizationJwt" ) ``` 2. **create openssl self-signed certificate** mkdir /app/onlyoffice/DocumentServer/data/certs cp /app/onlyoffice/DocumentServer/data/certs/onlyoffice.crt cp /app/onlyoffice/DocumentServer/data/certs/onlyoffice.key 4. **Edit file docker-compose.yml**4. ``` - JWT_ENABLED=true - JWT_SECRET=123123123 - JWT_HEADER=AuthorizationJwt - JWT_IN_BODY=true ``` **full file docker-compose.yml** ``` version: '2' services: onlyoffice-documentserver: image: jiriks74/onlyoffice-documentserver:latest container_name: onlyoffice-documentserver depends_on: - onlyoffice-postgresql - onlyoffice-rabbitmq environment: - DB_TYPE=postgres - DB_HOST=onlyoffice-postgresql - DB_PORT=5432 - DB_NAME=onlyoffice - DB_USER=onlyoffice - AMQP_URI=amqp://guest:guest@onlyoffice-rabbitmq # Uncomment strings below to enable the JSON Web Token validation. - JWT_ENABLED=true - JWT_SECRET=123123123 - JWT_HEADER=AuthorizationJwt - JWT_IN_BODY=true # Uncomment the line below to set larger file limits (about 1GB) #- LARGER_FILE_LIMITS=true ports: - '9050:80' - '9000:443' stdin_open: true restart: always stop_grace_period: 120s volumes: # Uncomment the line below to get access to the slide themes directory. # To use the themes, copy them to the slideThemes directory and run `docker exec -it <container-name> /usr/bin/documentserver-generate-allfonts.sh` #- ./slideThemes:/var/www/onlyoffice/documentserver/sdkjs/slide/themes/src #- /var/www/onlyoffice/Data #- /var/log/onlyoffice #- /var/lib/onlyoffice/documentserver/App_Data/cache/files #- /var/www/onlyoffice/documentserver-example/public/files #- /usr/share/fonts - /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice - /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data - /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice - /app/onlyoffice/DocumentServer/db:/var/lib/postgresql onlyoffice-rabbitmq: container_name: onlyoffice-rabbitmq image: rabbitmq restart: always expose: - '5672' onlyoffice-postgresql: container_name: onlyoffice-postgresql image: postgres:9.5 environment: - POSTGRES_DB=onlyoffice - POSTGRES_USER=onlyoffice - POSTGRES_HOST_AUTH_METHOD=trust restart: always expose: - '5432' volumes: - postgresql_data:/var/lib/postgresql volumes: postgresql_data: ``` 5. run docker-compose onlyoffice - **docker-compose up -d** 6. I go to the browser: https://localhost:9000 open: ONLYOFFICE Docs Community Edition installed 7. I go to the browser and enter the nextcloud settings, I press the save button, it gives an error: **Error while downloading the document file to be converted.) (версия 7.1.0.215)** https://github.com/jiriks74/Docker-DocumentServer **( full instruction )** What could be causing the error, how can it be solved??

kerem closed this issue

kerem commented

Author

Owner

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

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

This error usually mena that DocumentServer cannot access file it's trying to convert, usually due to network errors

Check /var/log/onlyoffice/ for any details

@ShockwaveNN commented on GitHub (May 26, 2022): > Error while downloading the document file to be converted.) (версия 7.1.0.215) This error usually mena that DocumentServer cannot access file it's trying to convert, usually due to network errors Check `/var/log/onlyoffice/` for any details

kerem commented

Author

Owner

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

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

This error usually mena that DocumentServer cannot access file it's trying to convert, usually due to network errors

Check /var/log/onlyoffice/ for any details

Checked, gives an error

[2022-05-26T16:47:49.213] [ERROR] nodeJS - dnsLookup error: hostname = example.ru
Error: getaddrinfo EAI_AGAIN  example.ru
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26)
[2022-05-26T16:47:49.213] [ERROR] nodeJS - checkIpFilter error:url=https:/example.ru/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.AOWo1tb7MieSkbPNBZsA_yzAf7qM4MvEvsuT--RHlUo;code:403;(id=conv_check_209251679_docx)

How to solve this error?

@webagroprom commented on GitHub (May 26, 2022): > > Error while downloading the document file to be converted.) (версия 7.1.0.215) > > This error usually mena that DocumentServer cannot access file it's trying to convert, usually due to network errors > > Check `/var/log/onlyoffice/` for any details **Checked, gives an error** ``` [2022-05-26T16:47:49.213] [ERROR] nodeJS - dnsLookup error: hostname = example.ru Error: getaddrinfo EAI_AGAIN example.ru at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26) [2022-05-26T16:47:49.213] [ERROR] nodeJS - checkIpFilter error:url=https:/example.ru/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.AOWo1tb7MieSkbPNBZsA_yzAf7qM4MvEvsuT--RHlUo;code:403;(id=conv_check_209251679_docx) ``` How to solve this error?

kerem commented

Author

Owner

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

This mean that in some of your configs there is host example.ru and DocumentServer thinks that it's store it files there

This host is non-existing and so it fails

Look you configs for example.ru - I think it cannot be in our source at all, your attached docker-compose has no mention of it either, but seems that nextcloud is aware of it

@ShockwaveNN commented on GitHub (May 27, 2022): This mean that in some of your configs there is host example.ru and DocumentServer thinks that it's store it files there This host is non-existing and so it fails Look you configs for `example.ru` - I think it cannot be in our source at all, your attached docker-compose has no mention of it either, but seems that nextcloud is aware of it

kerem commented

Author

Owner

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

This mean that in some of your configs there is host example.ru and DocumentServer thinks that it's store it files there

This host is non-existing and so it fails

Look you configs for example.ru - I think it cannot be in our source at all, your attached docker-compose has no mention of it either, but seems that nextcloud is aware of it

Where exactly are the configs that can be edited to solve the error?

Above I have given all the steps that I do to set up the integration of onlyoffice + nextcloud

In this error, where the example.ru domain is indicated, my domain is shown on which I have nextcloud installed. Example.ru I indicated for an example.

@webagroprom commented on GitHub (May 27, 2022): > This mean that in some of your configs there is host example.ru and DocumentServer thinks that it's store it files there > > This host is non-existing and so it fails > > Look you configs for `example.ru` - I think it cannot be in our source at all, your attached docker-compose has no mention of it either, but seems that nextcloud is aware of it Where exactly are the configs that can be edited to solve the error? Above I have given all the steps that I do to set up the integration of onlyoffice + nextcloud In this error, where the example.ru domain is indicated, my domain is shown on which I have nextcloud installed. Example.ru I indicated for an example.

kerem commented

Author

Owner

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

Ok, got it, understand that example.ru is just a template

[2022-05-26T16:47:49.213] [ERROR] nodeJS - dnsLookup error: hostname = example.ru
Error: getaddrinfo EAI_AGAIN  example.ru
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26)

This error means that DocumentServer cannot resolve or access the hostname you've used in the config of the Nextcloud connector plugin

Usually, it's some network problem or something like this, especially if you're in Russia (judging by your example URL) some server can be in RKN block list by error

So proper way to check - connect to the DocumentServer container and ping/curl that address from inside of container and if you get any error on ping\curl - that mean that it's not a bug in DocumentServer but issue in your network configuration

@ShockwaveNN commented on GitHub (May 29, 2022): Ok, got it, understand that example.ru is just a template ``` [2022-05-26T16:47:49.213] [ERROR] nodeJS - dnsLookup error: hostname = example.ru Error: getaddrinfo EAI_AGAIN example.ru at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26) ``` This error means that DocumentServer cannot resolve or access the hostname you've used in the config of the Nextcloud connector plugin Usually, it's some network problem or something like this, especially if you're in Russia (judging by your example URL) some server can be in RKN block list by error So proper way to check - connect to the DocumentServer container and ping/curl that address from inside of container and if you get any error on ping\curl - that mean that it's not a bug in DocumentServer but issue in your network configuration

kerem commented

Author

Owner

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

Ok, got it, understand that example.ru is just a template
[2022-05-26T16:47:49.213] [ERROR] nodeJS - dnsLookup error: hostname = example.ru
Error: getaddrinfo EAI_AGAIN  example.ru
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26)
This error means that DocumentServer cannot resolve or access the hostname you've used in the config of the Nextcloud connector plugin

Usually, it's some network problem or something like this, especially if you're in Russia (judging by your example URL) some server can be in RKN block list by error

So proper way to check - connect to the DocumentServer container and ping/curl that address from inside of container and if you get any error on ping\curl - that mean that it's not a bug in DocumentServer but issue in your network configuration

curl https://192.168.200.11:9000

curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

But if I go to this address in the browser https://192.168.200.11:9000 (it says that the certificate is not verified), I forcefully accept a non-secure security certificate, the onlyoffice page opens with a greeting:

ONLYOFFICE Docs Community Edition installed
To edit office documents and collaborate, integrate ONLYOFFICE Docs into your sync&share app.

Self-signed security certificate ( openSSL )
I plan to use onlyoffice inside the local network without direct access outside the onlyoffice application

How to bypass certificate verification?
Are there other solutions to this error?

@webagroprom commented on GitHub (May 30, 2022): > Ok, got it, understand that example.ru is just a template > > ``` > [2022-05-26T16:47:49.213] [ERROR] nodeJS - dnsLookup error: hostname = example.ru > Error: getaddrinfo EAI_AGAIN example.ru > at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26) > ``` > > This error means that DocumentServer cannot resolve or access the hostname you've used in the config of the Nextcloud connector plugin > > Usually, it's some network problem or something like this, especially if you're in Russia (judging by your example URL) some server can be in RKN block list by error > > So proper way to check - connect to the DocumentServer container and ping/curl that address from inside of container and if you get any error on ping\curl - that mean that it's not a bug in DocumentServer but issue in your network configuration **curl https://192.168.200.11:9000** curl: (60) SSL certificate problem: self signed certificate More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. **But if I go to this address in the browser** https://192.168.200.11:9000 (it says that the certificate is not verified), I forcefully accept a non-secure security certificate, the onlyoffice page opens with a greeting: ONLYOFFICE Docs Community Edition installed To edit office documents and collaborate, integrate ONLYOFFICE Docs into your sync&share app. Self-signed security certificate ( openSSL ) I plan to use onlyoffice inside the local network without direct access outside the onlyoffice application How to bypass certificate verification? Are there other solutions to this error?

kerem commented

Author

Owner

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

I think enabling of option USE_UNAUTHORIZED_STORAGE may help you

Didn't check it for long time through, since clients prefer to use legit certificate in most cases after rise of Let's Encrypt

@ShockwaveNN commented on GitHub (May 30, 2022): I think enabling of option [USE_UNAUTHORIZED_STORAGE](https://github.com/ONLYOFFICE/Docker-DocumentServer/#available-configuration-parameters) may help you Didn't check it for long time through, since clients prefer to use legit certificate in most cases after rise of Let's Encrypt

kerem commented

Author

Owner

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

I think enabling of option USE_UNAUTHORIZED_STORAGE may help you

Didn't check it for long time through, since clients prefer to use legit certificate in most cases after rise of Let's Encrypt

I plan to use onlyoffice on the local network, so there is no need to connect Let's Encrypt.
What is the correct way to add the USE_UNAUTHORIZED_STORAGE setting to docker-compose ?

# Uncomment strings below to enable the JSON Web Token validation.
      - JWT_ENABLED=true
      - JWT_SECRET=123123123
      - JWT_HEADER=AuthorizationJwt
      - JWT_IN_BODY=true
      - USE_UNAUTHORIZED_STORAGE=true
      # Uncomment the line below to set larger file limits (about 1GB)
      #- LARGER_FILE_LIMITS=true
    ports:
      - '9050:80'
      - '9000:443'
    stdin_open: true
    restart: always
    stop_grace_period: 120s

Is this addition of a parameter correct?

@webagroprom commented on GitHub (May 30, 2022): > I think enabling of option [USE_UNAUTHORIZED_STORAGE](https://github.com/ONLYOFFICE/Docker-DocumentServer/#available-configuration-parameters) may help you > > Didn't check it for long time through, since clients prefer to use legit certificate in most cases after rise of Let's Encrypt I plan to use onlyoffice on the local network, so there is no need to connect Let's Encrypt. What is the correct way to add the USE_UNAUTHORIZED_STORAGE setting to docker-compose ? ``` # Uncomment strings below to enable the JSON Web Token validation. - JWT_ENABLED=true - JWT_SECRET=123123123 - JWT_HEADER=AuthorizationJwt - JWT_IN_BODY=true - USE_UNAUTHORIZED_STORAGE=true # Uncomment the line below to set larger file limits (about 1GB) #- LARGER_FILE_LIMITS=true ports: - '9050:80' - '9000:443' stdin_open: true restart: always stop_grace_period: 120s ``` Is this addition of a parameter correct?

kerem commented

Author

Owner

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

Yeah, look ok, but as said not sure if it working right now, since it was somehow related to nodejs version in previous times and something may changed since..

@ShockwaveNN commented on GitHub (May 30, 2022): Yeah, look ok, but as said not sure if it working right now, since it was somehow related to nodejs version in previous times and something may changed since..

kerem commented

Author

Owner

@toonemastic commented on GitHub (May 30, 2022):

Hello,

Facing to the same issue running netcloudpi on a raspberry pi using the same docker-compose.
I launch the containers using these commands in a bash script :
export DOCKERHOST=$(ifconfig | grep -E "([0-9]{1,3}.){3}[0-9]{1,3}" | grep -v 127.0.0.1 | awk '{ print $2 }' | cut -f2 -d: | head -n1)
docker-compose up -d
And add these lines in docker-compose.yml for the service onlyoffice-documentserver: :
extra_hosts:
- "dockerhost:$DOCKERHOST"

I see in the logs/documentserver/converter/out.log this error :
[2022-05-30T12:07:15.991] [ERROR] nodeJS - error downloadFile:url=https://dockerhost/index.php/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.ed9EyZ_kJw0pcqBQ1aZ0B_pEkVrRoAzAUlpJ1DTJMzY;attempt=3;code:undefined;connect:undefined;(id=conv_check_450561579_docx)
Error: Error response: statusCode:400; headers:{"date":"Mon, 30 May 2022 12:07:15 GMT","server":"Apache","expires":"Thu, 19 Nov 1981 08:52:00 GMT","cache-control":"no-store, no-cache, must-revalidate","pragma":"no-cache","content-security-policy":"default-src 'self'; script-src 'self' 'nonce-Z2o2VmFzaXlqcWJaK09KYlMxZmpnSTgrRlhTUGlsWXE3R045ZHlhbDg5UT06eEh6TlhwclZ5ZjZva05NMkpEMkl3OE50WkRmSDJpZFpxMU1YTlVIRWdiST0='; style-src 'self' 'unsafe-inline'; frame-src *; img-src * data: blob:; font-src 'self' data:; media-src *; connect-src *; object-src 'none'; base-uri 'self';","set-cookie":["oc_sessionPassphrase=aHaHD4T6Io%2B%2BjZ%2BcuVLcB%2BUCHeW40JqSBdPM0j%2B0q%2By29BUlN62vjnbHG3PRoRuwct0rdqsslalxVC44BVEJ7ODsEmWV2mhhB9Vl6qAN8c%2FZkbpTcsFFeGtOSpdNG3mq; path=/; secure; HttpOnly; SameSite=Lax","ocmh3ubw421p=ffnehu66k3s7bu324pc0jjmt89; path=/; secure; HttpOnly; SameSite=Lax","__Host-nc_sameSiteCookielax=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=lax","__Host-nc_sameSiteCookiestrict=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=strict"],"strict-transport-security":"max-age=15768000; includeSubDomains","referrer-policy":"no-referrer","x-content-type-options":"nosniff","x-download-options":"noopen","x-frame-options":"SAMEORIGIN","x-permitted-cross-domain-policies":"none","x-robots-tag":"none","x-xss-protection":"1; mode=block","upgrade":"h2,h2c","connection":"Upgrade, close","transfer-encoding":"chunked","content-type":"text/html; charset=UTF-8"};
at Request.fResponse (/snapshot/server/build/server/Common/sources/utils.js)
at Request.emit (events.js:400:28)
at Request.onRequestResponse (/snapshot/server/build/server/Common/node_modules/request/request.js:1059:10)
at ClientRequest.emit (events.js:400:28)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:647:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17)
at TLSSocket.socketOnData (_http_client.js:515:22)
at TLSSocket.emit (events.js:400:28)
at addChunk (internal/streams/readable.js:293:12)
at readableAddChunk (internal/streams/readable.js:267:9)
at TLSSocket.Readable.push (internal/streams/readable.js:206:10)
at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)

I just don't know what does that means.

Could someone give me a tip?

Regards,

Pierre

@toonemastic commented on GitHub (May 30, 2022): Hello, Facing to the same issue running netcloudpi on a raspberry pi using the same docker-compose. I launch the containers using these commands in a bash script : **export DOCKERHOST=$(ifconfig | grep -E "([0-9]{1,3}\.){3}[0-9]{1,3}" | grep -v 127.0.0.1 | awk '{ print $2 }' | cut -f2 -d: | head -n1) docker-compose up -d** And add these lines in docker-compose.yml for the service onlyoffice-documentserver: : extra_hosts: - "dockerhost:$DOCKERHOST" I see in the logs/documentserver/converter/out.log this error : [2022-05-30T12:07:15.991] [ERROR] nodeJS - error downloadFile:url=https://dockerhost/index.php/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.ed9EyZ_kJw0pcqBQ1aZ0B_pEkVrRoAzAUlpJ1DTJMzY;attempt=3;code:undefined;connect:undefined;(id=conv_check_450561579_docx) Error: Error response: statusCode:400; headers:{"date":"Mon, 30 May 2022 12:07:15 GMT","server":"Apache","expires":"Thu, 19 Nov 1981 08:52:00 GMT","cache-control":"no-store, no-cache, must-revalidate","pragma":"no-cache","content-security-policy":"default-src 'self'; script-src 'self' 'nonce-Z2o2VmFzaXlqcWJaK09KYlMxZmpnSTgrRlhTUGlsWXE3R045ZHlhbDg5UT06eEh6TlhwclZ5ZjZva05NMkpEMkl3OE50WkRmSDJpZFpxMU1YTlVIRWdiST0='; style-src 'self' 'unsafe-inline'; frame-src *; img-src * data: blob:; font-src 'self' data:; media-src *; connect-src *; object-src 'none'; base-uri 'self';","set-cookie":["oc_sessionPassphrase=aHaHD4T6Io%2B%2BjZ%2BcuVLcB%2BUCHeW40JqSBdPM0j%2B0q%2By29BUlN62vjnbHG3PRoRuwct0rdqsslalxVC44BVEJ7ODsEmWV2mhhB9Vl6qAN8c%2FZkbpTcsFFeGtOSpdNG3mq; path=/; secure; HttpOnly; SameSite=Lax","ocmh3ubw421p=ffnehu66k3s7bu324pc0jjmt89; path=/; secure; HttpOnly; SameSite=Lax","__Host-nc_sameSiteCookielax=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=lax","__Host-nc_sameSiteCookiestrict=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=strict"],"strict-transport-security":"max-age=15768000; includeSubDomains","referrer-policy":"no-referrer","x-content-type-options":"nosniff","x-download-options":"noopen","x-frame-options":"SAMEORIGIN","x-permitted-cross-domain-policies":"none","x-robots-tag":"none","x-xss-protection":"1; mode=block","upgrade":"h2,h2c","connection":"Upgrade, close","transfer-encoding":"chunked","content-type":"text/html; charset=UTF-8"}; at Request.fResponse (/snapshot/server/build/server/Common/sources/utils.js) at Request.emit (events.js:400:28) at Request.onRequestResponse (/snapshot/server/build/server/Common/node_modules/request/request.js:1059:10) at ClientRequest.emit (events.js:400:28) at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:647:27) at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17) at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at TLSSocket.Readable.push (internal/streams/readable.js:206:10) at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23) I just don't know what does that means. Could someone give me a tip? Regards, Pierre

kerem commented

Author

Owner

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

Yeah, look ok, but as said not sure if it working right now, since it was somehow related to nodejs version in previous times and something may changed since..

Added to my configuration docker-compose: USE_UNAUTHORIZED_STORAGE=true

# Uncomment strings below to enable the JSON Web Token validation.
      - JWT_ENABLED=true
      - JWT_SECRET=123123123
      - JWT_HEADER=AuthorizationJwt
      - JWT_IN_BODY=true
      - USE_UNAUTHORIZED_STORAGE=true
      # Uncomment the line below to set larger file limits (about 1GB)
      #- LARGER_FILE_LIMITS=true
    ports:
      - '9050:80'
      - '9000:443'
    stdin_open: true
    restart: always
    stop_grace_period: 120s

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

@webagroprom commented on GitHub (May 30, 2022): > Yeah, look ok, but as said not sure if it working right now, since it was somehow related to nodejs version in previous times and something may changed since.. Added to my configuration docker-compose: **USE_UNAUTHORIZED_STORAGE=true** ``` # Uncomment strings below to enable the JSON Web Token validation. - JWT_ENABLED=true - JWT_SECRET=123123123 - JWT_HEADER=AuthorizationJwt - JWT_IN_BODY=true - USE_UNAUTHORIZED_STORAGE=true # Uncomment the line below to set larger file limits (about 1GB) #- LARGER_FILE_LIMITS=true ports: - '9050:80' - '9000:443' stdin_open: true restart: always stop_grace_period: 120s ``` **Error while downloading the document file to be converted.) (версия 7.1.0.215)**

kerem commented

Author

Owner

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

Could you temporary disable jwt and see if problem still persists, maybe this config is broken as I said (

@ShockwaveNN commented on GitHub (May 30, 2022): Could you temporary disable jwt and see if problem still persists, maybe this config is broken as I said (

kerem commented

Author

Owner

@toonemastic commented on GitHub (May 30, 2022):

jwt disable : same issue

@toonemastic commented on GitHub (May 30, 2022): jwt disable : same issue

kerem commented

Author

Owner

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

Could you temporary disable jwt and see if problem still persists, maybe this config is broken as I said (

docker-compose.yml Disable jwt

 # Uncomment strings below to enable the JSON Web Token validation.
      # - JWT_ENABLED=true
      # - JWT_SECRET=123123123
      # - JWT_HEADER=AuthorizationJwt
      # - JWT_IN_BODY=true
      # - USE_UNAUTHORIZED_STORAGE=true
      # Uncomment the line below to set larger file limits (about 1GB)
      #- 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$

Disable jwt nextcloud and eject secret key.

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

@webagroprom commented on GitHub (May 30, 2022): > Could you temporary disable jwt and see if problem still persists, maybe this config is broken as I said ( **docker-compose.yml** Disable jwt ``` # Uncomment strings below to enable the JSON Web Token validation. # - JWT_ENABLED=true # - JWT_SECRET=123123123 # - JWT_HEADER=AuthorizationJwt # - JWT_IN_BODY=true # - USE_UNAUTHORIZED_STORAGE=true # Uncomment the line below to set larger file limits (about 1GB) #- 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$ ``` **Disable jwt nextcloud** and eject secret key. **Error while downloading the document file to be converted.) (версия 7.1.0.215)**

kerem commented

Author

Owner

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

Ok, seems that this option can be broken

We'll look at that as soon as we got free time

@ShockwaveNN commented on GitHub (May 30, 2022): Ok, seems that this option can be broken We'll look at that as soon as we got free time

kerem commented

Author

Owner

@igwyd commented on GitHub (May 31, 2022):

hello @webagroprom, first of all, you are using someone else's docker container based on our product image: jiriks74/onlyoffice-documentserver:latest we won't be able to help with this. Our containers you can get from docker hub, and it should be image: onlyoffice/documentserver:latest.
I checked connection onlyoffice and nextcloud with using self signed certs in local network (for examlpe i took your docker-compose.yml and our image onlyoffice/documentserver:latest), its work fine.

I did everything the same as you in the first post, with a few changes:
you need choose our official docker image image: onlyoffice/documentserver:latest and as @ShockwaveNN posted add USE_UNAUTHORIZED_STORAGE=true variable for ignore certs check, docker-compose.yml should look like this:

version: '2'
services:
  onlyoffice-documentserver:
    image: onlyoffice/documentserver:latest
    container_name: onlyoffice-documentserver
    depends_on:
      - onlyoffice-postgresql
      - onlyoffice-rabbitmq
    environment:
      - DB_TYPE=postgres
      - DB_HOST=onlyoffice-postgresql
      - DB_PORT=5432
      - DB_NAME=onlyoffice
      - DB_USER=onlyoffice
      - AMQP_URI=amqp://guest:guest@onlyoffice-rabbitmq
      - USE_UNAUTHORIZED_STORAGE=true
      # Uncomment strings below to enable the JSON Web Token validation.
      - JWT_ENABLED=true
      - JWT_SECRET=123123123
      - JWT_HEADER=AuthorizationJwt
      - JWT_IN_BODY=true
...

The nextcloud also has a certificate check, do not forget to disable it when setting up:

PS We have official documentation how Installing ONLYOFFICE Docs with docker here.

@igwyd commented on GitHub (May 31, 2022): hello @webagroprom, first of all, you are using someone else's docker container based on our product ```image: jiriks74/onlyoffice-documentserver:latest``` we won't be able to help with this. Our containers you can get from [docker hub](https://hub.docker.com/r/onlyoffice/documentserver/), and it should be ```image: onlyoffice/documentserver:latest```. I checked connection onlyoffice and nextcloud with using self signed certs in local network (for examlpe i took your docker-compose.yml and our image onlyoffice/documentserver:latest), its work fine. I did everything the same as you in the first post, with a few changes: you need choose our official docker image **image: onlyoffice/documentserver:latest** and as @ShockwaveNN posted add **USE_UNAUTHORIZED_STORAGE=true** variable for ignore certs check, docker-compose.yml should look like this: ``` version: '2' services: onlyoffice-documentserver: image: onlyoffice/documentserver:latest container_name: onlyoffice-documentserver depends_on: - onlyoffice-postgresql - onlyoffice-rabbitmq environment: - DB_TYPE=postgres - DB_HOST=onlyoffice-postgresql - DB_PORT=5432 - DB_NAME=onlyoffice - DB_USER=onlyoffice - AMQP_URI=amqp://guest:guest@onlyoffice-rabbitmq - USE_UNAUTHORIZED_STORAGE=true # Uncomment strings below to enable the JSON Web Token validation. - JWT_ENABLED=true - JWT_SECRET=123123123 - JWT_HEADER=AuthorizationJwt - JWT_IN_BODY=true ... ``` The nextcloud also has a certificate check, do not forget to disable it when setting up: ![NC](https://user-images.githubusercontent.com/67538082/171196333-bbc272bd-97a7-46be-bbab-ec4d10d141e2.jpg) PS We have official documentation how Installing ONLYOFFICE Docs with docker [here](https://helpcenter.onlyoffice.com/installation/docs-community-install-docker.aspx).

kerem commented

Author

Owner

@toonemastic commented on GitHub (Jun 1, 2022):

Hi,
The reason we are using image: jiriks74/onlyoffice-documentserver:latest is because the image: onlyoffice/documentserver:latest don't run on raspberry pi running on arm64.
This onlyoffice/documentserver:latest contains reference to amd64.

On my raspberry pi, I've git clone the repo https://github.com/ONLYOFFICE/Docker-DocumentServer and build the image whith errors.
I've modified in the line 76 of the Dockerfile the amd64 to arm64 and yes, the image is build.
I modify the image reference in the docker-compose.yml file to use this build image.
The result is the same ERROR] nodeJS - error downloadFile:url=... issue.

Regards,

Pierre

@toonemastic commented on GitHub (Jun 1, 2022): Hi, The reason we are using image: jiriks74/onlyoffice-documentserver:latest is because the image: onlyoffice/documentserver:latest don't run on raspberry pi running on arm64. This onlyoffice/documentserver:latest contains reference to amd64. On my raspberry pi, I've git clone the repo https://github.com/ONLYOFFICE/Docker-DocumentServer and build the image whith errors. I've modified in the line 76 of the Dockerfile the amd64 to arm64 and yes, the image is build. I modify the image reference in the docker-compose.yml file to use this build image. The result is the same ERROR] nodeJS - error downloadFile:url=... issue. Regards, Pierre

kerem commented

Author

Owner

@igwyd commented on GitHub (Jun 2, 2022):

@toonemastic your error and error @webagroprom different as i see. I don't see the topicstarter mentioning that he uses raspberry pi. I think you need other issue for arm64 or create new one if you dont find the same.
By the way we have an image for arm64 on docker hub - onlyoffice/documentserver:latest-arm64

@igwyd commented on GitHub (Jun 2, 2022): @toonemastic your error and error @webagroprom different as i see. I don't see the topicstarter mentioning that he uses raspberry pi. I think you need other issue for arm64 or create new one if you dont find the same. By the way we have an image for arm64 on [docker hub](https://hub.docker.com/layers/documentserver/onlyoffice/documentserver/latest-arm64/images/sha256-4c7b264cc5d7e08180d7b1359d9b773e3dd1bcf7a06c61d86d7aa3db634e676f?context=explore) - onlyoffice/documentserver:latest-arm64

kerem commented

Author

Owner

@toonemastic commented on GitHub (Jun 2, 2022):

Hi,

I've continue with the investigations.

Instead of having the onlyoffice-document server running on the same server as nextcloudpi,
I run the image on another raspberry pi server and after some settings, It Works.
to have only-office-cdocumentserver running in a docker container, we must tell him the nextcloud server to reach. The following line is added in the docker run command : --add-host nextcloudpitest:192.168.1.137 \

Here is the situation as it is now :

The image is the one build on a raspberry pi after changing amd64 to arm64. See my previous comment. That explains why I use the image toone/onlyoffice-documentserver:latest.
nextcloudpi server : 192.168.1.137
onlyoffice-documentserver : 192.168.1.139
self-signed certificate, as described in the doc : onlyoffice.crt and onlyoffice.key + dhparam.pem installed in the docker volume /app/onlyoffice/DocumentServer/data/certs.
/etc/hosts on onlyoffice-documentserver contains : 127.0.0.1 onlyoffice
/etc/hosts on nextcloudpi server contains : 192.168.1.139 onlyoffice
content of the bash script used to start the containers : start-onlyoffice-documentserver.sh
#--restart=always
docker run -i -t -d -p 444:443
--name onlyoffice-documentserver
--add-host nextcloudpitest:192.168.1.137
-v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice
-v /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data
-v /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice
-v /app/onlyoffice/DocumentServer/db:/var/lib/postgresql
-e JWT_ENABLED=true
-e JWT_SECRET=marbais85
-e JWT_HEADER=AuthorizationJwt
-e JWT_IN_BODY=true
-e SSL_CERTIFICAE_PATH=/var/www/onlyoffice/Data/certs/onlyoffice.crt
-e SSL_KEY_PATH=/var/www/onlyoffice/Data/certs/onlyoffice.key
-e SSL_DHPARAM_PATH=/var/www/onlyoffice/Data/certs/dhparam.pem
-e USE_UNAUTHORIZED_STORAGE=true
toone/onlyoffice-documentserver:latest

Of course, a docker-compose.yml can also be used.

Now that I know that the image is OK and compatible with nextcloud 24.0.1, I need to have nextcloud and the docker image running on the same raspberry pi.

I keep you updated.

Regards,

Pierre

@toonemastic commented on GitHub (Jun 2, 2022): Hi, I've continue with the investigations. - Instead of having the onlyoffice-document server running on the same server as nextcloudpi, - I run the image on another raspberry pi server and after some settings, It Works. - to have only-office-cdocumentserver running in a docker container, we must tell him the nextcloud server to reach. The following line is added in the docker run command : --add-host nextcloudpitest:192.168.1.137 \ Here is the situation as it is now : - The image is the one build on a raspberry pi after changing amd64 to arm64. See my previous comment. That explains why I use the image toone/onlyoffice-documentserver:latest. - nextcloudpi server : 192.168.1.137 - onlyoffice-documentserver : 192.168.1.139 - self-signed certificate, as described in the doc : onlyoffice.crt and onlyoffice.key + dhparam.pem installed in the docker volume /app/onlyoffice/DocumentServer/data/certs. - /etc/hosts on onlyoffice-documentserver contains : 127.0.0.1 onlyoffice - /etc/hosts on nextcloudpi server contains : 192.168.1.139 onlyoffice - content of the bash script used to start the containers : start-onlyoffice-documentserver.sh #--restart=always \ docker run -i -t -d -p 444:443 \ --name onlyoffice-documentserver \ --add-host nextcloudpitest:192.168.1.137 \ -v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice \ -v /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data \ -v /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice \ -v /app/onlyoffice/DocumentServer/db:/var/lib/postgresql \ -e JWT_ENABLED=true \ -e JWT_SECRET=marbais85 \ -e JWT_HEADER=AuthorizationJwt \ -e JWT_IN_BODY=true \ -e SSL_CERTIFICAE_PATH=/var/www/onlyoffice/Data/certs/onlyoffice.crt \ -e SSL_KEY_PATH=/var/www/onlyoffice/Data/certs/onlyoffice.key \ -e SSL_DHPARAM_PATH=/var/www/onlyoffice/Data/certs/dhparam.pem \ -e USE_UNAUTHORIZED_STORAGE=true \ toone/onlyoffice-documentserver:latest Of course, a docker-compose.yml can also be used. Now that I know that the image is OK and compatible with nextcloud 24.0.1, I need to have nextcloud and the docker image running on the same raspberry pi. I keep you updated. Regards, Pierre

kerem commented

Author

Owner

@toonemastic commented on GitHub (Jun 2, 2022):

Hi @igwyd

Thanks for the image. I will test it asap.

Pierre

@toonemastic commented on GitHub (Jun 2, 2022): Hi @igwyd Thanks for the image. I will test it asap. Pierre

kerem commented

Author

Owner

@toonemastic commented on GitHub (Jun 2, 2022):

Hi @igwyd

Image onlyoffice/documentserver:latest-arm64 runs OK.

Now I will try to run the image on the same raspberry pi server on which runs nextcloud. That was the issue I have before my test on two separate servers.

Pierre

@toonemastic commented on GitHub (Jun 2, 2022): Hi @igwyd Image onlyoffice/documentserver:latest-arm64 runs OK. Now I will try to run the image on the same raspberry pi server on which runs nextcloud. That was the issue I have before my test on two separate servers. Pierre

kerem commented

Author

Owner

@toonemastic commented on GitHub (Jun 3, 2022):

Hello all,

Just to say that nextcloud (nextcloudpi img : https://ownyourbits.com/nextcloudpi/) and the docker image onlyoffice/documentserver:latest-arm64 running on the same raspberry pi.

To start the image, I use the following bash script
export DOCKERHOST=$(ifconfig | grep -E "([0-9]{1,3}.){3}[0-9]{1,3}" | grep -v 127.0.0.1 | awk '{ print $2 }' | cut -f2 -d: | head -n1)
echo $DOCKERHOST
docker run -i -t -d -p 444:443
--restart=always
--name onlyoffice-documentserver
--add-host nextcloudpitest:$DOCKERHOST
-v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice
-v /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data
-v /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice
-v /app/onlyoffice/DocumentServer/db:/var/lib/postgresql
-e JWT_ENABLED=true
-e JWT_SECRET=secret
-e JWT_HEADER=AuthorizationJwt
-e JWT_IN_BODY=true
-e SSL_CERTIFICAE_PATH=/var/www/onlyoffice/Data/certs/onlyoffice.crt
-e SSL_KEY_PATH=/var/www/onlyoffice/Data/certs/onlyoffice.key
-e SSL_DHPARAM_PATH=/var/www/onlyoffice/Data/certs/dhparam.pem
-e USE_UNAUTHORIZED_STORAGE=true
onlyoffice/documentserver:latest-arm64
I launch the container and then I stop the container it, just to have the volumes created. I use this script to stop :
docker stop onlyoffice-documentserver
docker rm onlyoffice-documentserver
docker volume prune --force
I use self-signed certificate created with this script :
openssl genrsa -out onlyoffice.key 2048
openssl req -new -key onlyoffice.key -out onlyoffice.csr
openssl x509 -req -days 36500 -in onlyoffice.csr -signkey onlyoffice.key -out onlyoffice.crt
openssl dhparam -out dhparam.pem 2048
The end of the nextcloud config in /var/www/nextcloud/config/config.php contains :
'allow_local_remote_servers' => true,
'onlyoffice' =>
array (
'verify_peer_off' => true,
'jwt_secret' => 'secret',
'jwt_header' => 'AuthorizationJwt',
),
);
/etc/hosts must contain this line :
127.0.0.1 onlyoffice
Once it has been launch once, we can copy the certificate and key in the just created permanent volume /app/onlyoffice/DocumentServer/data/ in a certs directory, we need to create :
The directory /app/onlyoffice/DocumentServer/data/certs contains :
dhparam.pem
onlyoffice.crt
onlyoffice.key
Everything is set up. Now we can launch the container for good using the launch script. Because of the --restart=always option used in the docker run command, the container will restart after a reboot.
In nextcloud with the admin account, ncp in my case, we need to install the ONLYOFFICE connector and then to do the set up.
In the "ONLYOFFICE Docs address" field, we insert the address of the onlyoffice server, ie in my case : https://192.168.1.137:444/ and check the field "Disable certificate verification (insecure)"
Save the settings and the page will grow with more settings.
In the browser, we need to connect to the onlyoffice web site to accept the https exception to be able to use ONLYOFFICE without the error "ONLYOFFICE cannot be reached. Please contact admin". In the same browser, launch, ie in my case, https://192.168.1.137:444/, that IP address must be the same as the one used for the ONLYOFFICE connector setting.

So, after a lot of error and retries, a lot of search on Internet with not a lot of success but good ideas to read between the lines, I was able to make run on the same raspberry pi nextcloud and onlyoffice. It was tested on a rpi3B+ and when ok, I've redo the installation on a rpi4.

Thanks to the good job done by creating this docker image.

I'm sure that this report will help a lot of people.

Regards,

Pierre

@toonemastic commented on GitHub (Jun 3, 2022): Hello all, Just to say that nextcloud (nextcloudpi img : https://ownyourbits.com/nextcloudpi/) and the docker image onlyoffice/documentserver:latest-arm64 running on the same raspberry pi. - To start the image, I use the following bash script export DOCKERHOST=$(ifconfig | grep -E "([0-9]{1,3}\.){3}[0-9]{1,3}" | grep -v 127.0.0.1 | awk '{ print $2 }' | cut -f2 -d: | head -n1) echo $DOCKERHOST docker run -i -t -d -p 444:443 \ --restart=always \ --name onlyoffice-documentserver \ --add-host nextcloudpitest:$DOCKERHOST \ -v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice \ -v /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data \ -v /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice \ -v /app/onlyoffice/DocumentServer/db:/var/lib/postgresql \ -e JWT_ENABLED=true \ -e JWT_SECRET=secret \ -e JWT_HEADER=AuthorizationJwt \ -e JWT_IN_BODY=true \ -e SSL_CERTIFICAE_PATH=/var/www/onlyoffice/Data/certs/onlyoffice.crt \ -e SSL_KEY_PATH=/var/www/onlyoffice/Data/certs/onlyoffice.key \ -e SSL_DHPARAM_PATH=/var/www/onlyoffice/Data/certs/dhparam.pem \ -e USE_UNAUTHORIZED_STORAGE=true \ onlyoffice/documentserver:latest-arm64 - I launch the container and then I stop the container it, just to have the volumes created. I use this script to stop : docker stop onlyoffice-documentserver docker rm onlyoffice-documentserver docker volume prune --force - I use self-signed certificate created with this script : openssl genrsa -out onlyoffice.key 2048 openssl req -new -key onlyoffice.key -out onlyoffice.csr openssl x509 -req -days 36500 -in onlyoffice.csr -signkey onlyoffice.key -out onlyoffice.crt openssl dhparam -out dhparam.pem 2048 - The end of the nextcloud config in /var/www/nextcloud/config/config.php contains : 'allow_local_remote_servers' => true, 'onlyoffice' => array ( 'verify_peer_off' => true, 'jwt_secret' => 'secret', 'jwt_header' => 'AuthorizationJwt', ), ); - /etc/hosts must contain this line : 127.0.0.1 onlyoffice - Once it has been launch once, we can copy the certificate and key in the just created permanent volume /app/onlyoffice/DocumentServer/data/ in a certs directory, we need to create : The directory /app/onlyoffice/DocumentServer/data/certs contains : dhparam.pem onlyoffice.crt onlyoffice.key - Everything is set up. Now we can launch the container for good using the launch script. Because of the --restart=always option used in the docker run command, the container will restart after a reboot. - In nextcloud with the admin account, ncp in my case, we need to install the ONLYOFFICE connector and then to do the set up. - In the "ONLYOFFICE Docs address" field, we insert the address of the onlyoffice server, ie in my case : https://192.168.1.137:444/ and check the field "Disable certificate verification (insecure)" Save the settings and the page will grow with more settings. - In the browser, we need to connect to the onlyoffice web site to accept the https exception to be able to use ONLYOFFICE without the error "ONLYOFFICE cannot be reached. Please contact admin". In the same browser, launch, ie in my case, https://192.168.1.137:444/, that IP address must be the same as the one used for the ONLYOFFICE connector setting. So, after a lot of error and retries, a lot of search on Internet with not a lot of success but good ideas to read between the lines, I was able to make run on the same raspberry pi nextcloud and onlyoffice. It was tested on a rpi3B+ and when ok, I've redo the installation on a rpi4. Thanks to the good job done by creating this docker image. I'm sure that this report will help a lot of people. Regards, Pierre

kerem commented

Author

Owner

@webagroprom commented on GitHub (Jul 1, 2022):

hello @webagroprom, first of all, you are using someone else's docker container based on our product image: jiriks74/onlyoffice-documentserver:latest we won't be able to help with this. Our containers you can get from docker hub, and it should be image: onlyoffice/documentserver:latest. I checked connection onlyoffice and nextcloud with using self signed certs in local network (for examlpe i took your docker-compose.yml and our image onlyoffice/documentserver:latest), its work fine.

I did everything the same as you in the first post, with a few changes: you need choose our official docker image image: onlyoffice/documentserver:latest and as @ShockwaveNN posted add USE_UNAUTHORIZED_STORAGE=true variable for ignore certs check, docker-compose.yml should look like this:
version: '2'
services:
  onlyoffice-documentserver:
    image: onlyoffice/documentserver:latest
    container_name: onlyoffice-documentserver
    depends_on:
      - onlyoffice-postgresql
      - onlyoffice-rabbitmq
    environment:
      - DB_TYPE=postgres
      - DB_HOST=onlyoffice-postgresql
      - DB_PORT=5432
      - DB_NAME=onlyoffice
      - DB_USER=onlyoffice
      - AMQP_URI=amqp://guest:guest@onlyoffice-rabbitmq
      - USE_UNAUTHORIZED_STORAGE=true
      # Uncomment strings below to enable the JSON Web Token validation.
      - JWT_ENABLED=true
      - JWT_SECRET=123123123
      - JWT_HEADER=AuthorizationJwt
      - JWT_IN_BODY=true
...
The nextcloud also has a certificate check, do not forget to disable it when setting up:

PS We have official documentation how Installing ONLYOFFICE Docs with docker here.

I did everything as you said and got the following errors

Nextcloud admin panel:
Error while downloading the document file to be converted.) (версия 7.1.1.23)

log file:

Ошибка | onlyoffice | Exception: Возникла ошибка в службе документов: 
Error while downloading the document file to be converted./var/www/nextcloud/apps/onlyoffice/lib/documentservice.php - line 95: OCA\Onlyoffice\DocumentService->ProcessConvServResponceError()/var/www/nextcloud/apps/onlyoffice/lib/documentservice.php - line 446: OCA\Onlyoffice\DocumentService->GetConvertedUri()/var/www/nextcloud/apps/onlyoffice/controller/settingscontroller.php - line 175: OCA\Onlyoffice\DocumentService->checkDocServiceUrl()/var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 225: OCA\Onlyoffice\Controller\SettingsController->SaveAddress()/var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 133: OC\AppFramework\Http\Dispatcher->executeController()/var/www/nextcloud/lib/private/AppFramework/App.php - line 172: OC\AppFramework\Http\Dispatcher->dispatch()/var/www/nextcloud/lib/private/Route/Router.php - line 298: OC\AppFramework\App::main()/var/www/nextcloud/lib/base.php - line 1023: OC\Route\Router->match()/var/www/nextcloud/index.php - line 36: OC::handleRequest()
-- | -- | --

Full configuration:

docker-compose.yml

version: '2'
services:
  onlyoffice-documentserver:
    image: onlyoffice/documentserver:latest
    container_name: onlyoffice-documentserver
    depends_on:
      - onlyoffice-postgresql
      - onlyoffice-rabbitmq
    environment:
      - DB_TYPE=postgres
      - DB_HOST=onlyoffice-postgresql
      - DB_PORT=5432
      - DB_NAME=onlyoffice
      - DB_USER=onlyoffice
      - AMQP_URI=amqp://guest:guest@onlyoffice-rabbitmq
      - USE_UNAUTHORIZED_STORAGE=true
      # Uncomment strings below to enable the JSON Web Token validation.
      - JWT_ENABLED=true
      - JWT_SECRET=SecretMy123
      - JWT_HEADER=AuthorizationJwt
      - JWT_IN_BODY=true
      # Uncomment the line below to set larger file limits (about 1GB)
      #- LARGER_FILE_LIMITS=true
    ports:
      - '9050:80'
      - '9000:443'
    stdin_open: true
    restart: always
    stop_grace_period: 120s
    volumes:
       # Uncomment the line below to get access to the slide themes directory.
       # To use the themes, copy them to the slideThemes directory and run `docker exec -it <container-name> /usr/bin/documentserver-generate-allfonts.sh`
       #- ./slideThemes:/var/www/onlyoffice/documentserver/sdkjs/slide/themes/src
       #- /var/www/onlyoffice/Data
       #- /var/log/onlyoffice
       #- /var/lib/onlyoffice/documentserver/App_Data/cache/files
       #- /var/www/onlyoffice/documentserver-example/public/files
       #- /usr/share/fonts
        - /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice
        - /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data
        - /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice
        - /app/onlyoffice/DocumentServer/db:/var/lib/postgresql

  onlyoffice-rabbitmq:
    container_name: onlyoffice-rabbitmq
    image: rabbitmq
    restart: always
    expose:
      - '5672'

  onlyoffice-postgresql:
    container_name: onlyoffice-postgresql
    image: postgres:9.5
    environment:
      - POSTGRES_DB=onlyoffice
      - POSTGRES_USER=onlyoffice
      - POSTGRES_HOST_AUTH_METHOD=trust
    restart: always
    expose:
      - '5432'
    volumes:
      - postgresql_data:/var/lib/postgresql

volumes:
  postgresql_data:

docker-compose images:

onlyoffice-documentserver   onlyoffice/documentserver   latest   5a50e3a2d2ed   2.929 GB
onlyoffice-postgresql       postgres                    9.5      6d176851b77f   197.2 MB
onlyoffice-rabbitmq         rabbitmq                    latest   be6d544851f4   228.2 MB

SSL Certificate - Create OpenSSL:

-rw-r--r--   1 root root 1294 июл  1 15:28 onlyoffice.crt
-rw-r--r--   1 root root 1041 июл  1 15:27 onlyoffice.csr
-rw-------   1 root root 1679 июл  1 15:26 onlyoffice.key

Nextcloud 24 config:
/var/www/nextcloud/config/config.php

'onlyoffice' =>
  array (
    'jwt_secret' => 'SecretMy123',
    'jwt_header' => 'AuthorizationJwt',
    'verify_peer_off' => true,
  ),

netstat:
tcp6 0 0 :::9000 :::* LISTEN 775784/docker-proxy

run sudo docker-compose up -d

open https://localAdress:9000

Go to open nextcloud admin panel, onlyoffice:

The error is still valid.

What am I doing wrong ?
How can I fix this error ?

@webagroprom commented on GitHub (Jul 1, 2022): > hello @webagroprom, first of all, you are using someone else's docker container based on our product `image: jiriks74/onlyoffice-documentserver:latest` we won't be able to help with this. Our containers you can get from [docker hub](https://hub.docker.com/r/onlyoffice/documentserver/), and it should be `image: onlyoffice/documentserver:latest`. I checked connection onlyoffice and nextcloud with using self signed certs in local network (for examlpe i took your docker-compose.yml and our image onlyoffice/documentserver:latest), its work fine. > > I did everything the same as you in the first post, with a few changes: you need choose our official docker image **image: onlyoffice/documentserver:latest** and as @ShockwaveNN posted add **USE_UNAUTHORIZED_STORAGE=true** variable for ignore certs check, docker-compose.yml should look like this: > > ``` > version: '2' > services: > onlyoffice-documentserver: > image: onlyoffice/documentserver:latest > container_name: onlyoffice-documentserver > depends_on: > - onlyoffice-postgresql > - onlyoffice-rabbitmq > environment: > - DB_TYPE=postgres > - DB_HOST=onlyoffice-postgresql > - DB_PORT=5432 > - DB_NAME=onlyoffice > - DB_USER=onlyoffice > - AMQP_URI=amqp://guest:guest@onlyoffice-rabbitmq > - USE_UNAUTHORIZED_STORAGE=true > # Uncomment strings below to enable the JSON Web Token validation. > - JWT_ENABLED=true > - JWT_SECRET=123123123 > - JWT_HEADER=AuthorizationJwt > - JWT_IN_BODY=true > ... > ``` > > The nextcloud also has a certificate check, do not forget to disable it when setting up: ![NC](https://user-images.githubusercontent.com/67538082/171196333-bbc272bd-97a7-46be-bbab-ec4d10d141e2.jpg) > > PS We have official documentation how Installing ONLYOFFICE Docs with docker [here](https://helpcenter.onlyoffice.com/installation/docs-community-install-docker.aspx). **I did everything as you said and got the following errors** Nextcloud admin panel: **Error while downloading the document file to be converted.) (версия 7.1.1.23)** log file: ``` Ошибка | onlyoffice | Exception: Возникла ошибка в службе документов: Error while downloading the document file to be converted./var/www/nextcloud/apps/onlyoffice/lib/documentservice.php - line 95: OCA\Onlyoffice\DocumentService->ProcessConvServResponceError()/var/www/nextcloud/apps/onlyoffice/lib/documentservice.php - line 446: OCA\Onlyoffice\DocumentService->GetConvertedUri()/var/www/nextcloud/apps/onlyoffice/controller/settingscontroller.php - line 175: OCA\Onlyoffice\DocumentService->checkDocServiceUrl()/var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 225: OCA\Onlyoffice\Controller\SettingsController->SaveAddress()/var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 133: OC\AppFramework\Http\Dispatcher->executeController()/var/www/nextcloud/lib/private/AppFramework/App.php - line 172: OC\AppFramework\Http\Dispatcher->dispatch()/var/www/nextcloud/lib/private/Route/Router.php - line 298: OC\AppFramework\App::main()/var/www/nextcloud/lib/base.php - line 1023: OC\Route\Router->match()/var/www/nextcloud/index.php - line 36: OC::handleRequest() -- | -- | -- ``` **Full configuration:** **docker-compose.yml** ``` version: '2' services: onlyoffice-documentserver: image: onlyoffice/documentserver:latest container_name: onlyoffice-documentserver depends_on: - onlyoffice-postgresql - onlyoffice-rabbitmq environment: - DB_TYPE=postgres - DB_HOST=onlyoffice-postgresql - DB_PORT=5432 - DB_NAME=onlyoffice - DB_USER=onlyoffice - AMQP_URI=amqp://guest:guest@onlyoffice-rabbitmq - USE_UNAUTHORIZED_STORAGE=true # Uncomment strings below to enable the JSON Web Token validation. - JWT_ENABLED=true - JWT_SECRET=SecretMy123 - JWT_HEADER=AuthorizationJwt - JWT_IN_BODY=true # Uncomment the line below to set larger file limits (about 1GB) #- LARGER_FILE_LIMITS=true ports: - '9050:80' - '9000:443' stdin_open: true restart: always stop_grace_period: 120s volumes: # Uncomment the line below to get access to the slide themes directory. # To use the themes, copy them to the slideThemes directory and run `docker exec -it <container-name> /usr/bin/documentserver-generate-allfonts.sh` #- ./slideThemes:/var/www/onlyoffice/documentserver/sdkjs/slide/themes/src #- /var/www/onlyoffice/Data #- /var/log/onlyoffice #- /var/lib/onlyoffice/documentserver/App_Data/cache/files #- /var/www/onlyoffice/documentserver-example/public/files #- /usr/share/fonts - /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice - /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data - /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice - /app/onlyoffice/DocumentServer/db:/var/lib/postgresql onlyoffice-rabbitmq: container_name: onlyoffice-rabbitmq image: rabbitmq restart: always expose: - '5672' onlyoffice-postgresql: container_name: onlyoffice-postgresql image: postgres:9.5 environment: - POSTGRES_DB=onlyoffice - POSTGRES_USER=onlyoffice - POSTGRES_HOST_AUTH_METHOD=trust restart: always expose: - '5432' volumes: - postgresql_data:/var/lib/postgresql volumes: postgresql_data: ``` **docker-compose images:** ``` onlyoffice-documentserver onlyoffice/documentserver latest 5a50e3a2d2ed 2.929 GB onlyoffice-postgresql postgres 9.5 6d176851b77f 197.2 MB onlyoffice-rabbitmq rabbitmq latest be6d544851f4 228.2 MB ``` **SSL Certificate - Create OpenSSL:** ``` -rw-r--r-- 1 root root 1294 июл 1 15:28 onlyoffice.crt -rw-r--r-- 1 root root 1041 июл 1 15:27 onlyoffice.csr -rw------- 1 root root 1679 июл 1 15:26 onlyoffice.key ``` **Nextcloud 24 config:** /var/www/nextcloud/config/config.php ``` 'onlyoffice' => array ( 'jwt_secret' => 'SecretMy123', 'jwt_header' => 'AuthorizationJwt', 'verify_peer_off' => true, ), ``` **netstat:** tcp6 0 0 :::9000 :::* LISTEN 775784/docker-proxy **run** sudo docker-compose up -d **open** https://localAdress:9000 ![1656685529316](https://user-images.githubusercontent.com/30408997/176913560-d1558bec-4329-4a52-9943-7e0ae124c9cb.jpg) **Go to open nextcloud admin panel, onlyoffice:** ![1656684907208](https://user-images.githubusercontent.com/30408997/176911840-15ef1d62-d517-4423-9939-8187e2462d26.jpg) The error is still valid. What am I doing wrong ? How can I fix this error ?

kerem commented

Author

Owner

@igwyd commented on GitHub (Jul 8, 2022):

@webagroprom
Unfortunately I don't see any errors. For the test, I took 2 servers in the local network, one with nextcloud (this manual), the second with onlyoffice-documentserver and took your configs, everything works. In my opinion the problem might be with proxy nexcloud or some special settings and also check connector version for your nexcloud version. As you see by default it work.

@igwyd commented on GitHub (Jul 8, 2022): @webagroprom Unfortunately I don't see any errors. For the test, I took 2 servers in the local network, one with nextcloud (this [manual](https://help.nextcloud.com/t/howto-running-nextcloud-over-self-signed-https-ssl-tls-in-docker/101973)), the second with onlyoffice-documentserver and took your configs, everything works. In my opinion the problem might be with proxy nexcloud or some special settings and also check [connector version](https://apps.nextcloud.com/apps/onlyoffice#:~:text=ONLYOFFICE%20connector%20allows%20you%20to,document%20library%20for%20Office%20documents.) for your nexcloud version. As you see by default it work. ![screen](https://user-images.githubusercontent.com/67538082/177999069-bab73e36-846d-4d03-9665-97b9a0397ad8.png)

kerem commented