Issue connecting to Docker on server

[gunnery]

Everything was working perfectly, until an upgrade of the software on the Mac:

I am now getting this error:

Error: All configured authentication methods failed at doNextAuth     (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:865:21) at tryNextAuth (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:1082:7) at tryNextAgentKey (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:1091:11) at /Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:1057:15 at /Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/agent.js:1042:15 at process.processTicksAndRejections (node:internal/process/task_queues:77:11)

Error: All configured authentication methods failed at doNextAuth (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:865:21) at tryNextAuth (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:1082:7) at tryNextAgentKey (/Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:1091:11) at /Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/client.js:1057:15 at /Applications/Wappler.app/Contents/Resources/app/node_modules/ssh2/lib/agent.js:1042:15 at process.processTicksAndRejections (node:internal/process/task_queues:77:11)

any help would be appreciated and its pretty urgent.

[Apple]

I'm assuming you've already restarted Wappler and your computer?

[guptast]

Hi Peter,

If you're using Resources Manager, check whether the SSH key is appearing under the SSH Agent for this project. If it is not appearing, then right click on the SSH Agent -> Add New Key -> select the existing key.

[George]

Seems like the SSH key used for deployment can not be found.

So make sure it is associated with your project and listed well in the Resource Manager and the SsH Agent there, see also:

Understanding SSH Keys: Enhancing Server Security and Access Control

Secure Shell (SSH) keys are a critical component of secure server management, access control, and various deployment processes, including Docker deployments. In this article, we’ll explore SSH keys in a broader context and then dive into their importance within Wappler, a platform that facilitates server management and Docker deployments using SSH keys. What are SSH Keys? SSH keys, or Secure Shell keys, are cryptographic credentials used to establish secure and encrypted connections between a…

[gunnery]

It seems that the update from apple caused a mismatch in the key. I've ended up redoing the keys and it's all working now, pretty frustrating when you need to make changes to a site.

[George]

Could you explain more in detail what was wrong with the key, where it was stored and how did you solved it, so it can be useful to others

[gunnery]

I checked the key on the server and compared it to the one on my Mac and they were different. This is what was causing the problem with not being able to connect to the server. (I can only assume the update on the Mac caused this as it has been working perfectly for several months)
I regenerated the key on my Mac, transferred it over to the server. As they were both the same now it works.

[Apple]

If a MacOS update caused an SSH key to mutate, there would be chaos on the Internet

Something else must've happened. I'm glad it's now solved though.

As for the key comparison, you could've made a mistake comparing the public key to the private key. The server only has the public key, but your computer uses a private key to login into remote computers (even though it might also have a public key file). The public key is always different from the private key, which might explain why you thought the key was different.

The most likely reason was perhaps something related with the SSH agent, which in my initial post I asked if you restarted your computer already.

[gunnery]

confused the hell out of me as well. Everything was working perfectly before the update.
Yes I did restart the machine several times, each time same issue.
The only thing that happened was the update, I have no other possible explanation.