@nebulon I can't share the original document publicly, unfortunately, but the problem has disappeared after having raised the PHP Memory Limit in Nextcloud from 512 MB to 2 GB.

@jdaviescoates This is an idea I have quickly considered as well but one reason why I want to move this installation to Cloudron so desperately is that I want to have less work with it, not more

We will probably need to live with the fact that we will need to re-share all information again and simply do the move using one of the manual ways (e.g. user migration plugin). That will create chaos for a day or two, but at least then we will have a more stable installation.

@subven I agree with that, we are using Postmark, it's $10 per month only for a normal volume and really easy to set up. The deliverability has increased compared to other solutions like a mail package with even an established company in the market.

@nebulon It is happening also with similarly big files (as in many pages, not big file size). I don't think it's necessarily a Cloudron issue, but it would still be great to understand if there are ways how this could be resolved.

@humptydumpty I have read studies detailing this question a bit more. In total, DeepL is much better than Google Translate except for Russian (no experience with the new Asian languages yet). There are some commercial engines that work better for certain topics, but you would only want to look into this if you work in the translation industry. So, you can safely rely on it.

Hi, I was wondering if I can move a Nextcloud snap installation to Cloudron, perhaps similar to this tutorial?

https://github.com/nextcloud-snap/nextcloud-snap/wiki/Migrating-from-nextcloud-snap-to-Nextcloud-server

Ideally I would like to unify two VPS I have currently running on one dedicated server (price-wise about the same) under the roof of Cloudron. The Nextcloud installation is being used by multiple users though.

EDIT: I was wondering if I could use the new user migration app of Nextcloud 24 to achieve this? I would then install Nextcloud under Cloudron in the same way as before including all apps and then simply log into every single user account using "impersonate" and re-import this into the new instance. If this works, it would be an elegant way to avoid a lot of mistakes that could happen otherwise.

Happy to hear other suggestions as well.

I am using Vultr and Host Europe with Backblaze and Digital Ocean Spaces as Backups. So far, good experience with all of these providers. I'd give an edge to Vultr, though, because of the intuitive user interface and the multiple hosting options. I might exchange Backblaze for a cheaper option in the long run.

@subven I agree with that, we are using Postmark, it's $10 per month only for a normal volume and really easy to set up. The deliverability has increased compared to other solutions like a mail package with even an established company in the market.

@nebulon I can't share the original document publicly, unfortunately, but the problem has disappeared after having raised the PHP Memory Limit in Nextcloud from 512 MB to 2 GB.

@nebulon It is happening also with similarly big files (as in many pages, not big file size). I don't think it's necessarily a Cloudron issue, but it would still be great to understand if there are ways how this could be resolved.

@nebulon I just looked at the top command inside the Collabora app in Cloudron and never got the processor over 10% usage when scrolling through the document in different browsers. Same goes for the Nextcloud app, but since this is a rendering issue in Collabora, I wouldn't expect Nextcloud to react strangely anyway.

The file is 297KB with only a few small screenshots.

I can try re-setting up Collabora, but I didn't change anything from the standard configuration anyway, except giving it more resources in the Cloudron admin dashboard.

I have a dedicated server running Cloudron and Nextcloud and Collabora as separate applications on the same server.

When I am trying to open a long file with pictures, it takes endless time to open and I somehow suspect it's the editor's fault because of what I found in the logs during the file loading process:

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297249 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:122880:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297361 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:122880:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297370 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:0:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297376 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297382 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:6144:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297388 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:9216:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297393 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297399 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:0:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297404 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297409 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:6144:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297414 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:9216:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297419 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297425 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:0:132096:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297430 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:132096:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297436 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:6144:132096:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297441 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:9216:132096:3072:3072:0 was dropped because of time out (5618ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297446 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:132096:3072:3072:0 was dropped because of time out (5618ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

However, I don't know what to do with that. Can someone help?

@nebulon I am having the same issue. So, no quick solution in sight before the next release?

@chminc Indeed, I looked into this quite recently myself for our setup and came to very similar conclusions. It's not advised to use object storage. We will move to volume storage in case the space on the server won't be enough - it is not that much more expensive. But I have made really good experience with the Cloudron backup function, it restored everything completely error-free. And you can store the backup on object storage. Using encryption is not a problem at all.

@chminc Can't you use the Cloudron backup function to store a backup with an external provider, implement it in Cloudron on server B if you have to, and then do the same the other way round?
Backblaze or Digital Ocean Spaces worked well for us in similar cases.

@humptydumpty Thank you, that has actually worked!