@tereensio is this issue resolved for you by now?

@tbroady do you have any update on this? Can we mark this as "solved"?

Since your provider does not support multiple PTR records per ip, I think this is only solvable in your case by using a email relay.

@fbartels Yes, the format of cloudron.json had changed between the CLI version. We didn't write the migration code since we thought it wasn't important.

@nebulon said in Large file not syncing in Nextcloud / cannot set max file size for syncing: So you are saying, one of those now disabled plugins/apps were causing the issue then? It seems so... I disabled https://apps.nextcloud.com/apps/bruteforcesettings https://apps.nextcloud.com/apps/files_antivirus https://apps.nextcloud.com/apps/ransomware_detection https://apps.nextcloud.com/apps/ransomware_protection Now everything works as intended. The error when setting the max upload file size still exists though.

Sorry for that, the renewed certs are now deployed.

Thanks @girish, that did the trick and lead straight into Backup Improvements: Restic as Backend.

There is an entry in the issue tracker for powerdns already at https://git.cloudron.io/cloudron/box/issues/117 Regarding the Linux distribution, we currently only support Ubuntu in versions 16.04 and 18.04 and due to testing effort, we don't currently plan on adding further distributions.

@gofaniyi SOGo is a "frontend" to email. The emails itself are stored in the backend which is part of Cloudron. Practically, what this means is that if you install some other email frontend like rainloop or roundcube, you will be able to see the same emails. To answer your question, all the data will be in /home/yellowtent/boxdata/mail/vmail. You will find directories organized by domain.com/username. They are all in maildir format.

Actually, the next time, if you run any linux distribution on your pc, then I would recommend to install imapsync there and do the one-time syncing, this avoids having to install additional packages alongside of Cloudron on that server.

Cloudron will "take over" the server and also manages the packages and services, which are installed. Generally it is not supported to install anything on the side. In this case Cloudron depends on mysql-server-5.7 which will probably uninstall mariadb through apt.

@nebulon Thank you very much. Yes, the server was done for a while but now back online :).

Hi, the application's data path can be found at /home/yellowtent/appsdata/<appId>/data/ and that is the only writeable path for apps (besides /tmp and /run of course). This is done for security as well as predictability for updates. Usually if you push data there through external means like SSH, you might have to reconfigure the app through the dashboard, in case the file permissions are not correct. Generally it is preferred that data changes are done via the app itself, which I guess is not quite applicable for your use-case though. For duplicator, from what I understand this migration script is mostly just creating a tarball/zipfile of the whole previous installation and then extracts it into a folder, which is served up by some LAMP environment. This is incompatible with the Cloudron WordPress package, for reasons mentioned above (mostly the read-only fashion) For this you probably have to fallback to the LAMP app itself. There it should work.

Thank you @girish for the refund! Much, much appreciated!

Amazing. Thank you!

From the next version, we don't require port 80 to be open since we support acme2 DNS based validation.

@ihtsham Yes, if you change the MX record of the client's domain to Cloudron's main domain i.e my.domain.com. When you have more clients, you can point all their MX domains to the same my.domain.com.

Well spotted @fbartels in fact 14.04 is not even supported by Cloudron at all, so it likely won't work anyways.

Getting a direct ssh connection into an app is not possible. All apps run in a separate container and are isolated from the main system. Depending on the app however, most apps have a read/write folder mounted from the host system into the container to store data. For example nextcloud is setup like this. The folder is located in /home/yellowtent/appsdata/<appid>/data/ and you could rsync data into this folder with the regular ssh connection to your server. You can easily see the appid if you open either the logs viewer of the app in question and take the appid from the browers url bar. Please note that this is merely a workaround so far and it depends on the app, if it correctly will pickup the data there.