Error when trying to connect bad healthcheck status

Error when trying to connect bad healthcheck status

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.

Created at 1 year ago

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

Created at 2 years ago

I have this same issue.
If I change https://mydomain.tld/apps/documentserver_community to https://localhost/apps/documentserver_community I get «ONLYOFFICE cannot be reached. Please contact admin» instead.
I have nginx setup with reverse proxies and am wondering if I need a change to one of the location flags to reflect this new access.

Created at 2 years ago

Stuck at this point too, also behind a nginx reverse proxy.

Created at 2 years ago

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.

Created at 2 years ago

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.

Created at 2 years ago

The following fixed my issue on a NC 19.0.6 installation with OO 0.1.8 DSCE.

1. In the OO-settings page I simply removed ALL server-entries and REFRAINED from clicking the safe-button.
2. After that I switched to another settings page, the «Overview» in my case, and returned to the OO-settings without changing anything else.
3. 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:// /index.php/apps/documentserver_community/

Created at 1 year ago

@LordMort : Thanks! Your the hero of the day with that URL — did the trick on v.21 and current OO as of today.

Created at 1 year ago

The following fixed my issue on a NC 19.0.6 installation with OO 0.1.8 DSCE.

1. In the OO-settings page I simply removed ALL server-entries and REFRAINED from clicking the safe-button.
2. After that I switched to another settings page, the «Overview» in my case, and returned to the OO-settings without changing anything else.
3. 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.

Источник

Error when trying to connect (Bad healthcheck status) about documentserver_community HOT 8 OPEN

The following fixed my issue on a NC 19.0.6 installation with OO 0.1.8 DSCE.

1. In the OO-settings page I simply removed ALL server-entries and REFRAINED from clicking the safe-button.
2. After that I switched to another settings page, the «Overview» in my case, and returned to the OO-settings without changing anything else.
3. 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:// /index.php/apps/documentserver_community/

axcairns commented on January 16, 2023

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

SenchoPoro42 commented on January 16, 2023

I have this same issue.
If I change https://mydomain.tld/apps/documentserver_community to https://localhost/apps/documentserver_community I get «ONLYOFFICE cannot be reached. Please contact admin» instead.
I have nginx setup with reverse proxies and am wondering if I need a change to one of the location flags to reflect this new access.

Wdavery commented on January 16, 2023

Stuck at this point too, also behind a nginx reverse proxy.

klaask commented on January 16, 2023

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.

SenchoPoro42 commented on January 16, 2023

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.

TheSimu commented on January 16, 2023

@LordMort : Thanks! Your the hero of the day with that URL — did the trick on v.21 and current OO as of today.

MaoMaoCake commented on January 16, 2023

The following fixed my issue on a NC 19.0.6 installation with OO 0.1.8 DSCE.

1. In the OO-settings page I simply removed ALL server-entries and REFRAINED from clicking the safe-button.
2. After that I switched to another settings page, the «Overview» in my case, and returned to the OO-settings without changing anything else.
3. 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:// /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:// / fill in https:// /index.php/apps/documentserver_community/

• Specifically XLSX files are not being saved. HOT 1
• Cannot GET //printfile/<>
• Nextcloud Update Notification does not resepect Administration Overview Groups
• cant open odt HOT 1
• Remove the app as it is not maintained anyway HOT 4
• 24.0.5 no compatible for this Nextcloud version HOT 13
• Document opening problems on iPad
• How close the office after working on a file? HOT 4
• Mobile editing not working HOT 6
• PDF not working HOT 2
• Segfault while rebuilding fonts HOT 2
• No changes when you work together
• Update or install failed HOT 1
• File are not saved on file system but are only editable in onlyoffice HOT 17
• Error: OCADocumentServerDocumentDocumentConversionException: TypeError: this.Ia.HK is not a function HOT 1
• kernel: x2t[792851]: segfault at 78 ip sp error 4 in libgraphics.so HOT 3
• documentserver:flush
• [Bug]: DocumentConversionException: Segmentation fault (core dumped) HOT 1
• OCADocumentServerDocumentDocumentConversionException: TypeError: Cannot read property ‘om’ of undefined at mm.Rh
• Open pdf file blank or failed

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.

Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

TensorFlow

An Open Source Machine Learning Framework for Everyone

Django

The Web framework for perfectionists with deadlines.

Laravel

A PHP framework for web artisans

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

Some thing interesting about web. New door for the world.

server

A server is a program made to process requests and deliver data to clients.

Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

Visualization

Some thing interesting about visualization, use data art

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.

Microsoft

Open source projects and samples from Microsoft.

Источник

TrueNas-NextCloud problem. #187

I’m running TrueNas12 and NextCloud latest.

I installed Document Server Community.

OnlyOffice settings were automatically configured in this way:

When I click save I get the following error:

cURL error 7: Failed to connect to MYIP port 8282: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html))

In the «Office Online» app the following happens:

in URL and port I added this:
http://MYIP:8282/apps/documentserver_community/
And a huge green icon shows up apparently indicating everything is ok but after clicking save I get:
Could not establish connection to the Office Online server.

The text was updated successfully, but these errors were encountered:

I am using Freenas 11.3-U5 and nextcloud 19.0.4

I installed the Document Server Community app and the ONLYOFFICE app

OnlyOffice settings were automatically configured with: https:// /apps/documentserver_community/

I tried to open a .ods file and I got two messages:
Community document server is not supported for this instance, please setup and configure an external document server
only linux based servers are supported

I went back to ONLYOFFICE app settings, pressed save (just for checking), but nothing happens, I just see the progress gif rolling forever.

Tried to remove the the Document Server Community app and pressed save again on the ONLYOFFICE app settings it gives me Error when trying to connect (Bad healthcheck status) obviously.

So it looks like onlyoffice is properly recognizing and connecting to the community server, but it doesn’t work.

Источник

Error when trying to connect (Bad Request or timeout error) #172

I followed instructions from
http://helpcenter.onlyoffice.com/server/linux/document/linux-installation.aspx
and then I followed the instruction to activate the ssl encription and now the documentserver is listening correctly on thee 443 port with ssl encryption

Now I want to integrate nextcloud with onlyoffice. I’ve successfully installed in other machine nextcloud with ssl support I installed and activated the ONLYOFFICE app, into NEXTCLOUD, but when go to configure the app inserting https:// / I have an error that appear to the upper part of the browser

Error when trying to connect (Bad Request or timeout error)

and the integration doesn’t work.

DocumentServer version: 5.1.0-115
Operating System: Both UBUNTU SERVER 16.04 LTS

The text was updated successfully, but these errors were encountered:

Please send us the screenshot of ONLYOFFICE address settings in Nextcloud.

Try also to check the accessibility of the server with the document server from the machine where Nextcloud is installed. Use wget command: wget https://your_document_server_address and vice versa.

Both the servers have ssl activated with self-signed certificate and both the FQDN are registered in our internal dns server and point to internal (private) ip addresses.

From nextcloud to onlyoffice

From onlyoffice to nextcloud

Try to check the accessibility using wget command without no-check-certificate parameter. Most likely that servers will be inaccessible.

Please try to do the following:

Open /nextcloud/config/config.php and add a section:

Try to check the accessibility using wget command without no-check-certificate parameter. Most likely that servers will be inaccessible.

without no-check-certificate option the command wget returns an error because the certificate is self signed and not trusted.

Please try to do the following:
Open /nextcloud/config/config.php and add a section:
‘onlyoffice’ =>
array (
‘verify_peer_off’ => TRUE,
)

I tried and now my config.php is as follow

But now, when I go to save the onlyoffice nextcloud plugin, I have another error, the following
Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.)

@quelo1972, please try to use another trusted certificate, which will be verified, and remove this section from the config.

Now I’m only testing a solution for my organization and I don’t have any trusted certificate to use for it but above all I do not have any machines directly exposed on the internet, so I can not even get a free certificate from let’s encrypt. Is not there a way to make everything work to allow me to test the environment?

@quelo1972, there are two options you can do:

1. you can try to remove both certificates from NC and OO;
2. or you can try to add the certificate of your NC to the document server, in this case you need to add the section which disables certificate validation again. Please follow this link to find more information on how to a certificate authority.

1. you can try to remove both certificates from NC and OO;

at the beginning I tried this way but I was told that it was necessary to activate SSL to make the integration work.

1. or you can try to add the certificate of your NC to the document server, in this case you need to add the section which disables certificate validation again. Please follow this link to find more information on how to a certificate authority.

unfortunately I do not have much experience with SSL, could you guide me step by step please?

For NC I used Apache for OO I used nginx.

I copyed the self-signed certificate from NC /etc/ssl/certs/apache-selfsigned.crt to /usr/local/share/ca-certificate/ of the OO machine and I ran update-ca-certificates command line in the OO machine, restarted nginx service but I get the same error.
Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.)

Hi, i have the same Problem with my NC, OO installation.
Both servers are using trusted certificates (Let’s Encrypt wildcard).
«wget http(s)://oo-server.tld» and «wget http(s)://nc-server.tld» are working without a problem.
But there is still the error «Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.)»
If I set the Advanced server settings to http I’ll get a new error «CommandRequest on check error: Error occurred in the document service: ErrorCode = 1»

Hi, I faced with the same «error while downloading the document file to be converted» after updating OO from 5.0 to new 5.1 version.
16.04LTS, DEB from repo

I tried a couple of things and now it’s working.
It seems like there is a problem with newer versions of Ubuntu Server / Debian.
I switched from 17.10 to 16.04LTS and it works without a Problem.

P.s.: I’m not using Docker but the .deb version.

When I try to configure OnlyOffice in my Nextcloud. I have the same error : Error when trying to connect (Bad Request or timeout error)

So I try the solutions you talked about and indeed I have an issue of trusting when I try to wget between my NC server and my OO server.

Resolving onlyoffice.xxxxx.fr (onlyoffice.xxxxx.fr). 145.239.xx.xx
Connecting to onlyoffice.xxxxx.fr (onlyoffice.xxxxx..fr)|145.239.xx.xx|:443. connected.
ERROR: The certificate of ‘onlyoffice.xxxxx..fr’ is not trusted.
ERROR: The certificate of ‘onlyoffice.xxxxx..fr’ hasn’t got a known issuer.

How do I make my NC server trust my OO server ?

Thank a lot in advance for your help 🙂

PS : I use Letsencrypt certificate both side (OO and NC server)

You have to install the Letsencrypt CA certificate on both servers.
Copy the CA certificate to «/usr/share/ca-certificates» and run «update-ca-certificates» as root.

I’m sorry, I’m not sure to understand what really is Letsencrypt CA certificate or where I find it ??
Is it a public file or is it something I generate somewhere in my server.

In my OO server, I search in /etc/letsencrypt/live/onlyoffice.xxxxx.fr and I have 4 files
cert.pem chain.pem fullchain.pem privkey.pem
Should I put one my NC server ?

Finally, my case is resolved. It was self-signed certificate issue, exactly. Having installed OO 5.0.x, rooCA in /usr/share/ca-certificates/extra/ all works fine and curl https://nextcloud.local was clean. But after upgrade to OnlyOffice 5.1 I faced with “error while downloading the document file to be converted”.
When I looked at /var/log/onlyoffice/documentserver/converter/out.log I saw:

After a lot of experiments and tryings, I realised two necessary things for my case:

• Web-server certificate for nexcloud must contain full chain. My certificate was signed by SubCA.
• I had to run Node.js with additional key NODE_EXTRA_CA_CERTS=/etc/ssl/certs/mycorpRCA.pem . I suppose it must be added only to /etc/onlyoffice/documentserver/supervisor/onlyoffice-documentserver-converter.conf , but I added it to each *.conf in that directory, for sure. Please note, adding NODE_TLS_REJECT_UNAUTHORIZED=0 instead wasn’t helpful for me.
  I hope it would be helpful for someone.

Is there a solution for this? My configuration:

Ubuntu 16.04 on NextCloud Server
Ubuntu 16.04 on OnlyOffice server
Each server has a letsencrypt cert for its domain and
OnlyOffice installed with docker image
Docker 17.05
OnlyOffice URL shows green check mark and «Document Server is running»
NextCloud integration fails like this:

I enable OnlyOffice. Then I navigate to Admin —> ONLYOFFICE and I type the https://onlyoffice.myserver.com/ address and I hit «Save» and I get the error at the top of the page:

Error when trying to connect (Bad Request or timeout error)

Please try to check the accessibility of the Document Server from the machine with Nextcloud and vice versa. Use wget command: wget https://document_server_address and from the machine with Document Server: wget https://nextcloud_address

@alexanderonlyoffice Thank you for this test. The problem was with my nginx configuration. I was using the cert.pem file for the Cert and not the fullchain.pem file (letsencrypt).

I am also getting the error «CommandRequest on check error: Error occurred in the document service: Error while downloading the document file to be converted.».
Environment: NextCloud 13.0.5, OnlyOffice 9.6.591? — that is what the file says.
Both on two different Ubuntu 16.04.2 boxes
both on same network so firewall shouldn’t be issue.
onlyoffice app is version 1.3.0
Both have a wildcard comodo (namecheap) certificate which show on both as no errors.
Can get to both without problems (welcome screen with onlyoffice).
can wget both hosts from each other without problems (gets the index file).
In onlyoffice configuration I put in my url https://myserver.mydomain.com/ (using my values). When I click save, it gives me the error above. I have tried the advanced and without advanced with same result. I have tried some of the other values after the domain name that I have seen in forums without help. Any thoughts on what else to try?
Thanks
Alan

Hello @jaschrock, this error means that the Document Server cannot download the file for editing. It seems that your NC is not accessible for the Document Server.

Check if JWT is disabled in /etc/onlyoffice/documentserver/default.json in container with Document Server, if you do not use it in NC.

Try also to change the value of the following string in default.json from true to false: «rejectUnauthorized»: true

Thanks for your help. I got it working. This is what I needed to do:
Changed outbox to true in /etc/onlyoffice/documentserver/default.json
«token»: <
«enable»: <
«browser»: false,
«request»: <
«inbox»: false,
«outbox»:true
>

I also had to do the change to false
«rejectUnauthorized»: false

All seems fine now.
Again, thanks for the help!

Hi @jaschrock, we are glad that the issue has been resolved.

iam getting the below error while saving the document root.
Error when trying to connect (Bad healthcheck status)

Installed nextcloud in ubunutu 16.04 server and installed letsencrypt

@shabsshab
Please check the status of the ONYOFFICE Document Server services
supervisorctl status all
Does it also have SSL certificate?

I have done with ONLYOFFICE document server but i have another issue Problem with code integrity check.

Some files have not passed the integrity check. Further information on how to resolve this issue can be found in the documentation. (List of invalid files… / Rescan…

Technical information

The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results

• core
  • FILE_MISSING
    • .htaccess
  • INVALID_HASH
    • .user.ini
    • version.php

Raw output

Array
(
[core] => Array
(
[FILE_MISSING] => Array
(
[.htaccess] => Array
(
[expected] => 70183f641f39fc5f43065aeb15b86ac99e86b82310d5467e1c4d935df30acc6155c0905f84f59616885275c19ffacea59e354a87a5c97c94f50d50d4eff0370e
[current] =>
)

Источник