From time to time, the connection just goes away.

I click the 'Save' button on the Open Office connection page inside NextCloud and it works again. AFAIK, this is a common issue.

Yes, I have completed every reinstall, and reinstall of the app instance. It is not working.

Better solution:

Find the "Domains & Certs" menu in the dropdown Click on your domain and switch from Cloudflare to Manual (this can just be temporary) and then save Now try to uninstall your app again. Now you can probably try to reintegrate Cloudflare again via API

You may just have an expired Cloudflare token, which can happen. Check out expiry date for your token and try again.

BTW, you could also just use one instance of OnlyOffice and connect it to multiple Nextclouds

This took a bit but the latest package version has this fixed.

@osobo there is a OnlyOffice EE package that removes this limitaiton - https://www.cloudron.io/store/com.onlyoffice_ee.coudronapp.html . But of course, you have to get a license key from OnlyOffice. Maybe you can explain your Non-profit setup and they can accomdate.

@girish the support replied. I did not have the time to look into it, but wanted to share the feedback with you asap:

You are correct, but you can decrease the amount of converter processes by changing maxprocesscount parameter in default.json file: /etc/onlyoffice/documentserver/default.json "FileConverter": { "converter": { "maxprocesscount": 1, The default value is "1" but you can change it (to 0.5 or 0.25 for instance) to decrease the number of processes, since maxprocesscount is a multiplier, the number of converter processes will be equal to maxprocesscount * number of CPUs. Please, do not forget to restart Document Server's services after applying the changes: supervisorctl restart all

@kmz010101 did you manage to get this to work in the end?

In case any one else is looking through this thread later, the best path forward in our case was to start using DigitalOcean's free DNS service and then change the domain configuration in cloudron from manual to DigitalOcean.

Our cloudron apps are hosted under a subdomain of the top level domain so we needed to setup both the top level domain and the subdomain in digital ocean with name server records for the subdomain defined at the top level domain. We also needed to change our domain registrar's setup so that they would point to DigitalOcean's name servers as authoritative for the domain.

All of this worked and has resulted in us being able to have a cloudron instance that is not reachable from the public internet in any way but is still able to use Let's Encrypt certificates for everything via cloudron's automatic certificate management.

If you go down this path please be sure to get things setup, change the domains configuration, sync dns, renew certificates, and reboot the cloudron server and if things are configured properly you should be able to see that the certificates being used switch from your manually loaded certificate to the Let's Encrypt certificate.

Ultimately this results in https connections between apps, like nextcloud and onlyoffice, working by default without work around needed to bypass certificate verification.

Thanks: that did the trick.

Looks like adjusting inputLimits is what is suggested in https://forum.onlyoffice.com/t/the-file-size-exceeds-the-limitation-set-for-your-server/4888 as well. https://github.com/ONLYOFFICE/DocumentServer/issues/1674 and https://github.com/ONLYOFFICE/DocumentServer/issues/685 also suggests similar.

Just to double check, did you restart the app after making changes ?

You may have to reach out to the OnlyOffice support also to get information on how to debug this. We haven't gotten any test license from them to debug such app issues unfortunately.

Also may be worth checking the OnlyOffice Cloudron app logs.

Just found https://www.reddit.com/r/devops/comments/ooq32r/what_does_reaped_mean_in_supervisord_logs/ where a comment has good information.

@chetbaker It was quite a ride to find this information. The information in the docs was quite cryptic.

What I found is (maybe):

You have to build a .plugin file yourself from source. Apparently, you do this by " Archive the plugin files (it must contain config.json, index.html, and pluginCode.js). Change the file extension to .plugin. " . I think one has to read up how to create a plugin to test this out (I haven't).

You have to edit the line https://github.com/ONLYOFFICE/onlyoffice.github.io/blob/master/sdkjs-plugins/content/languagetool/scripts/langTool.js#L61 before creating the plugin file.

@scooke it's been like that for ages.

There was a tiny time window during which it was possible to edit OnlyOffice docs on mobile too (i.e. just after Nextcloud Hub something came out all singing and dancing about the OnlyOffice partnership), but then OnlyOffice swiftly shut that down.

I think that is one of the major reasons Nextcloud Hub now comes with Collabora instead.

For a while someone created a naughty fork that generated a fake license key, but I think perhaps that whack a mole game gave up in the end.

@DSime said in Failing to open documents after Update to Enterprise 7.2.1:

After a rollback to the previous version everything's fine again.

Maybe the issue is upstream? Have you checked with a clean browser without any plugins enabled? Hard to pin down if it's not reproducable but at least we have log output.

@scooke I am now having an issue with my Onlyoffice app

Not responding
Fails to update
Logs show this every few minutes

Oct 21 17:30:59 => Initialize database Oct 21 17:30:59 psql: error: connection to server at "postgresql" (fd00:c107:d509::80), port 5432 failed: Connection refused Oct 21 17:30:59 Is the server running on that host and accepting TCP/IP connections? Oct 21 17:30:59 connection to server at "postgresql" (172.18.0.34), port 5432 failed: Connection refused Oct 21 17:30:59 Is the server running on that host and accepting TCP/IP connections?

Any thoughts ?

EDIT : I checked Services and saw Redis for this app had stopped. Restarted w/o problem.
But postgresql is shown in orange status and is trying to restart constantly.
Those logs show :

Oct 21 17:38:05 Debug mode. Sleeping Oct 21 17:38:20 Detected existing installation Oct 21 17:38:20 Resetting root password Oct 21 17:39:21 Detected existing installation Oct 21 17:39:21 Resetting root password Oct 21 17:40:23 Detected existing installation Oct 21 17:40:23 Resetting root password

EDIT(2) : rebooted box, postgresql restarted, seems to have cleared the issue.