Most certainly 403 is related to the JWT Token on the Community Server side. I would not recommend disabling JWT Token since it provides a security of your connection and prevents data from being fetched by unauthorized users.
To configure JWT Token on both sides please follow next instruction:
- Locate next config var/www/onlyoffice/WebStudio/web.appsettings.config in the Community Server container (use
docker ps
to see the list of currently running containers anddocker exec -it <ID> bash
where<ID>
is the ID of the container to connect to it); - In the web.appsettings.config locate next strings:
<add key="files.docservice.secret" value="<your_secret>" />
<add key="files.docservice.secret.header" value="<your_header>" />
and copy somewhere values <your_secret>
and <your_header>
.
- Connect to Document Server container and open next config /etc/onlyoffice/documentserver/local.json;
- In local.json find next section:
"token": {
"enable": {
"request": {
"inbox": true,
"outbox": true
},
"browser": true
},
"inbox": {
"header": "<your_header>",
"inBody": false
},
"outbox": {
"header": "<your_header>",
"inBody": false
}
},
"secret": {
"inbox": {
"string": "<your_secret>"
},
"outbox": {
"string": "<your_secret>"
},
"session": {
"string": "<your_secret>"
and set inbox
, outbox
and browser
values to true
as it shown above to make sure that JWT is enabled and paste <your_secret> and <your_header> from web.appsettings.config to the string
and header
strings according to the example above.
- Restart Document Server services with
supervisorctl restart all
to apply these changes and try editing documents again.
Basically, you have to make sure that <your_secret>
and <your_header>
are corresponding in both configs.
Let me know if you face any difficulties.