Error when Convert the id_rsa key to PPK format:
When I try to Convert the "id_rsa" key to PPK format:
I get the following error message.
Error moving temp file to /home/xxxxx/.ssh/putty/id_rsa.ppk: Invalid argument
It's not a folder permission and ownership problem.
I know I can use puttygen to convert. But I would like to found out what is causing this problem.
Any help is greatly appreciated.
-
what is the command you used for the conversion? can you provide exact command line?
Thank you for your reply. From cpanel account, under Security, SSH Access, Manage SSH Keys, Private Keys, View/Download There is a "Convert the "id_rsa" key to PPK format:". After keying in the passphrase, I get the following error. Error moving temp file to /home/xxxxxx/.ssh/putty/id_rsa.ppk: Invalid argument The ppk file could not be created.0 -
Thank you for your reply. I realize the problem only occurs when there is already a file with the same name in the output directory. Once I delete that file, the conversion will work. Conversion will work with any new file name. 0 -
Hello :) I am happy to see the issue is now resolved. Thank you for updating us with the outcome. 0 -
This issue is still not fixed after 3 months. Got same problem, after removing ppk file manually issue was solved. 0 -
This issue is still not fixed after 3 months. Got same problem, after removing ppk file manually issue was solved.
I've been unable to reproduce this issue with the Paper Lantern theme on cPanel version 56. Feel free to let us know if you encounter any additional issues. Thank you.0 -
Hello, I've gotten the same error when try to convert the key for second time. Here is know to reproduce it: 1. Create a new key with a passphrase 2. On private key clic view/download 3. Convert to putty format 4. Go to Manage root"s SSH Keys main page 5. Repeat steps 2 and 3 and you will get the error. Also If you delete the public and private keys, the putty file remains in the /root/.ssh/putty dir. 0 -
Hello, Internal case CPANEL-6111 is open to address this issue. There's currently no time frame on a resolution, but I will update this thread with more information as it becomes available. The temporary workaround remains to manually remove the the PPK file from the affected directory. Thank you. 0
Please sign in to leave a comment.
Comments
8 comments