Cloning a private Git repository through cPanel

Confirm Git Version Control and authorised shell access are available. Obtain the repository’s SSH clone URL and trusted host-key fingerprint. Plan a read-only deploy key when the hosting server only needs to pull code.

1. Generate a dedicated key for outbound repository access under the hosting account using the provider-supported procedure. Keep its private half protected on the server.
2. Add only the public key to the repository provider’s deploy-key or equivalent access settings, limited to the intended repository.
3. Configure the account’s SSH client to use that identity for the specific repository host. Preserve existing SSH configuration and avoid a wildcard identity rule that affects unrelated hosts.
4. Open Git Version Control > Create, enable cloning, enter the verified SSH URL and choose an empty permitted repository directory.
5. Verify any host-key prompt, create the clone and inspect the resulting branch and commit. Deploy through a separate reviewed process rather than assuming cloning publishes the site.

The repository should contain the intended project and be able to fetch authorised changes without an interactive password prompt. Confirm no credentials or .git data are publicly downloadable.

If cloning fails, test the outbound identity and repository permission separately from inbound hosting SSH access. Never embed a username-password pair in a clone URL or bypass an unexpected host-key change.

These are different authentication directions. Your laptop authenticates to hosting for inbound SSH, while the hosting server needs its own authorised identity to read the private repository.

• Deploying a cPanel Git repository with .cpanel.yml
• Resolving a cPanel Git pull blocked by local changes
• Adding an SSH public key to a cPanel account
• Rolling back a Git deployment while preserving uploaded data

• cPanel: Git Version Control
• cPanel: Guide To Git Set Up Access To Private Repositories