You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
SleepingShell
changed the title
Allow turning of TLS verification from env variable
Allow turning off TLS verification from env variable
Sep 15, 2020
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.
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.
The text was updated successfully, but these errors were encountered: