@nebulon Thank you, I will investigate today and let you know.

@skippsterr Why do you want to edit the sshd_config file in the container? I think the original solution was to edit the sshd_config in the target ubuntu machine that you will connect to (not Cloudron server).

Also, see https://forum.cloudron.io/topic/3237/remote-sql-support-on-a-per-app-basis?_=1652377131316 on how one can connect with a SSH tunnel.

@mehdi said in Email notify on SSH login:

@xarp actually, Cloudron uses the inbound port 25. This does not prevent it from sending stuff.

I tried the postfix/mailutils method which uses a simple bashrc method in the user/root home, however when Cloudron rebooted, the mail service couldn't start unfortunately.

@girish Thanks for looking into this!

In the mean time I've also been able to get the connection to work by using the "old key" method.

@subtlecourage I'm not sure on which machine you get this message now, but have you checked for file permissions (chmod) on your RSA keys that could also be a factor.

Andy

@nebulon Ok! Thank's a lot, very simple but better to ask before doing something!

@BrutalBirdie I thought of marking as solved but did not find the button. Now I understand why, it's buried somewhere 😆

Thanks, now I understand

@JOduMonT Thanks! merged, should be part of our next deploy.

Hi there,

SSH login is usually handled by the the server provider. Cloudron does not have a UI to manage SSH login methods. If you are locked out of your server, usually your VPS provider has a way to reboot the server with a SSH key setup or a reset root password.
Otherwise if for some reason this does not help in your situation you can try to enable Cloudron remote support in the support view of your Cloudron dashboard and then send a mail to support@cloudron.io with your domain details. This may allow us to reset your SSH login details.

best,
Johannes

@girish Got it. Thank you. I was using the SFTP login to SSH. 🙂

@staypath Continuing my conversation with myself 🙂

Posting this here in case anyone else comes across this with the same question: I found that configuring fail2ban to use systemd was the trick:

[sshd] port = ssh #logpath = %(sshd_log)s #backend = %(sshd_backend)s backend = systemd enabled = true maxretry = 1 bantime = 14d

@dieter if you add an ssh key whilst buying the Hetzner server then they don't even create a root pw

@girish I second this

Admin credentials for mongo are really internal/implementation details. In general, do not make configuration changes to the mongodb instance because it may not work across all apps. This is the reason why all the databases are "locked" down and not exposed to users for easy access.

That warning said, you can do docker inspect mongodb | grep CLOUDRON_MONGODB_ROOT_PASSWORD to get the root password.