DO server using resource manager can't connect

Wappler General Need Help
1

I’m still having terrible luck with the resource manager and setting up servers.

I have successfully setup a staging server, and a managed db.

Now trying to do the same thing and create (or import) a production server.

Screen Shot 2022-11-23 at 3.51.01 PM
Screen Shot 2022-11-23 at 3.51.01 PM978×1192 68.8 KB

I have done this half a dozen times, either creating the server in Wappler, or creating in the DO panel (where I can see the “pauka” ssh key is attached to the droplet, but I always end up without being able to connect.

I can perform the system check just fine:

Screen Shot 2022-11-23 at 3.54.19 PM
Screen Shot 2022-11-23 at 3.54.19 PM828×296 27.6 KB

Screen Shot 2022-11-23 at 3.54.50 PM
Screen Shot 2022-11-23 at 3.54.50 PM900×268 21.8 KB

But refreshing, or restarting Wappler, or restarting the computer, all leave me unable to connect, while the staging server works fine.

I’ve compared the fingerprint of the ssh key, to that on the Security panel of DO, and they match.

I’m at a loss. :man_shrugging:

2

@George any ideas here?

I can SSH through Wappler to both droplets.

But for 1 droplet, it errors when attempting to get the project info, and also fails when attempting to attach the cloud provider to a target:

Error: All configured authentication methods failed at doNextAuth (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:803:21) at tryNextAuth (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:993:7) at tryNextAgentKey (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:1002:11) at USERAUTH_FAILURE (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:366:20) at 51 (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/protocol/handlers.misc.js:337:16) at Protocol.onPayload (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/protocol/Protocol.js:2025:10) at AESGCMDecipherNative.decrypt (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/protocol/crypto.js:987:26) at Protocol.parsePacket [as _parse] (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/protocol/Protocol.js:1994:25) at Protocol.parse (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/protocol/Protocol.js:293:16) at Socket.<anonymous> (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:713:21) at Socket.emit (node:events:390:28) at addChunk (node:internal/streams/readable:315:12) at readableAddChunk (node:internal/streams/readable:289:9) at Socket.Readable.push (node:internal/streams/readable:228:10) at TCP.onStreamRead (node:internal/stream_base_commons:199:23)
3

Are your SSH keys added to the SSH Agent in Wappler Resource Manager?

Also do you SSH from Wappler Resource manager? From the server properties?

4

You mean like this?

Screen Shot 2022-11-24 at 10.04.27 AM
Screen Shot 2022-11-24 at 10.04.27 AM546×698 34.9 KB

Yes.

Screen Shot 2022-11-24 at 10.05.14 AM
Screen Shot 2022-11-24 at 10.05.14 AM1232×1270 128 KB

5

Ah it might be Ubuntu 22 and old rsa ssh key you are using.

For new servers we automatically enable the old rsa keys compatibility but for older servers you might have to do it manually. See:

1 Like
6

Okay I’ll try that. But why would the staging server work fine and the production not work? They are both Ubuntu 22. But I’m noticing the staging server that works has more IPv4 entries than production, but maybe that is because it has a deployment already??

Screen Shot 2022-11-24 at 10.38.53 AM
Screen Shot 2022-11-24 at 10.38.53 AM1170×1346 155 KB

7

Well check the ssh_config on the server to see if the setting is in there as outlined in the article above

1 Like
8

That did in @George. Thanks for the article link. Made the suggested change (to both servers so they match) and both are now working.

1 Like
9

I am exploring Resource Manager now and also encountered this issue.

I think it is worth some guidance for users.
Maybe add some note here? @George
E.g.:

Please note that Ubuntu 22 by default does not support the RSA ssh-key. One solution is to use ed25519 type for ssh key. You can generate such ssh key right from Resource Manager.
You can read more about this issue here.

Maybe even show this note only if selected ssh key is rsa and not ed25519.

image
image777×440 19.3 KB

10

I’ve opened one of my old project which needed to be updated and now I’m facing same problem - When I’m openedning Production tab console shows error: All configured authentication methods failed at doNextAuth
Remote Docker serveri s not available to from production tab, neither from Hetzner console - becuase it’s setup to login with Certificate.

@George please provide step-by-step instruction how to fix this problem.

11

Having the same issue... @Notum did you sort this out?

12

BACKUP FIRST! BACKUP FIRST! BACKUP FIRST! BACKUP FIRST!

@otavionestares

We had this issue with Digital Ocean Droplets in the past. The easiest way to overcome and resolve it is to delete the Server from the Resource Manager. Restart Wappler and then import the Server again. This should rectify the issue you are experiencing. You may also need to connect to it in the Digital Ocean Control Panel (using the root console) but not always necessary.

Like I said BACKUP FIRST!

1 Like
13

The issue means that no valid SSH key can be found to access the server.

So it all depends on how the server was created and where is the SSH key and if it was added to the SSH agent so it can be auto found.

See: