Skip to content

How to fix error 60029: PermissionDenied? 

  • by
  • 4 min read

Command line tools like Git are a God send for coders and just about anyone else that needs to be able to share and work collaboratively on software projects. That said, Git in itself is an entire skill to learn with the amount of complexity it has. This also means bumping into occasional errors from time to time. 

In this article, we’re talking about the “error 60029: PermissionDenied” issue with Git, its causes and what you can do to fix the problem.

What causes error 60029?

The error is primarily caused by the server rejecting your connection request. This could happen because of a number of reasons, with some of the most common causes being:

  • Internet connectivity issues.
  • Incorrect server credentials or SSH key.
  • Git requires elevated privileges. 

Also read: GitHub vs Git vs GitLab vs Bitbucket

How to fix error 60029?

Here are seven fixes you can try out. 

Check your internet connection

You need a stable internet connection to be able to access and push/pull repositories from Git. Check to see if your device has an active internet connection. If you’re connected to a WiFi network, ensure you have enough signal strength and speed. If you’re on mobile data, check to make sure that you’ve got good network coverage and that it’s actually enabled. 

Restart your PC

This should be especially helpful if you’re on Windows. Rebooting your PC can fix all sorts of seemingly random issues with your programs and scripts as it often refreshes the entire operating system meaning corrupt caches and system memory are cleared. 

Check your server address

Check to make sure that you’re connecting to the right server. Even if the server address or URL is right, any network firewalls you might have, such as the ones on corporate networks can restrict your connection. Make sure you are connecting to the right domain with the right port number and that your network traffic is actually getting through to the server. 

Disable Firewall or VPN

If you have a third-party firewall or VPN on your system, it could very well be blocking your connection to the target servers resulting in corrupt or incomplete commits. Try disabling any third-party firewalls or any VPNs that you might be using to check if that fixes your issue.

Use the git user

All connections, including those for remote URLs, must be made as the git user. If you try and use your Github username instead, you’ll end up seeing errors, including the aforementioned error 60029. You can verify your connection by using this command. Make sure you change the remote URL to use the git user first.

ssh -T

Verify the public key

Check to make sure that the public key you’re using is tied to your account. Github requires users to use a public key that’s unique to each account to securely connect with their repositories. In case there’s a typo in your key or you’re using someone else’s public key, you’ll get connection errors. You can find your public SSH keys in your access settings on Github. 

Clean up your Git logs

Another thing you can do is clean up your Git logs. By doing so, you ensure that Git can see your commit history clearly and not miss anything important required to squash the required commit.

You can do this by using the -r option for reword. This uses the same commit but edits the commit message which makes it easier for Git to differentiate between similar older commits. 

Also read: How to create a Git repository? How to connect it to GitHub?

Yadullah Abidi

Yadullah Abidi

Yadullah is a Computer Science graduate who writes/edits/shoots/codes all things cybersecurity, gaming, and tech hardware. When he's not, he streams himself racing virtual cars. He's been writing and reporting on tech and cybersecurity with websites like Candid.Technology and MakeUseOf since 2018. You can contact him here: