I have installed ONLYOFFICE 4.1.4 and Community Document Server 0.1.3 on Nextcloud 18.0.0 running in a Docker container (official image) on Ubuntu 19.10 x64.
When I go to the ONLYOFFICE settings the «Document Editing Service address» and «Server address for internal requests from the Document Editing Service» are prefilled with the address of my Nextcloud instance but the «Document Editing Service address for internal requests from the server» is empty.
If I hit save on the settings page I get an error toast with the message «Error when trying to connect (Bad healthcheck status)». There are no Onlyoffice options in either the create file menu or the file context menu.
Still not working with 0.1.5.
I noticed this in my Nextcloud logs (via settings > Logging) —
[PHP] Error: fclose(): supplied resource is not a valid stream resource at /var/www/html/custom_apps/documentserver_community/lib/Document/FontManager.php#66
GET /index.phpapps/update/documentserver_community
from 59.167.111.65 by allan at 2020-02-04T12:59:10+00:00
… and this in my docker logs for the nextcloud container —
[Tue Feb 04 20:59:38.166593 2020] [authz_core:error] [pid 125] [client 59.167.111.65:0] AH01630: client denied by server configuration: /var/www/html/config
Stuck at this point too, also behind a nginx reverse proxy.
Similar setup and healthcheck error on our side:
nginx reverse proxy & ssl termination (no docker)
To fix this error we added a different subdomain as «Document Editing Service address» and «Server address for internal requests from the Document Editing Service» and as trusted_domain in config.php.
I fixed my issue by letting removing the ONLYOFFICE application only, then installing it again. The correct server address was already filled in, but I just avoided pressing save on it and it then worked correctly and could connect.
The following fixed my issue on a NC 19.0.6 installation with OO 0.1.8 DSCE.
- In the OO-settings page I simply removed ALL server-entries and REFRAINED from clicking the safe-button.
- After that I switched to another settings page, the «Overview» in my case, and returned to the OO-settings without changing anything else.
- The OO-settings had been auto-filled with working entries, see below. Clicking on the safe-button at that time successfully enabled OO in my NC-installation.
The entry that had been auto-filled was:
https://<MY.DOMAIN.TLD>/index.php/apps/documentserver_community/
@LordMort : Thanks! Your the hero of the day with that URL — did the trick on v.21 and current OO as of today…
The following fixed my issue on a NC 19.0.6 installation with OO 0.1.8 DSCE.
- In the OO-settings page I simply removed ALL server-entries and REFRAINED from clicking the safe-button.
- After that I switched to another settings page, the «Overview» in my case, and returned to the OO-settings without changing anything else.
- The OO-settings had been auto-filled with working entries, see below. Clicking on the safe-button at that time successfully enabled OO in my NC-installation.
The entry that had been auto-filled was: https://<MY.DOMAIN.TLD>/index.php/apps/documentserver_community/
if this dosent work try adding /index.php/apps/documentserver_community/ to the end of the url
for example your server is at https://<MY.DOMAIN.TLD>/ fill in https://<MY.DOMAIN.TLD>/index.php/apps/documentserver_community/
The following fixed my issue on a NC 19.0.6 installation with OO 0.1.8 DSCE.
- In the OO-settings page I simply removed ALL server-entries and REFRAINED from clicking the safe-button.
- After that I switched to another settings page, the «Overview» in my case, and returned to the OO-settings without changing anything else.
- The OO-settings had been auto-filled with working entries, see below. Clicking on the safe-button at that time successfully enabled OO in my NC-installation.
The entry that had been auto-filled was: https://<MY.DOMAIN.TLD>/index.php/apps/documentserver_community/
In my case I had to click «Save», but simply changing the URL manually works the same. Just ensure that it includes the «index.php». Also, it’s important that both «Nextcloud Office» and «Collabora Online — Built-in CODE Server» are disabled. Otherwise, documents will be stalled at the loading screen as [at least one of] the two apps appear to interfere with ONLYOFFICE somehow. Once disabled, everything worked fine for me.
In my case, I had installed OnlyOffice from NextCloud’s app directory, but documentserver_community had not been downloaded automatically. I had to add it myself, then activate it, then re-enable the OnlyOffice connector, and now things run fine.
Loading
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
Nextcloud + OnlyOfficeDocumentServer + NGINX = Error when trying to connect (Bad healthcheck status)
I gave up on Nextcloud’s OnlyOffice integration to work properly so went down the rabbit hole of installing the DocumentServer docker and setting everything up.
I get the above error when trying to save the URL for the Document Editing Service Address (https://documentserver.mydomain.com)
I’m able to ping the documentserver.mydomain.com. I can type the documentserver.mydomain.com into FireFox and the Welcome page displays so I’m thinking it’s not a Cloudflare/NGINX issue otherwise I wouldn’t be able to reach documentserver.mydomain.com at all via URL or Pinging it.
I’m at a loss as to what to try next however. Any suggestions?
Loading