Just saying hi!

[luckym]

I couldn't find an introductions thread so will just use the off-topic forum

I re-discovered self-hosting as a service (is SHaaS a thing even ?) like Cloudron a couple of weeks ago after having first read about it a few years ago and then promptly forgotten about it again .

The re-discovery was quite exciting because I have both a personal server that I use to host my website, as well as umami and wg-easy (wireguard VPN), and I work for a small non-profit organization based in Berlin where money for software is always always always an issue and the potential of being able to reasonably self-host our software honestly fills my heart with joy.

So, looking forward to scope out the platform and engage with the community

p.s. actually one quick question, does the Cloudron install script mess with Ubuntu users? After installing from a new 'cloudron' sudo user, I can't seem to ssh into the server anymore with either root or the cloudron user ¯\_(ツ)_/¯.

[timconsidine]

Welcome. You’re going to love Cloudron !

[girish]

@luckym about the login issue, did you change the SSHd config or something ?

[nebulon]

@luckym welcome here! Also as a heads-up, Cloudron works best, if installed on a plain Ubuntu (20 or 22) server without extra packages installed or other things configured.

[luckym]

Thank you Tim! Yup, installation was already really painless and I love how active the forums are!

[luckym]

@girish @nebulon I created a fresh IONOS Ubuntu 22.04 VPS server, ssh'd into it via root, created a cloudron sudo user, then ssh'd into it via the cloudron user, and then ran the installation script. Did not change the default root password IONOS generates or anything else.

I don't really need to SSH into the server, I just noticed it and was wondering if this is expected behavior. Just using Terminal app on MacOS I'm getting Permission denied, please try again.

[jdaviescoates]

@luckym said in Just saying hi!:

created a cloudron sudo user

Why did you do this?

I think if you'd just run the install script without doing that first you likely wouldn't have had any issues.

Rarely, but occasionally, one does need to SSH into your Cloudron server, so if I were you I'd start again without doing that first not-in-the-instructions step

[BrutalBirdie]

Did you create a user named cloudron?
I also have an extra user on each system because I always lock down root completely for security reasons.

[luckym]

@jdaviescoates said in Just saying hi!:

Why did you do this?

I actually didn't really think about it too much, just a common practice to lock down the root user as @BrutalBirdie mentioned .

@BrutalBirdie

Yes, basically I ran adduser cloudron, followed by usermod -aG sudo cloudron, that was it. But yes, it's just on a small VPS server I set up to test things, I will probably move Cloudron over to a fresh install and bigger server in a couple of weeks so it doesn't really matter, just thought I'd mention it as I thought it was unexpected.

[scooke]

Interesting dilemma. I always have started with the fresh Ubuntu server as recommended, and I follow the usual DigitalOcean tuts ('cause I always forget) to tightening up SSH, disallowing root login, BUT I do create a second sudo user, and set up SSH to allow logins only by key, no passwords. Then, when I install Cloudron while logged in with the root user, it all goes well, root can't login, but my secondary sudo user still can. Maybe it was the name you choose? In reading your steps, I don't see that you did anything particular to the SSH service. So perhaps when Cloudron gets installed it does something which takes precedence over your non-steps, locking that user out. In my /home directory there is root, yellowtent and secondarysudouser. I suggest setting up your SSH service first, then install Cloudron.