Codeberg/Community
54
325
Fork
You've already forked Community
12

BYO Woodpecker seems to have token refresh problems? #2244

Open
opened 2025年12月05日 17:55:49 +01:00 by AstraLuma · 4 comments

Comment

So I stood up my own Woodpecker instance, hephestus, and it mostly works, but it starts failing mysteriously if I'm not constantly re-logging in.

I'm getting error messages in the logs like:

{"level":"error","error":"oauth2: \"unauthorized_client\" \"token was already used\"","time":"2025年12月05日T16:47:29Z","message":"refresh oauth token of user 'AstraLuma' failed"}
{"level":"error","error":"user does not exist [uid: 0, name: ]","repo":"teahouse/handtruck","user":"AstraLuma","time":"2025年12月05日T16:47:30Z","message":"could not get folder from forge: user does not exist [uid: 0, name: ]"}
{"level":"error","repo":"teahouse/handtruck","error":"configFetcher: fallback did not find config: user does not exist [uid: 0, name: ]\nuser does not exist [uid: 0, name: ]\nuser does not exist [uid: 0, name: ]","time":"2025年12月05日T16:47:31Z","message":"error while fetching config '' in 'refs/heads/trunk' with user: 'AstraLuma'"}

I can't tell if this is a bug in forgejo, a misconfiguration on my part, or a quirk of codeberg.

### Comment So I stood up my own Woodpecker instance, hephestus, and it mostly works, but it starts failing mysteriously if I'm not constantly re-logging in. I'm getting error messages in the logs like: ``` {"level":"error","error":"oauth2: \"unauthorized_client\" \"token was already used\"","time":"2025年12月05日T16:47:29Z","message":"refresh oauth token of user 'AstraLuma' failed"} ``` ``` {"level":"error","error":"user does not exist [uid: 0, name: ]","repo":"teahouse/handtruck","user":"AstraLuma","time":"2025年12月05日T16:47:30Z","message":"could not get folder from forge: user does not exist [uid: 0, name: ]"} ``` ``` {"level":"error","repo":"teahouse/handtruck","error":"configFetcher: fallback did not find config: user does not exist [uid: 0, name: ]\nuser does not exist [uid: 0, name: ]\nuser does not exist [uid: 0, name: ]","time":"2025年12月05日T16:47:31Z","message":"error while fetching config '' in 'refs/heads/trunk' with user: 'AstraLuma'"} ``` I can't tell if this is a bug in forgejo, a misconfiguration on my part, or a quirk of codeberg.

I think this is causing problems where Woodpecker can't pull config, and pipelines on that commit will always fail.

I think this is causing problems where Woodpecker can't pull config, and pipelines on that commit will always fail.

I think this is a Woodpecker bug.

@AstraLuma wrote in #2244 (comment):

{"level":"error","error":"oauth2: \"unauthorized_client\" \"token was already used\"","time":"2025年12月05日T16:47:29Z","message":"refresh oauth token of user 'AstraLuma' failed"}

Means the refresh token was used but for some reason the result was not stored.

I think this is a Woodpecker bug. @AstraLuma wrote in https://codeberg.org/Codeberg/Community/issues/2244#issue-2816022: > `{"level":"error","error":"oauth2: \"unauthorized_client\" \"token was already used\"","time":"2025年12月05日T16:47:29Z","message":"refresh oauth token of user 'AstraLuma' failed"}` Means the refresh token was used but for some reason the result was not stored.
Ok, forwarded as https://github.com/woodpecker-ci/woodpecker/issues/5839

Apparently woodpecker broke because of forgejo/forgejo#4633

Debate amongst yourselves who should change what, I guess

Apparently woodpecker broke because of https://codeberg.org/forgejo/forgejo/pulls/4633 Debate amongst yourselves who should change what, I guess
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2244
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?