question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

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://<ipaddress-of-onlyoffice-documentserver>/ 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.

Any idea?

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

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:30 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
alexanderonlyofficecommented, Aug 9, 2018

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

1reaction
alexanderonlyofficecommented, May 2, 2018

Hello @stone212,

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error when trying to connect (Bad Request or timeout ... - GitHub
I've recently installed the document server on a fresh server running Ubuntu 16.04. I want to use the onlyoffice for my nextcloud instance...
Read more >
Onlyoffice connector giving "Error when trying to connect (Bad ...
I've installed onlyoffice on a separate server in a docker container. Onlyoffice is working fine, and is able to connect to my nextcloud...
Read more >
How to Fix the ERR_CONNECTION_TIMED_OUT Error - Kinsta
Simply put, it's an indication that the system is unavailable and the time given for one to connect has elapsed, and now the...
Read more >
How to Fix the 400 Bad Request Error - Lifewire
The 400 Bad Request error means that the request you sent to the website server to view the page was somehow incorrect.
Read more >
HTTP error 400: how to fix it? - Debug Bar
When we try to download a large document from a website, a 400 bad request error can occur. This situation is this time...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found