[GH-ISSUE #504] Since upgrade to 7.2: "Can't download document" #241

Closed
opened 2026-02-26 10:31:15 +03:00 by kerem · 9 comments
Owner

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

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

Since upgrading the server to 7.2, I get the dreaded "Download failed" message.

This is what I see when trying to update the settings in Nextcloud:

(Client error: GET https://******/cache/files/data/conv_check_2132774431_docx/output.docx/check_********.docx?md5=*****************&expires=****************&filename=check_*********.docx resulted in a 403 Forbidden * response:

I have run docker container logs -f onlyoffice to see what is happening on the document server side, but nothing appears in the logs at the moment the failure occurs.

Downgrading the docker image to 7.1 lets it work again.
DocumentServer Docker tag:

latest

Host Operating System:

Ubuntu 20.04

Originally created by @vasyugan on GitHub (Sep 26, 2022). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/504 **Do you want to request a *feature* or report a *bug*?** Bug **What is the current behavior?** Since upgrading the server to 7.2, I get the dreaded "Download failed" message. This is what I see when trying to update the settings in Nextcloud: `(Client error: GET https://******/cache/files/data/conv_check_2132774431_docx/output.docx/check_********.docx?md5=*****************&expires=****************&filename=check_*********.docx resulted in a 403 Forbidden * response:` I have run docker container logs -f onlyoffice to see what is happening on the document server side, but nothing appears in the logs at the moment the failure occurs. Downgrading the docker image to 7.1 lets it work again. **DocumentServer Docker tag:** latest **Host Operating System:** Ubuntu 20.04
kerem closed this issue 2026-02-26 10:31:15 +03:00
Author
Owner

@Magneticdud commented on GitHub (Sep 26, 2022):

Same here, I was thinking I did some mistake with the setup, instead looks like not, because with tag 7.1 works fine

<!-- gh-comment-id:1257886708 --> @Magneticdud commented on GitHub (Sep 26, 2022): Same here, I was thinking I did some mistake with the setup, instead looks like not, because with tag 7.1 works fine
Author
Owner

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

Do you configured (or disabled) JWT correctly?

Because since v7.2 JWT with random key enabled by default for more secure setup

Read more details about this in http://docserverurl/welcome

<!-- gh-comment-id:1258079729 --> @ShockwaveNN commented on GitHub (Sep 26, 2022): Do you configured (or disabled) JWT correctly? Because since v7.2 JWT with random key enabled by default for more secure setup Read more details about this in `http://docserverurl/welcome`
Author
Owner

@Magneticdud commented on GitHub (Sep 26, 2022):

For 7.2 I am using a key specified in the docker-config.yml file

If i browse the container with docker exec, the content of /etc/onlyoffice/documentserver/local.json has my jwt key

<!-- gh-comment-id:1258091529 --> @Magneticdud commented on GitHub (Sep 26, 2022): For 7.2 I am using a key specified in the `docker-config.yml` file If i browse the container with `docker exec`, the content of `/etc/onlyoffice/documentserver/local.json` has my jwt key
Author
Owner

@vasyugan commented on GitHub (Sep 26, 2022):

Do you configured (or disabled) JWT correctly?

Because since v7.2 JWT with random key enabled by default for more secure setup

yes, the secret is configured correctly. I enabled it a long ago, I also set the JWT header, but since the upgrade to 7.1, it doesn't work anymore. I checked with command at the URL you provided.

I should say that the way I have enabled the JWT secret is through a local.json which mounted as a docker volume. I did this because passing the JWT secret and header via docker environment just never worked for me, whatever the reason.

<!-- gh-comment-id:1258096154 --> @vasyugan commented on GitHub (Sep 26, 2022): > Do you configured (or disabled) JWT correctly? > > Because since v7.2 JWT with random key enabled by default for more secure setup yes, the secret is configured correctly. I enabled it a long ago, I also set the JWT header, but since the upgrade to 7.1, it doesn't work anymore. I checked with command at the URL you provided. I should say that the way I have enabled the JWT secret is through a local.json which mounted as a docker volume. I did this because passing the JWT secret and header via docker environment just never worked for me, whatever the reason.
Author
Owner

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

You should not mount local.json for JWT kets, it will cause problems for 100%

For other cases I think we need a way to reproduce, maybe sample simplified docker-compose

<!-- gh-comment-id:1258139580 --> @ShockwaveNN commented on GitHub (Sep 26, 2022): You should not mount local.json for JWT kets, it will cause problems for 100% For other cases I think we need a way to reproduce, maybe sample simplified docker-compose
Author
Owner

@vasyugan commented on GitHub (Sep 26, 2022):

You should not mount local.json for JWT kets, it will cause problems for 100%

For other cases I think we need a way to reproduce, maybe sample simplified docker-compose

I see. But how do I set JWT header then, or has it been deprecated? Asking because setting its value via docker environment doesn't do anything for me.

<!-- gh-comment-id:1258142218 --> @vasyugan commented on GitHub (Sep 26, 2022): > You should not mount local.json for JWT kets, it will cause problems for 100% > > For other cases I think we need a way to reproduce, maybe sample simplified docker-compose I see. But how do I set JWT header then, or has it been deprecated? Asking because setting its value via docker environment doesn't do anything for me.
Author
Owner

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

It's not deprecated but may be some bug, so need some scenarios

<!-- gh-comment-id:1258145814 --> @ShockwaveNN commented on GitHub (Sep 26, 2022): It's not deprecated but may be some bug, so need some scenarios
Author
Owner

@vasyugan commented on GitHub (Sep 26, 2022):

Thanks a lot! Actually, now setting jwt_header via --env JWT_HEADER actually works, so whatever caused this not to work in the past seems to be straightened out.

I have removed the mount for local.json and instead use the random string for jwt_secret generated on startup, so that's also fine.

<!-- gh-comment-id:1258193828 --> @vasyugan commented on GitHub (Sep 26, 2022): > Thanks a lot! Actually, now setting jwt_header via --env JWT_HEADER actually works, so whatever caused this not to work in the past seems to be straightened out. I have removed the mount for local.json and instead use the random string for jwt_secret generated on startup, so that's also fine.
Author
Owner

@ShockwaveNN commented on GitHub (Oct 9, 2022):

Closing this issue, since problem seems be resolved

<!-- gh-comment-id:1272587515 --> @ShockwaveNN commented on GitHub (Oct 9, 2022): Closing this issue, since problem seems be resolved
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Docker-DocumentServer-ONLYOFFICE#241
No description provided.