Error: Convert the id_rsa key to PPK format
puttygen: error loading ` .../.ssh/id_rsa': unrecognised cipher name
I see error converting keys to putty format when doing from cPanel. And error appears similar to above for all user accounts. Also tried to install putty on Centos8 (WHM v94.01). Any help would be highly appreciated.
-
Hey there! Putty isn't something that you would normally install on a CentOS machine, as that would already have a full SSH package included. Putty is a client that is specifically designed for Windows to connect to other systems that are using SSH. I'm not completely clear on the key issue you're experiencing - can you get me more details about the instructions you are trying to follow so I can test that? 0 -
Yes, absolutely putty is more relevant to systems having GUI but that was just an attempt to look whats missing that couldnt read the cipher of openssh format and convert it to ppk format. Ill share a screenshot 0 -
Thanks for that screenshot. This seems more like an issue of the file itself missing or being damaged on the system in some way. If you use File Manager or SSH directly on the machine, are you able to view that file normally? It should look something like this: -----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,C598FA4D580C139D 8X5F5OmRHTmu7oxxAkY3WYZISxBnBoiui+p2BBCnqzbrUgwd3sIfI9kOCrOgDJr5 voFUSQB1YFjxGdM9ugPf1xR5uHLxvAjDnbuKZ7WkIjazOvVJiEEZXE4H83reZCUm NJaorV2VQE3YGgWo4Pej3KKqv8Co12Yg8/NwilO37/3RrWgSaDbFBT61Y74sBDHA dFaYbKB+ds4I1oiWDiBNINwYF/GRGp7GhOGV12OjOubtguEuSto/4z2Kzi+ozlz8 7584rTHSQelg0fwJsDtlcUNu7EzzK1fmb7DymsT41FDR9lQTrV3VPDLn+37LS9yC sHgMqkNIo4/rWHnwls8LfptddmTyLRKsCOgtlMnV8K5yitfMZTlWJmmgfIz6vgRZ 96eEU5ZXkvdoK9CGFTFUvcSMdgrteLu26NBFdrFWLV1nwJzwqVDyWuIIpLD8K76i LTHtv1Nn3A0HaT6bGJJRR8C2iTg5uWyMahsHeE7ebf2mQpxjNRwr+h1Or7ZEiC7R mDhxUg4UfGpnXU06gy46aYMSWItR66+YV7m5hztCF12nZSYiunlfFwXM++XSrwJ4 HbO87zNwqMC5dAu+fzq0RkkAEI21eWLWTNniBOQm4izFn9P3418/GqemNtIufzgq GRGdDfPJ/Ub0nOjwtwzt1a1f57n0VZOSNtNlklOtM5w0UqXuMq02rzowW9KdWaTV NMpl0qMlK6ZAC3Zs0N01VdAxyUNj4je4sCCb/z1fxmzso26eoJnE5bOr3hYKFfle 6jAdIXEAzONUFL5EfwDtt98gX6uHAloLd1g01hrqFu9DO/BWkh/wfJWEdcnzqN+y gXsyX+qQy5yv6oBnUKizDhkA9TksxiRex/plva1JDC1g5+pO+x9/i3dtNWvK1iFE DB5izYHIL15Ic0ZO3RQ7sWjcOQQ/ZsJrrj63kI3F1W0CoaKboHxRipB+Bw/s5dd6 5a3OSij623MEUSgOrqOVoNajfp4rUlTjJ3O2A5wVrcKdm1tsXZGGdiEA75C7mrrl 6tYk7t1fcQBrhpMXM/l1iXs/LNPeJUyREP5pshLnpUu53ARzHZDp8B2aJOg9hKW+ 1vS7HdjZaTc2q0WaISriqIuFnaFJmXj+fi6njkUEBJ/os2FaNVG3WA8D4XzWhSPT dfQASHknhNOP/DkTej4BtxlhubmxIl6k4biyCN4tQOEJGULKQhp+vdx99fx67AAY I1pRcIuNUoq0d+GWYECF2k7ZbxSI5jML9kr/1q/FhgK9SPtRr3vxd4qC4Aht+0/j UF1K0udLxCgr9pR+RRg8X8nF9Zui2GFrzXBv9B0G470rjlacWDBUWOrzGLWaMQ8N lWzvjvGmJQV0lndTLWbPF+8r91BzVb79vNewWZJPIsXqcDGSMcqHFULXu2rP1NCE tbpquIYz6ENFH/OmDSPefLFxhZBPKgKl+QeW8F4TyQX4MbAF8t8uljQun1jRCLuv qARtFan7Ea0cUaWW234ZPM5MUfQwsZAqovu3fTfLpv+xJirotFvYAbmsyD6jahx7 CkSohoFdLBRKpgJS/PRGSF2dVRx1sGtVnfwwC8z07ANSfjAcd4kFFQ== -----END RSA PRIVATE KEY-----
If the file looks different than that, it would be best to create a new key in the interface and use that.0 -
Yes you have got this thing right. Actually everytime the key is generated, it looks like this And people have written in various threads that its probably because of the new openssh version that puttygen cannot convert. But couldnt found any solution for this. Hope the new cPanel version only has this issue. I didnt face this issue in cPanel v92. Only faced this in v94. Any solution would be really helpful. 0 -
Thanks for the additional details. I just tested the key generation on both CloudLinux 6 and CentOS 7 with version 94 and I did not get an error trying to convert that on my end. If you're still seeing this issue with a new key I would recommend submitting a ticket to our support team so we can check that directly on the server and see what the issue may be. If you do get that ticket submitted please post the number here so I can follow along and keep the community updated. 0 -
Ok, i'll recommend you to also try it on Centos 8 once so if possible and then Ill create a ticket. Thank you so much 0 -
Sure - let me test that now! 0 -
Glad I would be helping you guys anyway. Ill keep an eye over this case till this is resolved. Thank you so much. 0 -
You're very welcome! 0 -
Hello, can anyone post solution for mentioned issue? kind regards 0 -
Currently there isn't a solution. Our devs are working on this and I hope to be able to provide an update soon. 0 -
Update! This will be resolved in version 94.0.4, which is currently in the Edge tier, so you'll be seeing this fix applied to your systems as that version makes its way through the different tiers. 0
Please sign in to leave a comment.
Comments
13 comments