Maggi0r 2 Posted April 27, 2020 Share Posted April 27, 2020 I found the problem and solved it myself. I deleted the folder in appdata once with rmv and then restarted the Docker after which it ran. Regards Maggi 1 Quote Link to post
patm95 2 Posted April 28, 2020 Share Posted April 28, 2020 17 hours ago, Maggi0r said: I found the problem and solved it myself. I deleted the folder in appdata once with rmv and then restarted the Docker after which it ran. Regards Maggi Glad to hear it Maggi. I just now saw your post. Glad you figured it out. I don't think I would have. Great work! Quote Link to post
Jessie 9 Posted May 16, 2020 Share Posted May 16, 2020 On 4/27/2020 at 2:00 AM, Maggi0r said: First of all, thanks for this guide, it is identical to the Space Invader. Except for the lower case of the container. However, I don't want to find a connection from OnlyOffice to the document server stat I get the following message in the Office settings when I want to save my document server. "Error connecting" bad Helthchek status " and in the document server log this is here "[2020-04-26T15: 58: 00.846] [ERROR] nodeJS - healthCheck error error: password authentication failed for user "onlyoffice" I hope you can continue helping me there. My subdomain is entered in the LE container and also ok. Regards Maggi Not sure whether relevant but I've just gone through this exercise and had a win. Install the documentserver docker as per spaceinvader tutorial, except don't do the cert copy stuff. Rename the docker to "documentserver" (all lower case), then in linuxservers letsencrypt docker there is a config file ready to go. It will update the certs automatically. Just rename the file without the .sample on the end and restart. 1 2 Quote Link to post
Predator68RS 0 Posted November 11, 2020 Share Posted November 11, 2020 @Maggi0r can you please elaborate on how you fixed this error? I'm stuck with the same problem... what folder did you remove, what else did you do? Thanks! Quote Link to post
yogy 13 Posted November 16, 2020 Share Posted November 16, 2020 (edited) I've successfully setup ONLYOFFICE to work in my self hosted Nextcloud instance. Like many others here I use NginxProxyManager to setup reverse proxy and get a certificate from Let's Encrypt for my subdomains. As already mentioned here you don't need to create any config files and copying certificate and private key to a newly created folder certs in appdata ...... I think anyone who added at least one proxy host to NginxProxyManager with SSL certificate from Let's Encrypt pointing to the newly created subdomain will be able to configure OnlyOffice Document Server to work properly with Nextcloud. If not I will gladly provide some assistance. My main intention here is creating a brief HOW TO in order to restrict the access to ONLYOFFICE Document Server (for security reasons and data integrity) with encrypted signature, known as Secret Key. Let me emphasize that I don't own the credit for this tutorial, I'm just posting something found among user comments in @SpaceInvaderOne YouTube video tutorial How to Install and Integrate Only Office with Nextcloud. Many, many thanks to @SpaceInvaderOne for providing great tutorials for us "nerds" and make our experience with unRAID easier. HOW TO add and configure Secret Key in ONLYOFFICE: Stop the OnlyOffice Document Server container. In the "edit" option for the OnlyOffice Document Server docker, do "+ Add another Path, Port, Variable, Label or Device". Config Type: Variable Name: JWT_ENABLED (can be whatever you want to see in the UI, I used the key) Key: JWT_ENABLED Value: true Description: Enables use of Secret key [press ADD] Then add another variable: Config Type: Variable Name: JWT_SECRET (same thing, up to you) Key: JWT_SECRET Value: [WhateverSecretKeyYouWantToUse]. You can use the following command in Terminal (without quotes) to create a random Secret Key: "openssl rand -base64 48" and press Enter Description: Defines the Secret key value [press ADD] [press APPLY] Start OnlyOffice Document Server container. Go to Nextcloud > Settings > ONLYOFFICE page. Enter the Secret Key and click Save (you should get the message: Settings have been successfully updated ..... No restart of the Nextcloud docker was needed. Edited November 16, 2020 by yogy 1 1 Quote Link to post
Aceriz 3 Posted December 15, 2020 Share Posted December 15, 2020 On 11/16/2020 at 4:13 PM, yogy said: I've successfully setup ONLYOFFICE to work in my self hosted Nextcloud instance. Like many others here I use NginxProxyManager to setup reverse proxy and get a certificate from Let's Encrypt for my subdomains. As already mentioned here you don't need to create any config files and copying certificate and private key to a newly created folder certs in appdata ...... I think anyone who added at least one proxy host to NginxProxyManager with SSL certificate from Let's Encrypt pointing to the newly created subdomain will be able to configure OnlyOffice Document Server to work properly with Nextcloud. If not I will gladly provide some assistance. My main intention here is creating a brief HOW TO in order to restrict the access to ONLYOFFICE Document Server (for security reasons and data integrity) with encrypted signature, known as Secret Key. Let me emphasize that I don't own the credit for this tutorial, I'm just posting something found among user comments in @SpaceInvaderOne YouTube video tutorial How to Install and Integrate Only Office with Nextcloud. Many, many thanks to @SpaceInvaderOne for providing great tutorials for us "nerds" and make our experience with unRAID easier. HOW TO add and configure Secret Key in ONLYOFFICE: Stop the OnlyOffice Document Server container. In the "edit" option for the OnlyOffice Document Server docker, do "+ Add another Path, Port, Variable, Label or Device". Config Type: Variable Name: JWT_ENABLED (can be whatever you want to see in the UI, I used the key) Key: JWT_ENABLED Value: true Description: Enables use of Secret key [press ADD] Then add another variable: Config Type: Variable Name: JWT_SECRET (same thing, up to you) Key: JWT_SECRET Value: [WhateverSecretKeyYouWantToUse]. You can use the following command in Terminal (without quotes) to create a random Secret Key: "openssl rand -base64 48" and press Enter Description: Defines the Secret key value [press ADD] [press APPLY] Start OnlyOffice Document Server container. Go to Nextcloud > Settings > ONLYOFFICE page. Enter the Secret Key and click Save (you should get the message: Settings have been successfully updated ..... No restart of the Nextcloud docker was needed. Thank you so much for this !! Quote Link to post
patm95 2 Posted December 27, 2020 Share Posted December 27, 2020 On 11/11/2020 at 10:11 AM, Predator68RS said: @Maggi0r can you please elaborate on how you fixed this error? I'm stuck with the same problem... what folder did you remove, what else did you do? Thanks! I think she deleted the whole folder in appdata. Then when you restart the container, it will basically redownload everything. I was getting a similar issue when I upgraded to Nextcloud 20 and that seemed to help me. Quote Link to post
32 posts in this topic Last Reply
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.