Manual deployment, multiple SSH keys issue/problem

suto

Registered
Feb 17, 2021
2
0
1
Hollandia
cPanel Access Level
Root Administrator
following this guide from cpanel Guide to Git™ - Set Up Access to Private Repositories | cPanel & WHM Documentation to setup a private repo for the manual method worked once, trying to setup more custom SSH keys with different namings doesn't work cpanel only checks for rsa_id naming and uses that and if not it will grant a permission denied.
using ssh [email protected] -i .ssh/customkey does grant access but this is from within the terminal and not when i try to clone a new private repository which already has a newly named Custom SSH key authorized and added in their repository. instead it will grant me the 128 ERROR code Repository not found check for rights.
but when checking the connection i saw this SSH cpanel - Pastebin.com and concluded that cpanel Git Version Control either can't use multiple SSH key or i'm missing a vital step.

Goal:

Person gets a project, SSH key is made for their Git Repo and added in, Then using the Manual Method i should be able to update the Live version and clone their private repo.
 

suto

Registered
Feb 17, 2021
2
0
1
Hollandia
cPanel Access Level
Root Administrator
No the issue is, if more than 1 project would be active using github i'd need to hand out unique and different SSH keys.
So far i can only get the default (first) key to work.
If i create a new key following the steps but rename the key.
so in the terminal:
ssh-keygen -t rsa -C "[email protected]" followed by a no passphrase and when it asks where to store, because that's how i rename it by giving it a different name as it stores otherwise it will ask to override already existing rsa_id key and that's not making a new second key
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
4,509
567
273
cPanel Access Level
Root Administrator
Thanks for the additional details. I spoke with the developers about this and currently only one key is supported at this time. To see that behavior changed I would recommend submitting a feature request using the link in my signature below, as those all get reviewed by the developers, but I currently don't have a way to work around that behavior.