We are happy to announce the release of Cloudron 0.130.0.
For those unaware, Cloudron is a platform that makes it easy to run apps on your server and keep them up-to-date.
It's a bit weird to announce unencrypted backups as a feature. Cloudron has supported only encrypted backups from the very first version. What we have seen is that many of our users do not set a backup password. But because Cloudron backups were always encrypted, we ended up in backups that were encrypted with an empty string. This has understandably led to a lot of confusion.
Starting this release, Cloudrons with a non-empty backup password are encrypted and have the extension
Encrypted backups can be extracted using the following command (assuming
secret is the password):
cat box_2017-04-28-201904-812_v0.130.0.tar.gz.enc | openssl aes-256-cbc -d -nosalt -pass "pass:secret" | tar zxvf -
Cloudrons with an empty password are not encrypted and have the extension
.tar.gz. They can be extract using the
cat box_2017-04-28-201904-812_v0.130.0.tar.gz | tar zxvf -
The External domain feature
allows you to set a custom domain for a single app. Enabling this feature involves opening the app's
configure dialog and choosing
External Domain in the location dropdown.
You can now set naked domains like
example.co.uk as an external domain for an app. The UI
will point out that you need to add
A record in the DNS for
example.com to point to the Cloudron.
Should the DNS credentials expire or become invalid, Cloudron now shows a warning.
In the situation that the DNS credentials expire and the webadmin (
my subdomain) certificate
could not be renewed, the Cloudron switches to using a self-signed certificate. To remedy the situation,
do the following:
mysubdomain manually to point to the Cloudron's public IP.
my.<domain>by accepting the self-signed certificate in the browser.
Domains & Certsmenu.
Cloudron will automatically get a new certificate once it has valid DNS credentials (just refresh the browser after a minute).