Anyone having trouble accessing with their private Codeberg repos with existing access tokens (repo: read and write permissions)? Just starting failing for me some time in the last 24 hrs. Thanks!

Update: I think it's Indiekit gitea-store having trouble... I tested a new Codeberg access token with added user permissions and it works in curl (https://codeberg.org/api/swagger#/repository/repoCreateFile).

Related:

https://codeberg.org/forgejo/forgejo/pulls/11458

https://codeberg.org/forgejo/forgejo/pulls/11437

https://codeberg.org/forgejo/forgejo/pulls/11736

#codeberg #forgejo #askFedi #git #indiekit

Forgejo API

@paulrobertlloyd Hi Robert, sorry to bother you. If you're able, can you check if gitea-store is broken with the latest changes on Codeberg/Forgejo/Gitea? I'll write an issue later today on the project page for reference.
@paulrobertlloyd I narrowed it down to Render.com and Codeberg not playing nicely together. I think that's the cause of my Gitea failed fetch error. Maybe something Codeberg did related to the recent DDOS attacks... And Render apps (which use AWS I think) are therefore also blocked from accessing Codeberg.