Token is improperly formed

Docs
1

Hi. I installed Onlyofflice stricly following documentation for Redhat and derivatives (no docker). It installed fine, but now it complains about the token to be improperly formed. I tried to meddle with local.json without any luck. Right after the installation and configuration using configure script this file looks like that:

{
“services”: {
“CoAuthoring”: {
“sql”: {
“dbHost”: “localhost”,
“dbName”: “onlyoffice”,
“dbUser”: “onlyoffice”,
“dbPass”: “REDACTED”
},
“redis”: {
“host”: “localhost”
},
“token”: {
“enable”: {
“request”: {
“inbox”: false,
“outbox”: false
},
“browser”: false
},
“inbox”: {
“header”: “Authorization”
},
“outbox”: {
“header”: “Authorization”
}
},
“secret”: {
“inbox”: {
“string”: “secret”
},
“outbox”: {
“string”: “secret”
},
“session”: {
“string”: “secret”
}
}
}
},
“rabbitmq”: {
“url”: “amqp://guest:guest@localhost”
}
}

I have passwd JWT_SECRET to Seafile config, but it also doesn’t work.

From what I understood from the docks that secret should be in the local.json. So it seems it is not generated after installation. Help please.

2

Hello @platyna

Sorry for the late reply.
As I can see from your local.json - you have disabled JWT token for Document Server. Did you restart all Document Server afterwards to apply changes? If not then double check the values of "inbox", "outbox" and "browser" being set to false from this section:

      "token": {
        "enable": {
          "request": {
            "inbox": false,
            "outbox": false
          },
          "browser": false
        },

and restart all Document Server services with supervisorctl restart all to apply them. After that check the situation and provide a feedback.