Rolling out 3.5.2 with following fixes: Fix encoding of links in plain text email Hide mail relay password Do not return API tokens in REST API

@nebulon Okay, it seems as if the update was applied over night. Thank you

@girish Great work guys! Any more details on everything you all implemented?

@girish @FTLAUDMAN Probably have your hands full with 3.4, but I'd love this as well. It allows us to expand the functionality of Cloudron to fill any holes in our deployment requirements, and eases the pressure on you guys to get apps out.

I will close this thread. https://forum.cloudron.io/topic/1560/what-s-coming-in-cloudron-3-3/22

@girish Thanks

Please note that existing Cloudrons will not use wildcard certs automatically. You have to go to domains -> edit the domain -> advanced -> Choose wildcard provider. New apps will then start using a wildcard cert automatically. Existing apps will start using wildcard certs once the existing ones expire. If you are impatient, you can just click on 'configure' of an existing app and click save to get a wildcard cert. Also, wildcard certs only work with programmable DNS. Finally, for new Cloudrons, wildcard is the default.

Cloudron 3.2 is now available for all. We pushed a mail container update as part of 3.2.2. This contains an important bug fix where the mail server keeps getting locked up.

@tomasz @saglagla Let's follow this up at https://forum.cloudron.io/topic/1453/how-to-backup-to-ovh-cloud-archive

@girish Sorry, I forgot mention you above!

How do I go back to the old unsupported unlimited version??? I have a ton of applications running already, and now they won't renew SSL certs. I am also unable to add more apps, to verify that the SSL is working or not. This is trashing existing users. I am this far from pulling the plug here. Freemium-sweetner-plan is what this is, not a real positive development for my use case.

We are slowly rolling out 2.4.

2.3 is out now - https://cloudron.io/blog/2018-06-04-cloudron-2.3.html

Surprise surprise - Gandi and GoDaddy DNS integrations are landing as part of 2.2 release [image: 1525721256999-gandi-resized.png]

We have another issue related to docker not upgrading because of unmet deps. Check journalctl -fa and if it shows something like below over and over again: The following packages have unmet dependencies: docker-ce : Depends: libseccomp2 (>= 2.3.0) but 2.2.3-3ubuntu3 is to be installed E: Unable to correct problems, you have held broken packages. To fix: apt update You might have to run the above command a couple of times since it might says it cannot get the lock. Once the update is done, it should update automatically.