passwd

#39 Invalid or expired token in Weblate
Closed by jkucera. Opened by rffontenelle.

Closed
Reopen Issue

Fedora Weblate fails to push changes to this upstream repository with reason "Invalid or expired token".

Can you please take a look at it?

Here is the message from the alert page:

Could not push the repository.

Weblate could not push changes to the upstream repository.

 Could not create pull request 401: Invalid or expired token. Please visit https://pagure.io/settings#nav-api-tab to get or renew your API token., Expired token (-1)

Weblate will retry the operation once it is needed again, so the alert might disappear for the temporary issues.

I can see a weblatebot activity from 2025-02-08 so it looks like it works again.

I look where to add Pagure API key to Weblate but didn't find any suitable place except https://docs.weblate.org/en/weblate-5.10.4/admin/config.html#pagure-credentials, which I have not access to since this is a config file only Fedora instance of Weblate maintainers have access to. Since Weblate and Pagure are behind the same auth-wall I suppose the token is not necessary and Weblate is (or should be, ideally) granted r/w permissions to Pagure for eternity. So I am seeing this Invalid or expired token-like messages and Cannot access to the repository notification e-mails as just temporal glitches (well, with their rate of occurrence increasing last days) that only maintainers of Fedora infrastructure can fix.
Edited by jkucera

Metadata Update from @jkucera:
- Issue status updated to: Closed (was: Open)

Indeed it seems to be the API token from weblatebot account in Pagure. This happened again recently with freedesktop.org, same reason. Sorry for the noise.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.