[GH-ISSUE #290] Allow turning off TLS verification from env variable #154

Closed
opened 2026-02-26 09:37:05 +03:00 by kerem · 4 comments
Owner

Originally created by @SleepingShell on GitHub (Sep 15, 2020).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/290

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

What is the current behavior?
You must edit the /etc/onlyoffice/documentserver/default.json to set rejectUnauthorized, however editing this file does not do anything when the server is already running as a container.

What is the expected behavior?
Have an environment variable that can set 'rejectUnauthorized' to false before the document server is actually started.

Did this work in previous versions of DocumentServer?
No, this has been discussed in #96 . The suggested workaround on that issue is to rebuild the docker image every update with the edited file, but that is not very feasible.

Originally created by @SleepingShell on GitHub (Sep 15, 2020). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/290 **Do you want to request a *feature* or report a *bug*?** feature **What is the current behavior?** You must edit the /etc/onlyoffice/documentserver/default.json to set rejectUnauthorized, however editing this file does not do anything when the server is already running as a container. **What is the expected behavior?** Have an environment variable that can set 'rejectUnauthorized' to false before the document server is actually started. **Did this work in previous versions of DocumentServer?** No, this has been discussed in #96 . The suggested workaround on that issue is to rebuild the docker image every update with the edited file, but that is not very feasible.
kerem 2026-02-26 09:37:05 +03:00
Author
Owner

@ShockwaveNN commented on GitHub (Sep 16, 2020):

Hi

The suggested workaround on that issue is to rebuild the docker image every update with the edited file

I may be wrong, but rebuilding of image every update is not needed if used like I described here
https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/96#issuecomment-506295760

But in general - I agree, specific option for this would be great. @agolybev any thoughts?

<!-- gh-comment-id:693248280 --> @ShockwaveNN commented on GitHub (Sep 16, 2020): Hi > The suggested workaround on that issue is to rebuild the docker image every update with the edited file I may be wrong, but rebuilding of image every update is not needed if used like I described here https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/96#issuecomment-506295760 But in general - I agree, specific option for this would be great. @agolybev any thoughts?
Author
Owner

@SleepingShell commented on GitHub (Sep 16, 2020):

Hi

The suggested workaround on that issue is to rebuild the docker image every update with the edited file

I may be wrong, but rebuilding of image every update is not needed if used like I described here
#96 (comment)

But in general - I agree, specific option for this would be great. @agolybev any thoughts?

You're right I didn't try that solution due to the one person saying it didn't work, but it I can confirm that solution works (although needs to be updated with new directory names). Although it is definitely hacky.

<!-- gh-comment-id:693572041 --> @SleepingShell commented on GitHub (Sep 16, 2020): > Hi > > > The suggested workaround on that issue is to rebuild the docker image every update with the edited file > > I may be wrong, but rebuilding of image every update is not needed if used like I described here > [#96 (comment)](https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/96#issuecomment-506295760) > > But in general - I agree, specific option for this would be great. @agolybev any thoughts? You're right I didn't try that solution due to the one person saying it didn't work, but it I can confirm that solution works (although needs to be updated with new directory names). Although it is definitely hacky.
Author
Owner

@igwyd commented on GitHub (Nov 18, 2024):

Hello @SleepingShell, sorry for the late reply. It's implemented USE_UNAUTHORIZED_STORAGE=true https://github.com/ONLYOFFICE/Docker-DocumentServer?tab=readme-ov-file#available-configuration-parameters

<!-- gh-comment-id:2482678014 --> @igwyd commented on GitHub (Nov 18, 2024): Hello @SleepingShell, sorry for the late reply. It's implemented ```USE_UNAUTHORIZED_STORAGE=true``` https://github.com/ONLYOFFICE/Docker-DocumentServer?tab=readme-ov-file#available-configuration-parameters
Author
Owner

@Rita-Bubnova commented on GitHub (Nov 18, 2024):

I close this issue. Feel free to comment or reopen it if you got further questions.

<!-- gh-comment-id:2482705185 --> @Rita-Bubnova commented on GitHub (Nov 18, 2024): I close this issue. Feel free to comment or reopen it if you got further questions.
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#154
No description provided.