[support] Siwat's Docker Repository


449 posts in this topic Last Reply

Recommended Posts

5 hours ago, showstopper said:

 

I initially thought it was $upstream_docs and $upstream_app that was the issue. After lots of tinkering yesterday it now all works.

They're just variables, aren't they? Pretty sure you could just as easily make it $left_bananas

What did you do to eventually get it working? It looks like you just stripped a bunch of configs from spaceinvader1, and I'm not sure what they do. What ended up working for you?

Link to post
  • Replies 448
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Yeah i have the same. I havent had time to look into this as yet but a quick fix is roll back to the earlier container. In the template change repository to add :6.0 on the end so onlyoffice/

I had quite a bit of trouble getting OnlyOfficeDocumentServer to work with nextcloud and letsencrypt. So I had letsencrypt install for plex etc and got it working with nextcloud. The confusing part of

These instructions should be stickied! THANK YOU!

Posted Images

1 minute ago, 4554551n said:

They're just variables, aren't they? Pretty sure you could just as easily make it $left_bananas

What did you do to eventually get it working? It looks like you just stripped a bunch of configs from spaceinvader1, and I'm not sure what they do. What ended up working for you?

 

In all honesty I don't know what eventually made it work. I deleted the folder from appdata, and then reinstalled it. It then suddenly started working again.

Link to post
On 2/25/2021 at 9:02 AM, showstopper said:

 

In all honesty I don't know what eventually made it work. I deleted the folder from appdata, and then reinstalled it. It then suddenly started working again.

 

can you repost your final "working" onlyoffice proxy config for us. thanks.

 

Link to post
10 hours ago, Tolete said:

 

can you repost your final "working" onlyoffice proxy config for us. thanks.

 

 

Sure - here:


 

# only office doc server


server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name external_dns_subdomain.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app OnlyOfficeDocumentServer;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_max_temp_file_size 2048m;
    }
}

 

Link to post

 

16 hours ago, showstopper said:

 

Sure - here:


 



# only office doc server


server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name external_dns_subdomain.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app OnlyOfficeDocumentServer;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_max_temp_file_size 2048m;
    }
}

 

 

yeah no joy here.

Surprisingly running a different onlyoffice document server image (chvb) same proxy config all works well.

When i attempt to run the official onlyoffice document server image (SIWATS) i get a 400 bad request :(. Send help!

 

Edited by Tolete
Link to post
1 hour ago, Tolete said:

 

 

yeah no joy here.

Surprisingly running a different onlyoffice document server image (chvb) same proxy config all works well.

When i attempt to run the official onlyoffice document server image (SIWATS) i get a 400 bad request :(. Send help!

 

The thing is I use pfSense’s HAProxy and it seems to work fine, I haven’t tried NGINX’s proxy_pass yet. So if the other image works for you, that may be your solution.

Link to post
11 hours ago, Siwat2545 said:

The thing is I use pfSense’s HAProxy and it seems to work fine, I haven’t tried NGINX’s proxy_pass yet. So if the other image works for you, that may be your solution.

I think a lot of your users will be using it with linuxsever.io containers of swag and nextcloud, as per the video by spaceinvader (let'sencrypt is now swag)
But it seems to pass through fine, but still gives the 400 error

Link to post
10 hours ago, 4554551n said:

I think a lot of your users will be using it with linuxsever.io containers of swag and nextcloud, as per the video by spaceinvader (let'sencrypt is now swag)
But it seems to pass through fine, but still gives the 400 error

that's correct.

Link to post

Hey   wondering   I have this your excellent docker all setup and working with Nextcloud :)  But am wondering when I try and enable within nextcloud the Use OnlyOffice to generate a Document preview... I keep getting an error below   

 

Is the preview option not something supported ?   or do I have to do somethign different in the setup ?

 

Exception: Error occurred in the document service: Error while downloading the document file to be converted.
/config/www/nextcloud/apps/onlyoffice/lib/documentservice.php - line 94:

OCA\Onlyoffice\DocumentService->ProcessConvServResponceError()

/config/www/nextcloud/apps/onlyoffice/lib/preview.php - line 266:

OCA\Onlyoffice\DocumentService->GetConvertedUri()

/config/www/nextcloud/lib/private/Preview/ProviderV1Adapter.php - line 54:

OCA\Onlyoffice\Preview->getThumbnail()

/config/www/nextcloud/lib/private/Preview/GeneratorHelper.php - line 63:

OC\Preview\ProviderV1Adapter->getThumbnail()

/config/www/nextcloud/lib/private/Preview/Generator.php - line 244:

OC\Preview\GeneratorHelper->getThumbnail()

/config/www/nextcloud/lib/private/Preview/Generator.php - line 140:

OC\Preview\Generator->getMaxPreview()

/config/www/nextcloud/lib/private/Preview/Generator.php - line 109:

OC\Preview\Generator->generatePreviews()

/config/www/nextcloud/lib/private/PreviewManager.php - line 190:

OC\Preview\Generator->getPreview()

/config/www/nextcloud/core/Controller/PreviewController.php - line 170:

OC\PreviewManager->getPreview()

/config/www/nextcloud/core/Controller/PreviewController.php - line 143:

OC\Core\Controller\PreviewController->fetchPreview()

/config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 218:

OC\Core\Controller\PreviewController->getPreviewByFileId()

/config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 127:

OC\AppFramework\Http\Dispatcher->executeController()

/config/www/nextcloud/lib/private/AppFramework/App.php - line 157:

OC\AppFramework\Http\Dispatcher->dispatch()

/config/www/nextcloud/lib/private/Route/Router.php - line 302:

OC\AppFramework\App::main()

/config/www/nextcloud/lib/base.php - line 993:

OC\Route\Router->match()

/config/www/nextcloud/index.php - line 37:

OC::handleRequest()

 

Link to post

I was able to 'fix' OnlyOfficeDocumentServer by pointing my reverse proxy to http instead of https. Its less a fix and more a workaround, but it got me up and running again. I noticed that if I tried pulling up the /welcome page by connecting directly instead of via nextcloud that I get nothing, but http is working fine.

Edited by rjlan
Typo
Link to post
  • 3 weeks later...
On 3/6/2021 at 10:49 PM, rjlan said:

I was able to 'fix' OnlyOfficeDocumentServer by pointing my reverse proxy to http instead of https. Its less a fix and more a workaround, but it got me up and running again. I noticed that if I tried pulling up the /welcome page by connecting directly instead of via nextcloud that I get nothing, but http is working fine.

My config that used HAProxy also point to HTTP too, internal networks are typically secure, Proxy are used as an SSL Offloader.

 

BTW, latest Documents Server seems to be stable now, version bumped to latest.

Link to post

I use SWAG, since I'm far from knowledgeable on this topic! I usually follow SpaceInvader One and his videos, but I know it usually just a scratch on the surface. But I haven't gotten it to work. I still get a "Error when trying to connect (Bad healthcheck status)✖" when I try to get it to work. But when I access the Document Server from the docker (WebUI) or the website (that I use in the proxy), I go to the OnlyOffice docker server. So the docker works? Maybe SWAG also works?

My question is; is this a SWAG problem? Maybe a Nextcloud problem? or is it something on the bug-fix-table?

 

I really want it to work, but I also know there might be a lot of work in it. #NoStress

Thank you again @Siwat2545 for making it possible :)

 

(I use the OnlyOfficeDocumentServer, not the OnlyOffice Document Server. I don't really know what the difference is :E)

Link to post
  • 3 weeks later...
On 3/27/2021 at 6:06 AM, Michelle Bausager said:

I use SWAG, since I'm far from knowledgeable on this topic! I usually follow SpaceInvader One and his videos, but I know it usually just a scratch on the surface. But I haven't gotten it to work. I still get a "Error when trying to connect (Bad healthcheck status)✖" when I try to get it to work. But when I access the Document Server from the docker (WebUI) or the website (that I use in the proxy), I go to the OnlyOffice docker server. So the docker works? Maybe SWAG also works?

My question is; is this a SWAG problem? Maybe a Nextcloud problem? or is it something on the bug-fix-table?

 

I really want it to work, but I also know there might be a lot of work in it. #NoStress

Thank you again @Siwat2545 for making it possible :)

 

(I use the OnlyOfficeDocumentServer, not the OnlyOffice Document Server. I don't really know what the difference is :E)

I have the same exact issue and the same exact problem using NPM.  I'm able to connect to documentserver.mydomain.com withouth issue and I can see the 'Congratulations' webpage from OnlyOffice.  So I'm 99.9% sure my Reverse proxy is working correctly or else I wouldn't even be able to reach that webpage.  As soon as I put the address into the OnlyOffice settings page from within NextCloud I also get the "Bad Healthcheck" error. 

 

I've nuked, removed, destroyed, exploded both Docker containers over and over a few hundred times now (saw a few posts mentioning that it just started working when they did a fresh install of one or the other) but still, every time "Bad Healthcheck". 

 

I've tried to set it up from my local 192.XX..XX.XX and also connecting to it from my Domain still always the same error message "Bad Healthcheck". 

 

I've gone to the /r/UnRaid reddit thread asking for help there but no one seems to know.  Figured I'd check on here but it doesn't bode well if you asked for help last month and still haven't received a reply / solution.

Link to post
5 minutes ago, CoZ said:

I have the same exact issue and the same exact problem using NPM.  I'm able to connect to documentserver.mydomain.com withouth issue and I can see the 'Congratulations' webpage from OnlyOffice.  So I'm 99.9% sure my Reverse proxy is working correctly or else I wouldn't even be able to reach that webpage.  As soon as I put the address into the OnlyOffice settings page from within NextCloud I also get the "Bad Healthcheck" error. 

 

I've nuked, removed, destroyed, exploded both Docker containers over and over a few hundred times now (saw a few posts mentioning that it just started working when they did a fresh install of one or the other) but still, every time "Bad Healthcheck". 

 

I've tried to set it up from my local 192.XX..XX.XX and also connecting to it from my Domain still always the same error message "Bad Healthcheck". 

 

I've gone to the /r/UnRaid reddit thread asking for help there but no one seems to know.  Figured I'd check on here but it doesn't bode well if you asked for help last month and still haven't received a reply / solution.

Quick question, are your proxy pointing to http or https of onlyoffice? and are your certificate installed in onlyoffice

Link to post
10 minutes ago, Siwat2545 said:

Quick question, are your proxy pointing to http or https of onlyoffice? and are your certificate installed in onlyoffice

 

I'm not entirely sure what you're asking but I will do my best to try and answer it. Externally if I use my domain, it's an https://office.mydomain*com and it connects to Nextcloud.

 

As far as the certs, there isn't a need to do that using NPM (as far as I know, that is, because I haven't had to copy any certs from anywhere into anything else).  The certs are installed "in" the docker container for NPM. Might be the same for SWAG as well since NPM changed from NPM to SWAG (but I haven't made the move over to it as of yet).

Link to post
4 minutes ago, CoZ said:

 

I'm not entirely sure what you're asking but I will do my best to try and answer it. Externally if I use my domain, it's an https://office.mydomain*com and it connects to Nextcloud.

 

As far as the certs, there isn't a need to do that using NPM (as far as I know, that is, because I haven't had to copy any certs from anywhere into anything else).  The certs are installed "in" the docker container for NPM. Might be the same for SWAG as well since NPM changed from NPM to SWAG (but I haven't made the move over to it as of yet).

What are your proxy configuration?

Link to post

@Siwat2545 ok sorry for the delay, tried as fast as I could.

 

This screenshot shows the Nextcloud NPM reverse proxy settings.

 

This screenshot shows your DocumentServer reverse proxy settings.

 

I'm able to connect to https://documentserver.mydomain.com  without any issue, I get the ONLYOFFICE Docs™ Community Edition – Welcome!  without issue - either connecting to it internally from my local IP or externally from documentserver.mydomain.com  I'm also able to connect to my Nextcloud install either through office.mydomain.com or, internally using my IP

 

So this has me thinking that my reverse proxy set up is working properly for both.  Just always get the Bad Healthcheck error message when attempting to get the two to talk to each other.  I've checked and unchecked every option under the NextCloud OnlyOffice connector settings app but still no good.

Link to post
Posted (edited)
6 minutes ago, CoZ said:

@Siwat2545 ok sorry for the delay, tried as fast as I could.

 

This screenshot shows the Nextcloud NPM reverse proxy settings.

 

This screenshot shows your DocumentServer reverse proxy settings.

 

I'm able to connect to https://documentserver.mydomain.com  without any issue, I get the ONLYOFFICE Docs™ Community Edition – Welcome!  without issue - either connecting to it internally from my local IP or externally from documentserver.mydomain.com  I'm also able to connect to my Nextcloud install either through office.mydomain.com or, internally using my IP

 

So this has me thinking that my reverse proxy set up is working properly for both.  Just always get the Bad Healthcheck error message when attempting to get the two to talk to each other.  I've checked and unchecked every option under the NextCloud OnlyOffice connector settings app but still no good.

The problem is probably with your reverse proxy, the two will refuse to talk if the certificate does not match.

I don't really know how gui get change in to conf, do you happen to have an nginx server block for onlyoffice?

Edited by Siwat2545
Link to post
3 minutes ago, Siwat2545 said:

The problem is probably with your reverse proxy, the two will refuse to talk if the certificate does not match.

I don't really know how gui get change in to conf, do you happen to have an nginx server block for onlyoffice?

Not that I'm aware of having a server block for onlyoffice.

 

 

I've no idea how to copy certificates or, if it's even possible since they are both using different SSL certs that were assigned to them by NGINX.  Unless maybe I can try to assign the office.mydomain.com certificate to the documentserver.mydomain.com

 

I've got even more issues now with Nextcloud, I've grenaded and wiped my install so many times, I'm running out of 'fake admin/user names' to try.  I've wiped the appdata/nextcloud folder from the SSD and I've cleared out my mnt/nextcloud folder share but for some insane strange reason, the docker still remembers all the user names I've entered previously which makes NO sense at all since the appdata folder is deleted along with the template and all the data. 

 

I'm about to throw a grenade right into my Unraid tower itself at this point.  I've been messing with this for 3 days now and it gets worse and worse the more I try to fix it. LOL

Link to post
1 minute ago, CoZ said:

Not that I'm aware of having a server block for onlyoffice.

 

 

I've no idea how to copy certificates or, if it's even possible since they are both using different SSL certs that were assigned to them by NGINX.  Unless maybe I can try to assign the office.mydomain.com certificate to the documentserver.mydomain.com

 

I've got even more issues now with Nextcloud, I've grenaded and wiped my install so many times, I'm running out of 'fake admin/user names' to try.  I've wiped the appdata/nextcloud folder from the SSD and I've cleared out my mnt/nextcloud folder share but for some insane strange reason, the docker still remembers all the user names I've entered previously which makes NO sense at all since the appdata folder is deleted along with the template and all the data. 

 

I'm about to throw a grenade right into my Unraid tower itself at this point.  I've been messing with this for 3 days now and it gets worse and worse the more I try to fix it. LOL

In my setup, I use one wildcard certificate that cover both nextcloud and onlyoffice install. maybe you can try that?

Link to post
1 minute ago, Siwat2545 said:

In my setup, I use one wildcard certificate that cover both nextcloud and onlyoffice install. maybe you can try that?

 

I just tried to assign the same CERT that nextcloud uses to the document server and now I've gotten a new error message:

 

Error when trying to connect (cURL error 60: SSL: no alternative certificate subject name matches target host name 'documentserver.MYDOMAIN.com' (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://documentserver.MYDOMAIN.com/healthcheck)

 

 

so I don't think that's going to work that way either.

Link to post

When I check the box that says Disable Certificate verification I get this message (When using the CERT from the nextcloud proxy):

 

Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 6.2.1.24)

 

Link to post
Posted (edited)
1 hour ago, CoZ said:

 

I just tried to assign the same CERT that nextcloud uses to the document server and now I've gotten a new error message:

 



Error when trying to connect (cURL error 60: SSL: no alternative certificate subject name matches target host name 'documentserver.MYDOMAIN.com' (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://documentserver.MYDOMAIN.com/healthcheck)

 

 

so I don't think that's going to work that way either.

That suggest that the certificate is not wildcarded at the sub domain level

Edited by Siwat2545
Link to post
8 hours ago, Siwat2545 said:

That suggest that the certificate is not wildcarded at the sub domain level

 

I see no way to edit the cert that NGINX assigns to the subdomain.  You just add a new certificate for the subdomain you're trying to forward and it assigns the cert.  There are no options or configurations for the cert.  I can only renew now or delete the cert.

 

The only option to do anything at all is under the proxy host:
 

Nginx variables available to you are:


$server # Host/IP

$port # Port Number

$forward_scheme # http or https

 

I went into appdata/NginxProxyManager/letsencrypt/keys and that directory is blank.  I then took a look into NginxProxyManager/nginx/proxy_host and found a bunch of randomly titled files in there finally found one that points to something:

 

# ------------------------------------------------------------
# office.MYDOMAIN.com
# ------------------------------------------------------------


server {
  set $forward_scheme https;
  set $server         "192.168.1.102";
  set $port           444;

  listen 8080;
listen [::]:8080;

listen 4443 ssl http2;
listen [::]:4443;


  server_name office.MYDOMAIN.com;


  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-24/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-24/privkey.pem;

 

It continues on and I don't want to clutter up the thread any more by posting the whole thing if this isn't relevant.

Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.