Jump to content

sse450

Members
  • Content Count

    90
  • Joined

  • Last visited

Community Reputation

1 Neutral

About sse450

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @aptalca Thank you for the hint. But, second sentence in your reply is important. It is not very clear tome. I do reverse proxy using LE docker. But, I think that onlyoffice still needs the certs in its /Data/certs directory. Am I wrong? How do just reverse proxying solve that issue without certs in OO docker?
  2. @aptalca , thank you for indicating the readme file. I successfully mounted LE config folder to onlyoffice docker. Howver, I still need to present the certs in the filenames onlyoffice required onlyoffice.crt, onlyoffice.key. Should I use "ln -s" or create a cron job to copy LE certs in the filenames required? I would appreciate any advice. Thank you.
  3. Onlyoffice DS docker needs the certificates installed in /mnt/user/appdata/onlyofficeds/Data/certs folder. I copied the certs from letsencrypt to this folder. It works. But, I need to find a way to automate the certs from LE docker as the static LE certs in onlyoffice docker will expire in max. 3 months. How can I do that? Does a symbolic link to LE certs work? Or should I set a cron job to copy LE certs everyday? Thanks.
  4. I know it is an old thread. But, @livingonline8, thank you very much for the method you explained. I finally could install onlyoffice with nextcloud. I have two questions though: 1. I copied certs from letsencrypt to onlyoffice/Data/certs folder. But what will happen when the certs expire? Should not it be integrated to letsencrypt docker somehow? Will it suffice to create two symbolic links to the LE certs in folder letsencrypt/keys? 2. In the onlyoffice.subdomain.com file, proxy pass directive is using port 443. Isn't it 4430? We use 443 for letsencrypt docker. Thanks.
  5. I am using latest docker image with Calibre 4.5. I cannot enter any non-ascii characters in calibre metadata edit window. However, if I install Calibre on my PC (Ubuntu), then this problem disappears. There must be some char encoding problem with the docker, or I have a misconfiguration. I would appreciate any help.
  6. I am not sure when it started, but having problem with this Calibre docker lately. When double click on the book in the main window, calibre viewer opens in the same main window of Calibre. The problem is there is no control in the viewer to close the viewer and get us back to the main window. So, as soon as I open the viewer, I am stuck with the viewer until I restart the docker. I believe the viewer should open in a new tab. Standalone installations open the viewer in a separate window. Hence, no problem with them. Thanks.
  7. Gosh! So easy. Feeling stupid. Thank you. Sent from my SM-G955F using Tapatalk
  8. I cleared and added a new drive to the array. But ended up with an "unmountable" drive. Here is the screenshot: I would appreciate any hint to fix it. Thank you.
  9. Thank you very much for the docker. Works nicely. I have a request if possible. Would you please install "ingest-attachment" plugin in the docker. Nextcloud needs it for indexing. It can be added by /bin/elasticsearch-plugin install ingest-attachment
  10. Old ISP: Your Public IPv4 is: 176.88.224.xxx Your IPv6 is: Not Detected Your Local IP is: 10.10.30.30 New ISP: Your Public IPv4 is: 78.188.71.yyy Your IPv6 is: Not Detected Your Local IP is: 10.10.30.30 Note: If I use the old ISP but without revising the IP in Cloudflare settings, I get exactly the same errors in NC. Note2: Related NC docker nginx log entry: 2019/03/21 14:49:35 [error] 314#314: *15995 upstream sent invalid status "0" while reading response header from upstream, client: 172.17.0.1, server: _, request: "GET /index.php/apps/richdocuments/settings/check HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "cloud.mydomain.com:443" Note3: Perhaps, port 80 is blocked by the new ISP. I temporarily forward port 80 to a webpage on the same Unraid. And checked it using some web tools. Not blocked. Note4: Re-installed LE docker from scratch. Renewed certificates but the problem persists. Frustrated. Kill me.
  11. I don't know where the correct tree is Hence, asking for help. Today, I did a very useful test. Currently, both ISPs, the old and the new, have connection at the same location. I reversed back to the old ISP and changed the IP number to that of old ISP at Cloudflare DNS settings. Collabora is again started working nicely. So, it looks it is related to the new ISP connection. If it is nothing to do with letsencrypt certs, then what could it be? Router (pfSense) is the same with forwarded ports 80 and 443 to 81 and 443, respectively. Thanks for your support. More Info on my setup: 1. I use your collabora and linuxserver's nextcloud and letsencrypt dockers. 2. Nextcloud and collabora are setup as subdomains. Setup procedure as per your guide. 3. I use wildcard with Cloudflare plugin in Letsencrypt settings. 4. NC: 15.0.5, Collabora: 4.0.2, Letsencrypt: Latest LS docker, Collabora Plugin NC: 3.2.4 4. The error in NC log is as below: Error PHP Undefined offset: 0 at /config/www/nextcloud/lib/private/AppFramework/Http.php#150 2019-03-21T12:20:17+0300 Error PHP Cannot declare class GuzzleHttp\Handler\CurlFactory, because the name is already in use at /config/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php#15 2019-03-21T12:20:17+0300 Error richdocuments GuzzleHttp\Exception\ConnectException: cURL error 28: Connection timed out after 5001 milliseconds (see http://curl.haxx.se/libcurl/c/libcurl-errors.html) 2019-03-21T12:20:17+0300 Someone had solved this problem by stating "Solved! it was an expired certificate for the loolwsd server." (https://github.com/nextcloud/server/issues/11278). That's why I wanted to force renew the certs.
  12. Due to change of ISP, I had to change my static IP in Cloudflare DNS records. As soon as I did that, my collabora and nextcloud stopped working together. I am receiving errors in NC and documents don't open. I checked NC/Collabora forums and found that this error is related to the invalid certificates. I feel that it is related to the letsencrypt certificates as issued for the old IP. My question is, is there a way to force renewing certificates? Thanks
  13. Hello Fellow Unraiders, All of a sudden, my Collabora stopped working with Nextcloud. Both work independently. When I try to open a document, Nextcloud gives the following errors: Error PHP Cannot declare class GuzzleHttp\Handler\CurlFactory, because the name is already in use at /config/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php#15 2019-03-20T14:07:30+0300 Error richdocuments GuzzleHttp\Exception\ConnectException: cURL error 28: Connection timed out after 5001 milliseconds (see http://curl.haxx.se/libcurl/c/libcurl-errors.html) 2019-03-20T14:07:30+0300 Error PHP Undefined offset: 0 at /config/www/nextcloud/lib/private/AppFramework/Http.php#150 And a pop up message on Nextcloud UI says "Failed to load Collabora online. Please try again later." All I did just before this problem was to change the static IP of the server and subdomains on Cloudflare DNS. I am not sure if this is any related with the issue. Nextcloud is setup as subdomain behind letsencrypt docker as outlined in this forum. Does this error ring any bell? Pretty cryptic for me. Thanks.