Can't connect to PROD after Windows reinstall

[Notum]

Good day Wappler,

After I re-install my PC to Windows 11 and importing one of my projects - I can’t no longer connect to my Hetzner server Production target.

What I did so far:

1. Delete all existing cloud providers
2. Added Hetzner with a new generated Hetzner API key
3. Imported server
4. Checked that Wappler’s SSH key is added in Hetzner

But when I click on System Check on production server error appears: root@95.**.**.***: Permission denied (publickey,password).

What would be a right step-by-step execution plan to fix that?

[Apple]

@Notum

• Checked that Wappler’s SSH key is added in Hetzner

Did you backup your previous SSH key? If you generate a new one it won’t magically be inserted into existing servers

[Hyperbytes]

I has similar issure with DO after a drive failure.
After trying lots of suggested fixes I backed up database with navicat, removed the site competely from host and then I was able to recreate it with a new key.
Then restored data from backup.

[Notum]

No I didn’t. Is there any instruction from Wappler team regarding Windows how to do it? Where these are located?

[George]

All your personal SSH keys are stored on your computer user profile .ssh folder

This is a system wide folder with ssh keys, so you should always make sure you backup very securely.

[Notum]

@George Don’t get me wrong but there should be a least some documentation regarding this. If you don’t backup those file your access to the server is lost. Maybe it worth implementing that all your project related files are saved within the project folder.

[George]

@Notum

Maybe it worth implementing that all your project related files are saved within the project folder.

But that is why we have an option to choose SSH key when creating a server, so you can choose a different one than your personal key, one that resides inside your project files.

But do note that if you share your project files you will be giving your private keys away as well.

[Notum]

This was a 3 years old Wappler project, when Remote Targets where configured outside of Resources Manager and I physically didn’t had such options.

[George]

I see. If it was based on the older docker machines, then those are even more difficult to backup.

For Resource Manager, using and generating SSH keys is easy. See:

Managing SSH Keys with Resource Manager

Intro You can manage your SSH Keys in the Resource Manager. You can create and manage keys per cloud provider or import existing keys from the provider. Creating SSH Keys You can find all your ssh keys per provider in the Resource Manager, under SSH Keys: [Screenshot_19] Creating a new key is really easy. Right click SSH Keys and click Add SSH Key: [Screenshot_20] Add a name for your key: [Screenshot_21] Select an encryption protocol: [Screenshot_22] And click Generate: [Screens…

I will see to enrich the creation confirmation message to alert you to backup the SSH key safely.

[George]

If you really lost your previous SSH key, you can try to add the new one, by using the server password that you can probably reset in Hetzner dashboard. The is a tool called ssh-copy-id for this. See:

https://www.ssh.com/academy/ssh/copy-id?hs_amp=true

[Alexander_Paladines]

In Hetzner if you have Cloud services you can enter to console:

If you don’t have root password, you can reset using Hetzner option, its under Rescue tab:

After that you have root access to server and can create new ssh key.

If server is ubuntu this can help you, if not in same tutorial you can choose different distribution of OS.

How to Set Up SSH Keys on Ubuntu 22.04 | DigitalOcean

[George]

@Alexander_Paladines

After that you have root access to server and can create new ssh key.

In Wappler’s Resource Nanager, when importing a server, you probably have created already an SSH key. So just use it

[Notum]

Thank you for advice, but I can’t reset root password because of this:

@George just for the reference this server was created by Wappler itself. There is 0 documentation regarding SSH keys, how to save them, how to use them and why there are not in project folder.

Should I explain that loosing access to Production target is a critical situation and maybe, just maybe, there is a little chance, that Wappler team will focus on some truly essential things like

• developing more transparent production target management
• informing their user about some feature deprecation
• providing documentation or instruction in case of OS change

[Apple]

May I suggest you open a ticket with Hetzner to ask assistance in performing a password reset? Note this procedure might result in downtime for the website, as most likely the VPS will need to be rebooted in rescue mode

[Notum]

@George is this behavior was improved in Wappler 6? So that Wappler would save per project SSH keys in Wapplers folder, not in some appdata location in Windows?

[George]

Yes now you can fully create and use SSH keys per project. Those are also saved in the project files.

See:

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…

[Notum]

Much appreciated for fast answer and your effort.