# Drone receives 404 from github posting build status

**URL:** <https://drone.discourse.group/t/drone-receives-404-from-github-posting-build-status/6174>\
**Category:** Drone Support\
**Created:** [January 4, 2019, 2:00pm UTC](https://drone.discourse.group/t/drone-receives-404-from-github-posting-build-status/6174 "2019-01-04T14:00:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![zapman449](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/zapman449/32/5988_2.png) [@zapman449](https://drone.discourse.group/u/zapman449)\
**Post date:** [January 4, 2019, 2:00pm UTC](https://drone.discourse.group/t/drone-receives-404-from-github-posting-build-status/6174/1 "2019-01-04T14:00:22Z")

</div>

Drone version 0.8

Most likely cause: engineer who setup drone just left the company, so some implicit permission issue.

Drone is watching 3 repos on our Github Enterprise system. 2 repos work great, 1 repo fails. Failure is drone posting the build status back to GHE.

Drone log message shows:

time=“2019-01-04T13:14:53Z” level=error msg=“error setting commit status for psc/tenants/15: POST [https://github.example.net/api/v3/repos/psc/tenants/statuses/ff5BLAHBLAHc8:](https://github.example.net/api/v3/repos/psc/tenants/statuses/ff5BLAHBLAHc8:) 404 Not Found []”

DRONE\_HOST is set to “DRONE\_HOST=http://drone.cicd.example.net”

All three repos have had "drone repo chown " run on them.

Thank you for any help;  
Jason

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [January 4, 2019, 3:26pm UTC](https://drone.discourse.group/t/drone-receives-404-from-github-posting-build-status/6174/2 "2019-01-04T15:26:38Z")

</div>

> Most likely cause: engineer who setup drone just left the company, so some implicit permission issue.

in this case you want the `drone repo chown <repo>` command, which will allow you to assume ownership of the repository to resolve any access problems.

---

<div class="post-metadata">

**Author:** ![zapman449](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/zapman449/32/5988_2.png) [@zapman449](https://drone.discourse.group/u/zapman449)\
**Post date:** [January 4, 2019, 3:40pm UTC](https://drone.discourse.group/t/drone-receives-404-from-github-posting-build-status/6174/3 "2019-01-04T15:40:46Z")

</div>

> All three repos have had "drone repo chown " run on them.

In digging, the issue was in github permissions. the drone service account didn’t have collaborator rights to the repo.