yep what your missing is for instance if you create an aws server from the aws default console
if you create one using the ubuntu or aws ami you get a configured server.
when following the connect to custom provider you put in the IP
try to connect and you get the message cannot connect
this is because you try from Wappler to login as root. which is prevented.
To reproduce
create a EC2 in AWS
be sure to use an existing ssh key whtch is also in your project as the connection method
then follow the instructions.
Workaround
create the ec2 with as above
login to the AWS console as ubuntu via connect
sudo -i to root
edit etc/ssh/sshd_config to allow rootuserlogin = yes and allow public key login
now edit /root/.ssh/authorized_keys to remove the first line until you get to your ssh key save
restart sshd
now you ca login and configure the server
however if you can login as say the allowed account ubuntu then you don’t need the workaround this could be accomplished by making he user a variable set with the ip address