Cloudron Forum

The first response considered some of the suggestions. I look forward to the new ui.

the other responses just seemed like you felt hurt. Not intended. Things can be improved. If you want to improve just denying problems won't help progress.

Cloudron is a clever idea, failing extensively in implementation.

CL does install things correctly. that is good.?

Cloudron itself has many UI problems and functional problems.

During setup the switch from Cloudron.IO (the "business" site) to Cloudron Server Portal is not clear. Each requires its own password though the login pages for both are indentical.

Suggestion: Simply make the login pages distinct with titles like: Cloudron Portal (the business site--pick anything you want) and Cloudron Server App Console.

The email setup is quite complex and unreliable. Required 2.5 hours to get everything working. Even though I had given Cloudron a correct Cloudflare API token with correct settings, Cloudron created all of the appropriate DNS records EXCEPT the needed MX record.

Cloudron email setup IS ESSENTIAL. Critical password changes can only be made via a change request email being sent. But, Catch-22: this can only be done with a correct setup. External SMTP did not work because the settings fields are incomplete or in accurate. Never did work. Don't blame Digital Ocean: I requested and obtained an exemption and 25, 587, etc were unblocked. I know this to be true because email sent by OnlyOffice worked through port 587.

Then I setup the internal server. Required PTR address and clearing blockage at xxxxHaus Zen. These are just requirements so not on Cloudron. But, the detection of the PTR record went on and off after being set. The real problem is that the outbound email is 1) different than NextCloud's outbound email, which is more reliable to set up; 2) it is essential for password changes so absolutely not optional. Instead of being documented (and the doc is voluminous and accurate)...

...Suggestion: build outgoing email setup into the workflow of the initial setup. Make it something that can be skipped. have a better standalone setup for outgoing email (from the Cloudron Server Management console, not from applications) for those who may choose to defer it.

Another substantial confusion is the App Store accessible from Cloudron.io is basically a NOOP: it is non functional. clicking install does nothing. it is marketing. OK to do marketing--but point people to the proper creation of the managed server and the Cloudron server console--that's the only place where the market place works to install apps.

Note: what I am referring to as Cloudron Server Management console is actually called Cloudron Dashboard: the latter is suitable, just needs to be distinguished from Cloudron.io--the business and marketing site.

Suggestion: while the complexity of various apps is on the developer of those apps, Cloudron purports to simplify those deployments. So, you have chosen to "wade in" to those complexities. Nextcloud requires sequential installs. You install the "backend" Nextcloud before you can install specific apps (not accessible from within Nextcloud itself) such as Collabora or OnlyOffice. Well, I'd call Nextcloud a "frontend" because it is the starting point and wrap around UI. I'd call Collabora a "backend". But, whatever--since you choose to support and simplify these deployments you really can't pass off the problems of the apps to the app vendors, like any commodity host does. You have chosen to step in as the "hero" to make it just work.

Suggestion: rather than the App Store just launching a setup, you should really launch a workflow of your own design to lead people through the essential steps. It's part of your value add.

Call these minor quibbles, but these are "speed bumps" that the new user encounters. By definition, almost everyone coming to Cloudron is a new user--or a new user after the bash scripts failed... So, it's important to create a great, not confusing and almost adequate, initial experience.

You really aren't there yet and it's a bit hard to recommend Cloudron. This is too bad because it works. While 2.5 hours of frustration is too much, it IS less than true self-hosting often turns out to be. The dashboard could also be more robust.