@George
Hi George
I have tried to connect an existing Hetzner cloud server following the tutorial, but unfortunately I am unable to successfully complete the operation.
I created the ssh key locally (with Wappler terminal) and then copied it to the Security section of the Hetzner server
@George
I tried to redo everything from the beginning, but even if I don’t enter a password when creating a new key, the password is still required. But it raises a doubt in /Users/.ssh/ there are these files authorized_keys id_rsa id_rsa.pub known_hosts If I delete them all, maybe I can eliminate the password problem? And above all, is it not that by deleting them I cause problems for the other projects on Hetzner that have no problems?
Adding to Hetzner’s console won’t magically make it appear on your existing VPS. This only applies to new instances going forward, where you have to chance to automatically add your SSH key to your VPS upon deployment
You need to use ssh-copy-id to upload your SSH key to an existing VPS
I understand the concept, but not how it can be done
However, the problem seems to be primarily the presence of the password which should be eliminated, as George said
@George
After Mela’s suggestion, now I can create the project machine without receiving errors and I can also without errors set porttainer and traefik, confirm IP address and regenerate Security Key
However, I cannot use the other functions of the START, STOP, RESTART, KILL panel
Evidently there is still something wrong
And indeed a test page is not displayed
Ok george
But unfortunately Wappler confirms the remote connection as a functioning, but then a simple index page is read correctly on local server but remotely not find the index file