certmonger

#266 Invalid or expired token in Weblate
Closed: fixed by rffontenelle. Opened by rffontenelle.

Closed: fixed
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 don't fully understand how Weblate does its pushes. I can replicate this behavior and am recommended to renew my personal token to allow a PR to be created. I don't actually have a token allowing access from weblate so this seems expected.

I'm not sure what to do with this next.

It's done. I was taken care by Weblate support. Sorry for the noise.

Metadata Update from @rffontenelle:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)
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.