ONLYOFFICE DocSpace released: improve document collaboration with offices, customers, and partners. Use it for free!
ONLYOFFICE DocSpace released

Problem with onlyoffice + humhub

Connectors
#1

Do you want to: Report a (possible) bug
For bug reports, provide the steps to reproduce and if possible a minimal demo of the problem: Can not use anymore Onlyoffice in Humhub
Document Server version: 7.2.2.56
Connector version: 3.0.0
DMS (platform) version: humhub 1.13.2
OS: linux debian
Browser version:
Attach logs if possible.

Hi

We are running humhub 1.13.2 with the 3.0.0 onlyoffice connector. We have just notice that we can not create / edit / view any document in Humhub with Onlyoffice (enterprise edition). When we open a document to view/create/edit, the page shows a login form (see attached image). It worked before. We did not try yet to revert to the previous version of the connector (2.4.0). We did not find any explicit errors in the log files.

Thanks for any hint to solve this.

Karim

image
image1290×573 57.4 KB

#2

Same problem with the version 2.4.0 of the connector …

#3

It works with the demo onlyoffice server …

#4

Hello @karimb

First of all, please note that you are using an outdated version of Document Server. Please update your current instance and check the situation again after that.

If the problem still persists, share a screenshot of the settings of the connector app.
Additionally, please share content of local.json file. It can be found:

  • for Linux in /etc/onlyoffice/documentserver (same path inside Docker container);
  • for Windows in %ProgramFiles%\ONLYOFFICE\DocumentServer\config.
#7

We have upgraded to 7.3.3.49 and the problem still persists. The local.json file is :

{

  "services": {

    "CoAuthoring": {

      "sql": {

        "type": "postgres",

        "dbHost": "localhost",

        "dbPort": "5432",

        "dbName": "onlyoffice",

        "dbUser": "onlyoffice",

        "dbPass": "onlyoffice"

      },

      "redis": {

        "host": "localhost"

      },

      "token": {

        "enable": {

          "request": {

            "inbox": true,

            "outbox": true

          },

          "browser": true

        },

        "inbox": {

          "header": "AuthorizationJwt",

          "inBody": true

        },

        "outbox": {

          "header": "AuthorizationJwt",

          "inBody": true

        }

      },

      "secret": {

        "inbox": {

          "string": "xxxxxxxxxxxxx"

        },

        "outbox": {

          "string": "xxxxxxxxxxx"

        },

        "session": {

          "string": "xxxxxxxxxxxxxx"

        }

      }

    }

  },

  "rabbitmq": {

    "url": "amqp://guest:guest@localhost"

  },

  "storage": {

    "fs": {

      "secretString": "xxxxxxxxxxxx"

    }

  }

}

image
image846×451 30.7 KB

Thanks for any hint

Karim

#8

image
image844×486 32.3 KB

#9

Hello @karimb

Thanks for the info.
I’ve noted that the values of secret strings marked with xxxxxx have different length. Please make sure that the values of secret key, i.e. values in string, of all three instances are the same first:

After that please copy that value and paste it into Secret field in the connector app setting and then do the same with header by pasting its value to the Header:

If you have changed any values, remember to apply them by restarting Document Server services with systemctl restart ds-*.

After that check the situation again.

#10

Hi
Thanks for the reply
The string for inbox, outbox and session is the same in the real local.json.
which password do you mean for header ? If i set the same string as for Secret then same problem
Cheers
Karim

#11

Hello @karimb

Here is the header from your local.json:

So in the connector settings please use AuthorizationJwt in the Header field.

#12

Many thanks !!!
It is ok now !

1 Like
#13

I’m glad to hear that it works now.

1 Like