# Actions API returns 405 after update to 1.23.6

**URL:** <https://forum.gitea.com/t/actions-api-returns-405-after-update-to-1-23-6/11050>\
**Category:** Install/Maintain/Configure\
**Created:** [March 31, 2025, 7:07pm UTC](https://forum.gitea.com/t/actions-api-returns-405-after-update-to-1-23-6/11050 "2025-03-31T19:07:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![m90](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/m90/32/6783_2.png) [@m90](https://forum.gitea.com/u/m90)\
**Post date:** [March 31, 2025, 7:07pm UTC](https://forum.gitea.com/t/actions-api-returns-405-after-update-to-1-23-6/11050/1 "2025-03-31T19:07:42Z")

</div>

I updated a Gitea instance from 1.22.1 to 1.23.6 yesterday. Since the update my runner went missing. Debugging this I found out that it (FWIW, the runner is at version 0.2.11) fails calling the Gitea API which now returns 405:

```auto
Mar 31 21:01:47 host gitea_runner[655]: time="2025-03-31T19:01:47Z" level=info msg="Starting runner daemon"
Mar 31 21:01:47 host gitea_runner[655]: time="2025-03-31T19:01:47Z" level=error msg="fail to invoke Declare" error="unknown: 405 Method Not Allowed"
Mar 31 21:01:47 host gitea_runner[655]: Error: unknown: 405 Method Not Allowed

```

From the logs of the proxy in front of my Gitea, I can see that the path that is being requested (using GET) is: `/api/actions/runner.v1.RunnerService/Declare`

Trying to find out why this happens, I had a look at `git.mydomain.com/api/swagger` where I cannot find a `actions` resource at all.

Did I miss a required configuration change in my upgrade that is required to expose this portion of the API? Is this a version mismatch between my Gitea instance and the runner? Is this a bug?

---

<div class="post-metadata">

**Author:** ![m90](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/m90/32/6783_2.png) [@m90](https://forum.gitea.com/u/m90)\
**Post date:** [April 1, 2025, 7:17pm UTC](https://forum.gitea.com/t/actions-api-returns-405-after-update-to-1-23-6/11050/2 "2025-04-01T19:17:38Z")

</div>

I “fixed” this by deleting the `.runner` file and re-registering my runner. Not sure how it got into such a bad state though?