Cloudron Forum

So frustrated with this experience. The exact scenario I predicted (#2) above came true.

I should have paid more attention to my gut, and been more skeptical of the answer above. After all these hours, my host finally got me back into my server about 10 mins ago.

For anyone else needing help with this... the correct answer is... if your host uses an oddball SSH port like mine, update your [ /etc/ssh/sshd_config ] file before installing Cloudron ... or else you'll have a bad day like me - running wild goose chases trying to troubleshoot it and then finally begging/waiting for your host to bail you out when everything else fails.

Thank you for your efforts, @JLX89

All the cuss words.... how do I fix this now?

I ran the install exactly as described. Verbatim.
And now I'm locked out of my box.

This is not a $5 DO instance I can just respin a hundred times until it's right. Cloudron is feeling like more hassle than it's worth.

All afternoon to work around the simplest crap.

Unless I'm just missing something.... I think my only option is to have my host recommission this server from scratch.

Very not cool.

Yep. Exactly as I feared. I think the install was successful, but now I've lost the ability to SSH into my box because the ports are all wrong. And I can't edit them without SSH access.
Grrrrrrrrrrr........

And no, it's not that easy to start over and over again.

Ok. Sounds good. If anything explodes, I'm holding you accountable. Haha!

First time using Cloudron. I have a fresh new Ubuntu 22.04 server up and ready to go, but first I need to understand best practices regarding the following:

Root User vs. Sudo User - To secure my servers, I normally prevent root logins. Create a sudo user, and only login with SSH keys.

But I'm unclear how Cloudron works in this regard. The Installation instructions (https://docs.cloudron.io/installation/) are mute on this so far as I can tell.

1. Should I run the install commands as the root user or a sudo user?

The manual does mention some of this in the Security section (https://docs.cloudron.io/security/#securing-ssh-access) - but that seems to be post-install.

Also... in that Security section of the manual, it mentions SSH is handled on port 202. My host has SSH setup on 1022.

2. I've read those docs, but am still unsure what I'll need to do to rectify this... or maybe more specifically... what order in which I need to do which task. I can imagine a scenario in which I install Cloudron (via root logged in through port 1022) and then get locked out immediately after the install because it's expecting me to use port 202 instead.

Deep appreciation for any hints on these issues. Thanks.

@girish Excellent. I think what you described will be ok in my case. You said there are "many" side effects. Are those you mentioned the worst of it as far as you know?

@jdaviescoates Thanks. Overthinking is one of my unfortunate specialties. But the docs are very clear that the apps are installed on subdomains - https://docs.cloudron.io/installation/

But by looking closer at the demo, I can see how the location can be changed (app's location tab) - so I assume that's how it's done.

I've read the docs about how MySQL works in Cloudron.

• Each app has its own DB (addon) inside its own container, keeping things nicely isolated and secure

But let's say I have 2 very simple LAMP apps needing to access a single DB... is there any way to accomplish this with Cloudron?

Thanks.

Interested in testing Cloudron, but need clarification about how domain mapping works. I'm probably overthinking this, but by searching through the docs and forums, somehow I'm coming away with different understanding each time.

• I understand that Cloudron installs each app on it's own subdomain of the root domain (e.g. nextcloud.example.com)

• Aliases allow for any number of additional domains to access the original nextcloud.example.com directly (that is, without redirect - so all domain aliases work like standalone websites, and are essentially mirrors of the original)

So use case question... let's say I want to setup the following apps:
mastodon.example.com
nextcloud.example.com
nodebb.example.com
wordpress.example.com

And then I want to access them (via Aliases) like so:
bigtoot.io --> mastodon.example.com
bigcloud.io --> nextcloud.example.com
bigforum.io --> nodebb.example.com
bigsite.io --> wordpress.example.com

1. Is this in fact, how the Aliases work (e.g. root level domains not associated with the Cloudron domain)?
2. Is there then any way to prevent the original Cloudron installed locations from displaying content - to help prevent duplicate content, domain confusion, etc?

Thanks.

BTW... first time using NodeBB. Pretty slick interface. Thanks for maintaining such a quality space.