Cloud Providers SSH error

[raymantle]

Hi,

I am having an issue creating a server with Cloud Providers.

The server gets created but then I get an error “Failed to retrieve SSH keys for test: 255“

I have confirmed that the newly created SSH key is populated in DigitalOcean.

Eventually I get the following in the Resource Manager

Any suggestions on what I could be doing wrong?

Thanks,
Ray

[Cheese]

Hi Ray,
Have you added the key to the SSH Agent in the Resource Manager?

You could also try the following.

Log in to Digital Ocean.
Select the Droplet.
Click on Access.

Click Launch Droplet Console.

This will then launch the root terminal on the Droplet and should generate/register the SSH key to the Droplet. You may also need to reboot your desktop/laptop for the key to be recognised by Wappler on your local machine. Can be a bit funky that way sometimes.

[raymantle]

Hi Cheese,

OK, I tried to add to the SSH Agent as you suggested, but I get the following error;

So, there’s something wrong.

@George Any suggestions?

Thanks
Ray

[franse]

I've never used resource manager, but have you created the ssh key from there? Or are you using an existing one?
Wappler needs that ssh keys are stored in openssh format..

[franse]

Also the location should not be ~/.ssh instead of .wappler/.ssh?
Sorry if not, just trying to help

[George]

@raymantle

OK, I tried to add to the SSH Agent as you suggested, but I get the following error;

So, there’s something wrong.

Are you adding the right key? You do have to have the private key part to add it. So make sure you key is located somewhere accessible like in the user .ssh folder and then from the context menu of the SSH Agent - choose "Add New key"

[raymantle]

Hi @George

I am creating the key when creating the server via the resource Manager.

I have also tried from the SSH Agent

Then when I try to add it, I get the error.

Thanks,
Ray

[George]

On What OS are you on exactly @raymantle - seems your SSH agent command is not well supported, you might want to update to the latest Windows 11 if you are using windows.

Also if you already have an SSH key - then and used it to create servers or to your cloud provider - you should use that key - no need to generate a new one. Otherwise you will have to redo your servers as well.

[raymantle]

I am running Window 11 version 25H2 (OS Build 26200.7171).

Here is step by step on how I am creating the server.

First, no SSH on Digital Ocean.

Add Provider with new SSH Key selected.

If I try to connect without clicking the “Generate“ button, I get a validation issue as expected.

When I click “Generate“ I get key generated successfully.

Now when I click connect I get provider connection OK.

I now see the see the SSH key in Digital Ocean.

I also see the SSH key in the Resource Manager.

Now I create the server. It auto populates the SSH Key as expected/

I see the server being created.

Then I get waiting for server setup to complete and I and now see the IP of the server in the properties

This is then when I see the error Failed to retrieve SSH keys for the server.

I then see the error exclamation on the server with the tooltip message.

Am I missing something.

Thanks
Ray

[George]

I've update our ssh key management libraries to support more key types and also improved reliability, so adding keys to the SSH agent should now work smoothly.

This will be available in the next Wappler update to be released later today.

[raymantle]

Thanks George.

[Teodor]

This should be now fixed in Wappler 7.5.2

[raymantle]

Hi @Teodor

I’m still experiencing the exact same issues as before, as shown in the screenshots.
I completely uninstalled Wappler, including using Revo Uninstaller to remove all leftover files and registry entries and then performed a fresh install of 7.5.2.

Any other suggestions?

Ray

[George]

Make sure after you have added the digital ocean as provider, you restart Wappler and your key should be auto added to the SSH agent. You can create servers with it then.

[raymantle]

Hi George,

I have tried that, and the SSH keys are not being added to the SSH Agent. If I try to manually add it I get the error.

Regards
Ray

[raymantle]

OK, I have solved the issue, 1Password was set to be my SSH Agent.

Once I disabled that, the SSH Key was added automatically to the SSH Agent when I added DigitalOcean as the provider.

I’m not sure what the correct approach would have to ensure that the user wasn’t using another SSH Agent, but at least we got to the root of the problem.

Thanks
Ray