As far as I understand those CVEs they are not relevant in that context. For the first, we don't use those affected configs and the second is for the ssh-agent.
Given that the Ubuntu team usually knows what they do and are working closely together with upstream projects, there seems no need here to go beyond their recommendations of versions they push out via security updates.
@Dreamcatch22 said in Disconnected: No supported authentication methods available (server sent: publickey):
But here was the error I was getting from the unresponsive wordpress app:
Inactive - Error getting IP of redis-3e2e5aad-1513-4b65-bb24-5eaafc998daa service
Services -> Redis -> Restart . Then, try the repair. Think it should work after that.
We haven't added a way to add custom persistent iptables rules . For SSH though, just move it port 202 and disable root auth and password auth. This usually cuts down all bots to 0.
@humptydumpty
Not only on home servers, also OVH and Vultr. Additional files will definitely be with local providers.
In this file "50-cloud-init.conf" as it actually is, I simply delete the line
Interesting. So, from @necrevistonnezr's like the hosts.allow/hosts.deny may not work in the future. "Note: this might not be an option on modern distributions, as support for tcpwrappers was removed from OpenSSH 6.7"
Yes, that was the problem. I was logged in under a second test user account that I had assigned admin role. Logged out and back in as my original cloudron owner account and all good on that front. Thanks.
@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).
