# Cannot delete Projects \<Git Remote\>

**URL:** <https://discourse.nodered.org/t/cannot-delete-projects-git-remote/1222>\
**Category:** General\
**Created:** [1 July 2018 14:00 UTC](https://discourse.nodered.org/t/cannot-delete-projects-git-remote/1222 "2018-07-01T14:00:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![IoTPlay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/iotplay/32/40_2.png) [@IoTPlay](https://discourse.nodered.org/u/IoTPlay)\
**Post date:** [1 July 2018 14:00 UTC](https://discourse.nodered.org/t/cannot-delete-projects-git-remote/1222/1 "2018-07-01T14:00:00Z")

</div>

Hi, I have a project on BitBucket, which I clone down to RPi into the folders as required by the Projects feature, plus add the keys of the project in …/projects/.sshkeys, then start-up Node-RED, which works well.

However, in menu \> Projects \> Projects Settings \> Settings, Git Remotes that was in the code, has additional characters, (which is not in the original project?) - that causes the History / Commit History (“Unable to access remote repository”) not to work.

I then try to delete the Git Remote (bin button), under

menu \> Projects \> Projects Settings \> Settings \> Git Remotes,

but then get this error:

```auto
An unexpected error occurred:

Error: error: could not lock config file .git/config: Permission denied fatal: could not unset 'branch.master.remote'

code: unexpected_error

```

Any ideas where to look?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [1 July 2018 20:03 UTC](https://discourse.nodered.org/t/cannot-delete-projects-git-remote/1222/2 "2018-07-01T20:03:05Z")

</div>

> [@IoTPlay](#):
>
> Error: error: could not lock config file .git/config: Permission denied fata

Have a look at the file permissions under `~/.node-red/projects/<name-of-project>/.git`

Have you run as root previously? Can't think of any way the permissions would get messed up here.