File conversion error -7

Docs API
,
23

local.json

{
  "services": {
    "CoAuthoring": {
      "sql": {
        "type": "postgres",
        "dbHost": "onlyoffice-postgresql",
        "dbPort": "5432",
        "dbName": "onlyoffice",
        "dbUser": "onlyoffice",
        "dbPass": "onlyoffice"
      },
      "token": {
        "enable": {
          "request": {
            "inbox": true,
            "outbox": true
          },
          "browser": true
        },
        "inbox": {
          "header": "Authorization",
          "inBody": false
        },
        "outbox": {
          "header": "Authorization",
          "inBody": false
        }
      },
      "secret": {
        "inbox": {
          "string": "zPJt4JIUvpVNYTMMSvknsZtZUvSJKV8g"
        },
        "outbox": {
          "string": "zPJt4JIUvpVNYTMMSvknsZtZUvSJKV8g"
        },
        "session": {
          "string": "zPJt4JIUvpVNYTMMSvknsZtZUvSJKV8g"
        }
      }
    }
  },
  "rabbitmq": {
    "url": "amqp://guest:guest@onlyoffice-rabbitmq"
  },
  "queue": {
    "type": "rabbitmq"
  },
  "storage": {
    "fs": {
      "secretString": "bjVJdH5ZAbXsrZ35DMwr"
    }
  }
}
24

Hello, I found out a problem, my token wasnot correct.

Now I have a question, why conversation API needs Key?

What if I try to convert one wile many times? will it take it from cache or everytime it generates new file?

25

@aigyr

congratulations :ok_hand:

You need a key to generate new documents.

ds will take it from cache. By the way, you can see how it happens.
Cache is stored in the directory:

/var/lib/onlyoffice/documentserver/App_Data/cache/files/data

(in docker)

26

查看 @ aigyr 的解决方案
“上次的令牌不正确”

27

If i send one file twice, will it generate a new converted file each time? or second time it will take from cache?

28

@Nikolas What is the current situation with my question

29

Hello @aigyr

Yes, it will take document from the cache for the second request if you use the say key for the second request since the document has been converted already. To avoid that you can simply use another key.

Hello @liyaxuan

Please see how @aigyr solved this issue:

Make sure that you are passing JWT correctly. If you still struggle with this, please share body of the request and example of how you are passing the JWT authentication.