Only Office (error: bad healthcheck status)

[Wong]

I followed the SpaceInvader video for setting up OnlyOffice. However at the very last step when I click save, an error pop out and say "Error when trying to connect (bad healthcheck status". I did tried to remove the cert and key file and recopy again but still not working. I am still a newbie. Could anyone tell me what is the problem?

 

I have copy and paste my conf file below for referrence as well: -

 

# only office doc server

server {
    listen 443 ssl;

    server_name onlyoffice.*;

    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_docs OnlyOfficeDocumentServer;
                proxy_pass https://$upstream_docs:443;
                proxy_redirect off;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Host $server_name;
                proxy_set_header X-Forwarded-Proto $scheme;
        }
}

 

 

Edited August 3, 2020 by Wong

[graphius]

I had used the same tutorial, and everything was working great until I did some updates on my server, now I get the above error. I have checked proxy files, recopied certs, checked permissions, etc and they are correct as far as I can tell...

[showstopper]

I guess you guys didn't get this working? I have just started to look into integrating openoffice into my nextcloud (21.0.0) and I am getting the same error. Any advice?

[deghimon]

Also followed the video, getting the same error. Anyone have a solution to this problem?

[clusterbox]

I can't explain why this fixed it (and honestly it concerns me that it did) but here's what I did:

 

1) Stop the OnlyOfficeDocumentServer container

2) Delete all the folders in `/appData/openofficeds` *EXCEPT* `/Data/certs`

3) Start the OnlyOfficeDocumentServer container and let it rebuild everything

4) Go back into Nextcloud --> Settings--> ONLYOFFICE and add `https://<ds_subdomain>.<your_domain>.com/`

5) Click "Save".

 

Profit!

 

Now.. why was this necessary??

[Stitch0815]

On 4/19/2021 at 2:10 AM, clusterbox said:

I can't explain why this fixed it (and honestly it concerns me that it did) but here's what I did:

 

1) Stop the OnlyOfficeDocumentServer container

2) Delete all the folders in `/appData/openofficeds` *EXCEPT* `/Data/certs`

3) Start the OnlyOfficeDocumentServer container and let it rebuild everything

4) Go back into Nextcloud --> Settings--> ONLYOFFICE and add `https://<ds_subdomain>.<your_domain>.com/`

5) Click "Save".

 

Profit!

 

Now.. why was this necessary??

Can confirm this worked for me!

[zage]

On 4/18/2021 at 7:10 PM, clusterbox said:

I can't explain why this fixed it (and honestly it concerns me that it did) but here's what I did:

 

1) Stop the OnlyOfficeDocumentServer container

2) Delete all the folders in `/appData/openofficeds` *EXCEPT* `/Data/certs`

3) Start the OnlyOfficeDocumentServer container and let it rebuild everything

4) Go back into Nextcloud --> Settings--> ONLYOFFICE and add `https://<ds_subdomain>.<your_domain>.com/`

5) Click "Save".

 

Profit!

 

Now.. why was this necessary??

 

 

Wow this worked for me too.

 

What is odd is I had some reverse proxy certs change when i was setting up a CName for my onlyofficeds container with my reverse proxy.  Pretty sure thats how they changed anyways.  I ended up blowing the whole only office document server container away and deleted all of its appdata as it seemed like the certs were being cached or stored somewhere else after they were first used.

 

Then I repulled the docker image and remade the container and applied the latest certs to only office from my proxy.

 

Then I ran into the health check errors in nextcloud.  I'm confused why not deleting the certs in my only office container after all of this solved it lol

 

Thanks