OnlyOffice NextCloud issue after update

I have a particularly vexing situation where the OnlyOffice integration has suddenly stopped working with our one NextCloud 14 instance (I have a production version and a test version). I am still able to access OnlyOffice from our test NextCloud box, which is its own separate box (i.e.: NextCloud prod, NextCloud test, and OnlyOffice are each on their own boxes). We always do updates to the test version before updating production to ensure that these kinds of issues should not happen.

Since updating OnlyOffice, as well as the latest version of the OnlyOffice app in NextCloud; I am unable to access OnlyOffice from the production box, but it works perfectly fine from the test box, which was updated prior to pushing the updates to prod.

I have looked at several online troubleshooting pages; have added the suggested ‘onlyoffice’ configuration regarding ‘verify_peer_off’; I have ensured I can wget the URL for OnlyOffice from NextCloud (works fine) as well as wget the URL from NextCloud on OnlyOffice (works fine) - so both boxes can communicate with one another. I have tried disabling the app then uninstalling the app, clearing the database, reinstalling the app. I’ve written my own script to access the OnlyOffice server using file_get_contents() to see if there was a PHP config change which had no problem using file_get_contents to fetch the contents.

When I try and save the URL in the OnlyOffice settings from the production server on NextCloud, I get the following: GetConvertedUri on check error: Bad Request or timeout error

I also get issues on file_get_contents( failed to open stream: HTTP request failed! HTTP/1.1 504 Gateway Time-out at /var/www/html/apps/onlyoffice/lib/documentservice.php#381

The issue only started after updating OnlyOffice where there was an issue with OnlyOffice not seeing the existing Let’s Encrypt cert (nginx lost its proper config) but I re-ran the certbot command to add the existing certificate to the nginx configuration file. I don’t see how it would affect two different boxes connecting to the same utility though?

I’m really stuck here, and would appreciate some help if anyone has any. I’ve been trying to troubleshoot based on various articles, but I am still at a loss for words.



Did you configure a “secret” in the OnlyOffice app settings in Nextcloud?
Maybe you could post your OO configuration (from the NC admin section) and just censor the hostname/ domain parts, but with URL readable to check for HTTP(S) and URL format.

There were no changes in the web server config and OO is still running on same ports and so on? Couldn’t be a proxy issue, right?
Sorry for just throwing around questions. I have no real idea unfortunately.

Thanks for the response :smile: The irritating thing is, it is working from a different environment with no issues, and only seems to fail when I try and save it (when it tries to test for the connection to OO)

I have not configured a secret in OnlyOffice as it’s off a pretty non-standard URL and did not want to complicate things.

Correct, no changes to the web config for OO. I updated to the latest version of NextCloud now too as well. The error log on NextCloud shows this output:

I can see that the OO server is working fine (I copy-pasted the URL in and it shows the doc server is running)

When I try and reach ConvertService.ashx I get the following response:

And there doesn’t appear to be connectivity issues as I can wget the index page from either server.

I managed to resolve it by reinstalling OnlyOffice. From what I could tell, there was an issue within Node (possibly connecting to Rabbitmq). I could not quite understand why it would fail on the one box and not on the other, so decided to rebuild OnlyOffice after spending too many days investigating.

1 Like