{"id":17861,"date":"2024-06-29T05:05:22","date_gmt":"2024-06-29T05:05:22","guid":{"rendered":"https:\/\/www.webhosting.uk.com\/kb\/?p=17861"},"modified":"2026-06-03T13:50:58","modified_gmt":"2026-06-03T13:50:58","slug":"how-to-resolve-cpanel-git-error-code-128-permission-denied-issue","status":"publish","type":"post","link":"https:\/\/www.webhosting.uk.com\/kb\/how-to-resolve-cpanel-git-error-code-128-permission-denied-issue\/","title":{"rendered":"How to resolve cPanel Git error code 128- \u2018Permission Denied\u2019 issue"},"content":{"rendered":"

Encountering Git Error Code 128: \u2018Permission Denied\u2019 when trying to push or pull repositories on a cPanel hosting environment is typically caused by permissions issues either in the Git repository or the user account trying to access it. Although this can be frustrating, several solutions can fix the error.<\/p>\n

Potential Causes –<\/strong><\/h2>\n

There are several common reasons for this error in cPanel:<\/p>\n

    \n
  1. Improper Repository URL: Your script may be using the wrong Git repository URL.<\/li>\n
  2. SSH Key Issues: The SSH key defined on your local environment may differ from the authorised key on the server.<\/li>\n
  3. Repository Ownership: The ownership and permissions on the Git repository may not be set properly in cPanel.<\/li>\n
  4. SELinux Issues: If SELinux is enabled and misconfigured, it could block Git operations due to incorrect security policies.<\/li>\n<\/ol>\n

    Troubleshooting Steps:<\/strong><\/h3>\n

    Here is a summary of how you can identify and fix Error 128 in cPanel:<\/p>\n

      \n
    1. Verify Repository URL<\/strong>: Ensure that the repository URL provided as the origin is correct. The URL should be in the format
      \nssh:\/\/username@domain.com\/path\/to\/repo.git.<\/em><\/li>\n
    2. Check SSH Key<\/strong>: Confirm that the SSH key set in your local environment matches the public key listed in the SSH Access section of the cPanel interface. You can also make the key importable via the terminal.<\/li>\n
    3. Check Repository Ownership<\/strong>: Log in to your server via SSH and navigate to the Git repository folder (e.g., \/home\/username\/repo.git<\/em>). Use ls -al to check the ownership. If you don’t own the folder, use chown to change ownership<\/a> to your cPanel username.<\/li>\n
    4. Set Repository Permissions<\/strong>: Use \u2018ls -al\u2019 to check the permissions on the Git repository folder. Ensure the folder and its contents have permissions set to 0755 or 0700. Use \u2018chmod\u2019 to set the desired permissions recursively.<\/li>\n
    5. Disable SELinux<\/strong>: SELinux can sometimes interfere with Git operations. Try temporarily disabling it to see if that resolves the issue:
      \nsudo setenforce 0
      \n<\/em>If disabling SELinux works, adjust the SELinux policies to allow the necessary Git operations properly.<\/li>\n
    6. Restart Git Server<\/strong>: Once appropriate changes or corrections have been made to ownership, permissions, or SELinux, restart the Git server process in cPanel to apply the changes.<\/li>\n
    7. Open Support Ticket<\/strong>: If the problem persists after trying all the above steps, open a support ticket with your hosting service provider for further assistance.<\/li>\n<\/ol>\n

      Additional Tips:<\/strong><\/h4>\n