Weblate suddenly can not push due to missing permissions #2774

binharry commented 2026年06月17日 22:24:26 +02:00

Comment

We have around 250 outgoing commits in our weblate project. Weblate will creates 4-5 PR's with a few commits each and then stops. When pushing manually from the web interface I got some errors:

Could not push esc-it.org/instructions/auto-reboot: kex_exchange_identification: read: Connection reset by peer Connection reset by 217.197.84.140 port 22 fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. (128)
Could not push esc-it.org/recommendations/file-encryption: kex_exchange_identification: read: Connection reset by peer Connection reset by 217.197.84.140 port 22 fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. (128) 

Is this maybe due to some rate limiting? If so, do you have a hint on how high/low it is and when we could expect the open commits to be through the pipeline?

Thanks for your great work, we really appreciate it! ❤️

### Comment We have around 250 outgoing commits in our [weblate project](https://translate.codeberg.org/projects/esc-it-org). Weblate will creates 4-5 PR's with a few commits each and then stops. When pushing manually from the web interface I got some errors: ``` Could not push esc-it.org/instructions/auto-reboot: kex_exchange_identification: read: Connection reset by peer Connection reset by 217.197.84.140 port 22 fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. (128) Could not push esc-it.org/recommendations/file-encryption: kex_exchange_identification: read: Connection reset by peer Connection reset by 217.197.84.140 port 22 fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. (128) ``` Is this maybe due to some rate limiting? If so, do you have a hint on how high/low it is and when we could expect the open commits to be through the pipeline? Thanks for your great work, we really appreciate it! ❤️

mahlzahn commented 2026年06月19日 15:14:10 +02:00

Is it still an issue? It very much sounds like a temporary connection error. You may manually retry pushing from the https://translate.codeberg.org/projects/esc-it-org/#repository ...

Is it still an issue? It very much sounds like a temporary connection error. You may manually retry pushing from the https://translate.codeberg.org/projects/esc-it-org/#repository ...

binharry commented 2026年06月19日 16:02:59 +02:00

Yes, thats exactly where the errors also come from, I already tried that. Therefor I was wondering whether this is related to some rate limiting or so..

I am trying to merge the changes locally now, but I also run into rate limits when downloading the changes vie API I think, because it's really slow ...

Would this be different, if we sett all the components to a push branch directly in our repo? We acutally liked the "Gitea merge request" option, since it kept our branches a bit cleaner (cause they are a mess anyway 🙈)

Edit: And yes, for me it acually also seems like a connection issue, because when clicking "Push" it loads for sometimes 5minutes, but it returns with a green "all changes have been pushed" banner, so I don't know, what actually happens.

Yes, thats exactly where the errors also come from, I already tried that. Therefor I was wondering whether this is related to some rate limiting or so.. I am trying to merge the changes locally now, but I also run into rate limits when downloading the changes vie API I think, because it's really slow ... Would this be different, if we sett all the components to a push branch directly in our repo? We acutally liked the "Gitea merge request" option, since it kept our branches a bit cleaner (cause they are a mess anyway 🙈) Edit: And yes, for me it acually also seems like a connection issue, because when clicking "Push" it loads for sometimes 5minutes, but it returns with a green "all changes have been pushed" banner, so I don't know, what actually happens.

mahlzahn commented 2026年06月19日 16:20:44 +02:00

OK, needs to be a current connection issue. I just tried it with my project, and clicking on "Push" takes forever, too.

1. failed 404 (didn’t check the time)
2. almost a minute
3. 20 seconds
4. 15 seconds
5. 2.5 minutes

but it returns with a green "all changes have been pushed" banner, so I don't know, what actually happens.

If it was successful, a PR in the repo should have been created (and it doesn’t look like)

Maybe just try it a couple of more times until it is successful?

(Edit: I reported it to the admins if they can do something, e.g., increase the response timeout)

OK, needs to be a current connection issue. I just tried it with my project, and clicking on "Push" takes forever, too. 1. failed 404 (didn’t check the time) 2. almost a minute 3. 20 seconds 4. 15 seconds 5. 2.5 minutes > but it returns with a green "all changes have been pushed" banner, so I don't know, what actually happens. If it was successful, a PR in the repo should have been created (and it doesn’t look like) Maybe just try it a couple of more times until it is successful? (Edit: I reported it to the admins if they can do something, e.g., increase the response timeout)

bagel-very commented 2026年06月22日 21:20:46 +02:00

Same error here, intermittently, over last two days.

Same error here, intermittently, over last two days.