Co-founder of Cloudron.io
First off, I hope all you guys are staying safe in these tough times! Our team is split in Santa Clara and Berlin and we are doing well!
5.1 will be a quick release. There are a bunch of security related fixes but the main feature is the integration of turn addon/service into the platform. This will help us get the video conference apps in asap since it's the need of the hour.
For the coming weeks, we are going to focus on getting some new apps packaged. The list is:
If we should prioritize something else, please let us know! But the above should keep us occupied this month.
What we initially planned as Cloudron 4.5 is now Cloudron 5. We decided to bump the major version since it got a lot of changes to justify the bump.
New installations will already get Cloudron 5. Existing installations will get an update in a week or two. We roll out updates conservatively as always, if you want it immediately, please just send a mail to support@cloudron.io and we will make it available.
I am preparing the blog post which will have the screenshots for the features.
Changes:
Add user roles - owner, admin, user manager and user
Show backup disk usage in graphs
Mail server event log and mailbox usage information
Spam auto-learning - the spam solution is now per mailbox. The mail server will now periodically auto learn spam and ham from the mailbox with no user intervention.
CPU resource allocation - We have implemented CPU Shared
Whitelabel the footer/404
App specific passwords
Import backups UI - this lets you easily move apps across Cloudrons
Display timestamps in browser timezone in the UI
linode: add object storage backend
Enhancements in the built-in LDAP to better support SOGo (more on this in a separate post).
There's a lot of other bug fixes as well. You can read through the commits for that 
I have added a new category called Apps - https://forum.cloudron.io/category/9/apps . I am slowly adding all the apps we have into it as subcategories. It seems this might work better than tags (people are mistyping tags) and also provides a better direction/place for people to post.
Ideally, we keep the current Support category to Cloudron platform related issues. I am moving existing Apps related posts this new category.
Finally, we will start posting app updates in these new categories. Basically, https://cloudron.io/appstatus.html with a changelog. But since now apps are a separate category we can post it a bit more freely without being concerned about polluting the main support category.
Wanted to give some progress on the release here. Both @nebulon and I are taking a bit of break for Jitsi We will revisit once we finish some more enjoyable tasks.
Update base image - this is done! Apps are slowly getting updated one by one.
Add support for member-only mailing lists - done!
Default to ECC certs from Let's Encrypt - done!
Redis status - Under services, you can now tune redis instance of each app
App firewall will not make it this release since the changes are stacking up.
Some more updates.
Clicking the update button now will always give you an update, if it's available. No more required to ask us to whitelist an update.
Encrypted backups - there were security flaws with the current encryption. It's been fixed (more info when we do the actual release). thanks to @mehdi who has patiently worked with us through this.
App graphs! Currently, just RAM and Disk. CPU and Network will come later.
System graphs
Backup listing UI for the platform
New backup retention policy (this is same as keep daily/weekly/monthly in borg/restic).
Finally, there is a way import and export the backup configuration easily. You see this in the right of the backups. You get a config file that can then be put in another Cloudron instance for restore or import.
We hope to get this out next week. Just doing a lot testing now.
@jdaviescoates For pricing, as mentioned, we just offer discounted pricing on a case by case basis. Given we are a small company ourselves, we don't want Cloudron pricing to be a blocker for another business relying on us. We have a dozen or so re-sellers and they are generally IT admins, sysadmins who host for co ops, non-profits and schools.
As for Cloudron the company itself, we are profitable and pay ourselves a salary, and I can say we are not going away anytime soon. We are completely bootstrapped and haven't tried to ever raise money nor do we plan to. Future wise, one thing we really want to happen it is to grow to a size where we can start supporting upstream opensource apps - either by contributing with people or funding them.
Hi all,
We released Cloudron 4 now. The blog has more details about the release.
Changes:
i button in the app grid. Note that the username for each app is different!Email -> Outbound -> Select Disabled
As others pointed, Cloudron uses PBKDF2-HMAC-SHA1 with a per-user salt. This is totally different from just using SHA1.
As we are not cryptographers ourselves, the best approach is to not try to re-implement crypto ourselves and just follow NIST guidelines - NIST 800-63 Specs.
It recommends PBKDF2 and atleast 10k iterations. We also follow most of it's other password guidelines including following including 8 character minimum, support at least 64 characters maximum length, all ASCII characters (including space) should be supported, no password hints/expiry, non-SMS 2FA etc.
There is a good article summarizing the NIST guidelines at the Sophos website and also an article how to store passwords safely.
You can use this thread to track updates to the Metabase package.
Please open issues in a separate topic instead of replying here.
Hi all,
Metabase is now available in the app store. Most of the packaging work was done by @jimcavoli (thanks!)
Code: https://git.cloudron.io/cloudron/metabase-app
App store link: https://cloudron.io/store/com.metabase.cloudronapp.html
Docs: https://cloudron.io/documentation/apps/metabase/
I have created a separate category for this app now - https://forum.cloudron.io/category/86/metabase . Please ask questions there, I will lock this thread.
Metabase is now available as an unstable app. Thanks a lot @jimcavoli !
@d19dotca As long as the app backup is part of a full cloudron (box) backup, it will be retained since box backup and all it's containing apps are retained per the policy.
The above is the behavior in 5.2. Currently, only the box backups determine whether a backup is kept or not. I think the retention policies should be applied to app backups as well. This way, if you made an app backup, it won't get cleaned out immediately... (since no box backup is referencing it). I will get this fixed for next release.
@doodlemania2 @toto-s Did you change the location/domain of your matrix install by any chance? If so, I think I have a guess as to what is causing the problem. Do you have a file named /app/data/configs/signing.key ?
As @msbt said, joining smaller rooms (~1k participants) works. If I join larger rooms, the server runs out of memory and I get the CORS error in the UI.
17:05:07 - 2020-06-03 00:05:07,447 - synapse.http.matrixfederationclient - 165 - INFO - POST-109 - {PUT-O-160} [matrix.org] Completed: 200 OK
17:05:13 - /app/pkg/start.sh: line 80: 95 Killed
I bumped up the app's RAM to 2GB and I can connect to all rooms.
[1.3.0]