Siwat2545

July 13, 2021

1 hour ago, Michelle Bausager said:

If I change it back to https in nextcloud, when it's back to the old error again.

& the original config still ends in a forever loop :E

what happens when you visit the url using chrome?

July 13, 2021

2 hours ago, Michelle Bausager said:

It still enters a forever-loop with the log saying;
"nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/onlyoffice.subdomain.conf:19"

over and over again.

If I comment the line out again & change the https to http;

and change the address to http;

I get another error now:

Error when trying to connect (Mixed Active Content is not allowed. HTTPS address for Document Server is required.)

only change to http in nginx configuration.
Here's what it's doing, nextcloud make a https request to nginx, nginx forward that to document server with http. so nextcloud still see the server as https.

July 13, 2021

On 7/11/2021 at 2:21 PM, Michelle Bausager said:

I've been here before, unfortunately I suddenly had to take some months out of the calendar & didn't get any closer to a sulotion But I'm back

To start with, I don't have a great knowledge of network protocols & usually take baby steps Last time I was here, the question arised if my proxy was pointing to http or https of onlyoffice, as fair as I know, it's https. But I'll hust walk you through what I have done & how far I've come If anyone have the time to help, it would be awesome.

I followed Spaceinvader One's video: https://www.youtube.com/watch?v=dEOfwKH2DHc&t=190s

When I had to copy the credentials I substatuded the Let's Encrypt folder to Swag as:

mkdir /mnt/user/appdata/onlyofficeds/Data/certs

cp /mnt/user/appdata/Swag/keys/cert.crt /mnt/user/appdata/onlyofficeds/Data/certs/onlyoffice.crt

cp /mnt/user/appdata/Swag/keys/cert.key /mnt/user/appdata/onlyofficeds/Data/certs/onlyoffice.key

After that I used the .conf file he provided and changed 433 ports to 4330, since I ude that as my 'Host Port 2'

When I then restarted the Swag Docker, an error appeared

If I comment the ''include /config/nginx/proxy.conf;" out it doen't end in a forever loop and it acually starts up.

When I use this .conf file, the error in nexcloud says:

Otherwise it's just a "Server not found" or something like that.

As far as my understanding goes, in the .conf file, it refers to it as a 'https', which means it point to it as a https? I think :s

I hope someone can help me, it's not critical, but it would be nice to get it up & running.
Thank you again for your great work

try proxy_pass to http instead of https

June 29, 2021

So I umount the disks then stop mdadm then yeet the plug.

Formatting went fine, running correcting parity-check right now

June 29, 2021

It been 30 minutes already

Here's the diagnosis

Ignore the CRC error, I already tried replacing the cable, it doesn't go away.

mainserver-diagnostics-20210629-0903.zip

June 9, 2021

50 minutes ago, Iceman24 said:

I'm getting this warning from Fix Common Problems and the fix doesn't stop the scan from still reporting the warning. Fix appears to have been applied okay.

Template URL for docker application AdGuard-Home is not the as what the template author specified.The template URL the author specified is https://raw.githubusercontent.com/sgraaf/Unraid-Docker-Templates/main/adguardhome/template.xml. The template can be updated automatically with the correct URL.

when you edit the container, what is in your ‘repository’ field?

May 24, 2021

1 hour ago, luk said:

no one can help me?

Since I only ported the official container, I do not know the inner working of these logs, I suggest that you ask here https://dev.onlyoffice.org/viewforum.php?f=4&sid=c5c0ec08795675163814c27b1f6577be

May 21, 2021

6 minutes ago, luk said:

Hi,

do you have already any solution for this? I have same issue...

Regards,

Luk

What seem to be the problem, does the web ui does not show up?

April 16, 2021

3 hours ago, CoZ said:
You just confused me. So you're saying I should be using THAT SSL cert for both the office.mydomain and the documentserver.mydomain or the other SSL cert for both office.mydomain & documentserver.mydomain?

I'll uncheck the HSTS

EDIT:

Still the same error:
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)
Using the SSL for the Nextcloud reverse proxy

Using the SSL for OnlyOffice proxy I get this error:
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)
So not sure where to go from here... both result in completely different error messages.

NVM, I confused HSTS with CORS, I don’t really know how to solve this as I do not use NGINX based reverse-proxy, but I heard that people got it working when DS have the correct certificates (in Data/certs directory)

April 15, 2021

1 hour ago, CoZ said:

Found it! I thought it was "gone" since I removed it and placed the CERT from the Nextcloud SSL into the DocumentServer Proxy to try and fix this whole mess but it's still present on the system since I never deleted it, just selected the "office.mydomain.com" SSL


# ------------------------------------------------------------
# documentserver.MYDOMAIN.com
# ------------------------------------------------------------


server {
  set $forward_scheme http;
  set $server         "192.168.1.102";
  set $port           9090;

  listen 8080;
listen [::]:8080;

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


  server_name documentserver.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;






  # Block Exploits
  include conf.d/include/block-exploits.conf;



  # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
  add_header Strict-Transport-Security "max-age=63072000;includeSubDomains; preload" always;





  access_log /config/log/proxy_host-25.log proxy;







  location / {

    


    # Force SSL
    include conf.d/include/force-ssl.conf;




  # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
  add_header Strict-Transport-Security "max-age=63072000;includeSubDomains; preload" always;





    
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    

    # Proxy!
    include conf.d/include/proxy.conf;
  }


  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

Looks good to me, try disabling HSTS

April 15, 2021

1 hour ago, CoZ said:
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.

What you just post there is called the server block, can I see one for the onlyofficeds? it should have a directive "server_name onlyoffice.MYDOMAIN.com"

April 15, 2021

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

April 15, 2021

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?

April 15, 2021

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?

April 15, 2021

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?

April 15, 2021

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

April 8, 2021

On 4/4/2021 at 1:08 AM, PicPoc said:

Can you post a pict ?

Is it always aivable on unRAID v6.8.x + ?

Thanks !

Do it in windows https://www.howtogeek.com/240840/should-you-use-the-balanced-power-saver-or-high-performance-power-plan-on-windows/

March 21, 2021

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.

March 1, 2021

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.

February 24, 2021

6 minutes ago, 4554551n said:

@Siwat2545
Can you please help us out? We would really appreciate it

Can you still access the web UI, or is the web UI is up and you can’t connect to it using nextcloud

PS. I’m in the middle of a midterm exam RN, sorry for the late reply.

February 16, 2021

1 hour ago, 4554551n said:

So that makes at least 3..
@Siwat2545 please help?

Set your Repository as follow

February 15, 2021

2 hours ago, 4554551n said:

I've been having this exact issue for a couple of months now.
@Siwat2545 could you please advise?

These are the instructions here.
It worked for me when I first set it up, then one day just broke.
Error when trying to connect (Client error: `GET https://[mydomain]/healthcheck` resulted in a `400 Bad Request` response: 400 Bad Request 400 Bad Request ngin (truncated...) )

Which version of the docker are you on?

January 31, 2021

7 hours ago, yogy said:

I'm using OnlyOfficeDocumentServer (from onlyoffice). Since the recent update I don't have onlyoffice icon anymore (? simbol in grey colour). When I check the Icon URL in Dockers Advanced View it says https://pbs.twimg.com/profile_images/801693107125362689/al5MQBQM_normal.jpg. Entering the link to the browser leads to an error. Can someone please post the correct link.

I’ll update it tomorrow

January 22, 2021

On 12/7/2020 at 11:45 PM, Siwat2545 said:

Interesting I’ll look into this when I’m free.

Looked into it, outta idea, maybe a debian bug?, template is now defaulted to v6.0 for now

January 22, 2021

4 hours ago, Grapes said:

I tired to update my homebridge docker container the other day and now I just get the following in the docker log file:


Get:1 https://deb.nodesource.com/node_12.x bionic InRelease [4584 B]
Ign:2 http://archive.ubuntu.com/ubuntu eoan InRelease
Ign:3 http://security.ubuntu.com/ubuntu eoan-security InRelease
Get:4 https://deb.nodesource.com/node_12.x bionic/main amd64 Packages [767 B]
Ign:5 http://archive.ubuntu.com/ubuntu eoan-updates InRelease
Err:6 http://security.ubuntu.com/ubuntu eoan-security Release
404 Not Found [IP: 91.189.88.142 80]
Ign:7 http://archive.ubuntu.com/ubuntu eoan-backports InRelease
Err:8 http://archive.ubuntu.com/ubuntu eoan Release
404 Not Found [IP: 91.189.88.142 80]
Err:9 http://archive.ubuntu.com/ubuntu eoan-updates Release
404 Not Found [IP: 91.189.88.142 80]
Err:10 http://archive.ubuntu.com/ubuntu eoan-backports Release
404 Not Found [IP: 91.189.88.142 80]
Reading package lists...
E: The repository 'http://security.ubuntu.com/ubuntu eoan-security Release' no longer has a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu eoan Release' no longer has a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu eoan-updates Release' no longer has a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu eoan-backports Release' no longer has a Release file.
Reading package lists...
E: The repository 'http://security.ubuntu.com/ubuntu eoan-security Release' no longer has a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu eoan Release' no longer has a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu eoan-updates Release' no longer has a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu eoan-backports Release' no longer has a Release file.

404 Not Found [IP: 91.189.88.152 80]
Get:154 http://archive.ubuntu.com/ubuntu eoan/universe amd64 libaacs0 amd64 0.9.0-2 [50.1 kB]
Get:155 http://archive.ubuntu.com/ubuntu eoan/universe amd64 libbdplus0 amd64 0.1.2-3 [47.3 kB]
Err:156 http://archive.ubuntu.com/ubuntu eoan/main amd64 libgdk-pixbuf2.0-bin amd64 2.40.0+dfsg-1build1
404 Not Found [IP: 91.189.88.152 80]
Err:157 http://archive.ubuntu.com/ubuntu eoan/main amd64 librsvg2-common amd64 2.44.14-1
404 Not Found [IP: 91.189.88.152 80]
Err:158 http://archive.ubuntu.com/ubuntu eoan-updates/universe amd64 mesa-va-drivers amd64 19.2.8-0ubuntu0~19.10.3
404 Not Found [IP: 91.189.88.152 80]
Err:159 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 mesa-vdpau-drivers amd64 19.2.8-0ubuntu0~19.10.3
404 Not Found [IP: 91.189.88.152 80]
Err:160 http://archive.ubuntu.com/ubuntu eoan/universe amd64 i965-va-driver amd64 2.3.0-0ubuntu2

404 Not Found [IP: 91.189.88.152 80]
Err:161 http://archive.ubuntu.com/ubuntu eoan/universe amd64 va-driver-all amd64 2.5.0-1

404 Not Found [IP: 91.189.88.152 80]
Err:162 http://archive.ubuntu.com/ubuntu eoan/main amd64 vdpau-driver-all amd64 1.2-1ubuntu1

404 Not Found [IP: 91.189.88.152 80]
Fetched 18.4 MB in 7s (2518 kB/s)
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/f/fribidi/libfribidi0_1.0.5-3.1ubuntu0.19.10.1_amd64.deb 404 Not Found [IP: 91.189.88.152 80]

E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/x/xkeyboard-config/xkb-data_2.26-2ubuntu2_all.deb 404 Not Found [IP: 91.189.88.152 80]

E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/libd/libdrm/libdrm-common_2.4.99-1ubuntu1_all.deb 404 Not Found [IP: 91.189.88.152 80]

E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/libd/libdrm/libdrm2_2.4.99-1ubuntu1_amd64.deb 404 Not Found [IP: 91.189.88.152 80]

E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/libp/libpng1.6/libpng16-16_1.6.37-1_amd64.deb 404 Not Found [IP: 91.189.88.152 80]

E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/libu/libusb-1.0/libusb-1.0-0_1.0.23-1_amd64.deb 404 Not Found [IP: 91.189.88.152 80]

Any ideas? Looks like the /etc/apt/sources.list repos need to be updated in the image.

Updated! 🙂

Siwat2545

Posts

Joined

Last visited

Days Won

Content Type

Profiles

Forums

Downloads

Store

Gallery

Bug Reports

Documentation

Landing

Posts posted by Siwat2545

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

Array stuck on formatting....

Array stuck on formatting....

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[SOLVED] VM is always paused

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository

[support] Siwat's Docker Repository