Thank you, @gofaniyi and @girish! Now everything works.

I will mark this as solved since it was fixed with the update (3.4.3).

Great, thanks!

This is a UI bug in our current release (caused by an update to fontawesome..). You can fix it by doing this: Open the browser console (firefox, chrome, safari) in the settings page. Run this command angular.element(document.getElementsByClassName('content')).scope().cloudronNameChange.show() This will open a dialog that will let you set the name. Some other elements are missing as well in the profile page. For that, run this: angular.element(document.getElementsByClassName('content')).scope().displayNameChange.show() angular.element(document.getElementsByClassName('content')).scope().emailchange.show() angular.element(document.getElementsByClassName('content')).scope().passwordchange.show() We will push an update next week.

Yep, thanks. it worked.

Can you check if the backup format is correct (i.e tgz or rsync) when you restore from the backups? The logs are in journalctl -u box -a.

I believe @scooke already got this sorted out. The solution is to just start over with a fresh Ubuntu install and installing Cloudron. Another important thing to remember is to provide the correct version as part of the installation. It must be ./cloudron-setup --provider generic --version <version>. The version field is in the backup id.

I will mark this as solved, since it's unlikely we will start supporting another OS. Supporting two ubuntu versions is really hard as-is.

@thisiscowboy does this issue persist with the current mailtrain app package?

Just to conclude this thread. Mostly restarting the mail container will bring back the email server. As mentioned by @alexy this is done via docker restart mail

I will mark this thread as "solved", since it is quite old. If this issue is still there, please post a reply.

The wildcard dns would cover that just fine, so no need to take further action at the moment. Eventually during an update the box service will be anyways restarted. Just for completeness, systemctl restart box requires root capabilities, so it has to run either as root user or through sudo

Is this still an issue? If not, was there a solution?

@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.