I am firm believer of moving ssl, a new private key should be generated
To answer your question, it is same for nodeworx or siteworx ssl, so goto nodeworx system ssl or siteworx hosting domain ssl and you can see the ssl
If none set, you can click create new and input your private key instead of generating a private key
If ssl already exists, click view private key and edit/delete and input your private key
You may not be aware but interworx can use let’s encrypt for ssl which is easy and to use, click generate all using let’s encrypt and select the list you want to cover with LE. Just be aware the dns for the records need to point at your server or it will fail
Thanks! My use-case actually is that I’m using a backup service, and they gave me their public SSH key to upload to my server so I don’t have to give them my password…
After much headache, I managed to save the public key in a file called “authorized_keys” after creating an “.ssh” folder in my user root. Then it worked!
I wish there was an easier way to do it via GUI . But at least it’s working now!
We do have an existing request for SSH Key management in the GUI. I’ll bump that request for additional visibility with the other devs. I can’t promise when (or if) that feature request might be taken up, but I will be sure it’s recorded. User interest does have a say in the features we choose to work on and roll out.