The issue you’re experiencing is due to n8n not supporting the AES-128-CBC cipher used by your cPanel-generated SSH key. Based on the [community.n8n.io]( Unable to use SSH Credentials. Bug? ) discussion, this was a known limitation that has been addressed in newer versions.
Here are your options to resolve this:
• **Convert your existing key**: Use `ssh-keygen -p -m PEM -f your-key.pem` to convert your current key to a supported format, then use it in n8n
• **Generate a new OpenSSH format key**: If possible, create a new SSH key pair using `ssh-keygen -t rsa -b 4096` without specifying the old PEM format
• **Update n8n**: Ensure you’re running the latest version of n8n Cloud, as SSH key support has been improved significantly since the early issues reported in the community
If your cPanel provider only supports the problematic cipher format and you can’t convert the key successfully, you might need to contact your hosting provider to see if they can generate keys in a different format or consider using a different connection method for your database access.