git push (AGit): Internal Server Error (no message for end users) #2283

laumann commented 2026年01月02日 14:09:35 +01:00

Comment

I get this result when running the following command (to create a PR via AGit):

$ git push codeberg HEAD:refs/for/master -o topic="eclean-pkgdir-var"
Enumerating objects: 11, done.
Counting objects: 100% (11/11), done.
Delta compression using up to 4 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 1.23 KiB | 1.23 MiB/s, done.
Total 6 (delta 4), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Forgejo: Internal Server Error (no message for end users)
remote: error: proc-receive exited abnormally
To ssh://codeberg.org/gentoo/gentoolkit.git
 ! [remote rejected] HEAD -> refs/for/master (fail to run proc-receive hook)
error: failed to push some refs to 'ssh://codeberg.org/gentoo/gentoolkit.git'

It fails the same way every time. The remote is configured like this:

$ git remote -v
codeberg	ssh://git@codeberg.org/gentoo/gentoolkit.git (fetch)
codeberg	ssh://git@codeberg.org/gentoo/gentoolkit.git (push)
...

I also tried forking the repository (gentoo/gentoolkit) and open a PR the "traditional" way. I get this error message when going to the cli-provided URL to open a PR (https://codeberg.org/gentoo/gentoolkit/compare/main...laumann:eclean-pkgdir-var):

image

Additionally, I get the same 404 page when I try to create a PR in the forked repository!

I tried looking for similar issues, but didn't find anything that looked like this.

The listed Forgejo version: 13.0.0-dev-658-b96b5f65

### Comment I get this result when running the following command (to create a PR via AGit): ``` $ git push codeberg HEAD:refs/for/master -o topic="eclean-pkgdir-var" Enumerating objects: 11, done. Counting objects: 100% (11/11), done. Delta compression using up to 4 threads Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 1.23 KiB | 1.23 MiB/s, done. Total 6 (delta 4), reused 0 (delta 0), pack-reused 0 (from 0) remote: Forgejo: Internal Server Error (no message for end users) remote: error: proc-receive exited abnormally To ssh://codeberg.org/gentoo/gentoolkit.git ! [remote rejected] HEAD -> refs/for/master (fail to run proc-receive hook) error: failed to push some refs to 'ssh://codeberg.org/gentoo/gentoolkit.git' ``` It fails the same way every time. The remote is configured like this: ``` $ git remote -v codeberg ssh://git@codeberg.org/gentoo/gentoolkit.git (fetch) codeberg ssh://git@codeberg.org/gentoo/gentoolkit.git (push) ... ``` I also tried forking the repository (gentoo/gentoolkit) and open a PR the "traditional" way. I get this error message when going to the cli-provided URL to open a PR (https://codeberg.org/gentoo/gentoolkit/compare/main...laumann:eclean-pkgdir-var):  Additionally, I get the same 404 page when I try to create a PR in the forked repository! I tried looking for similar issues, but didn't find anything that looked like this. The listed Forgejo version: 13.0.0-dev-658-b96b5f65

acidbong commented 2026年01月02日 17:33:27 +01:00

it's git@HOST:USER/REPO, not git@HOST/USER/REPO

it's `git@HOST:USER/REPO`, not `git@HOST/USER/REPO`

laumann commented 2026年01月02日 17:43:40 +01:00

yes, when it's git@... I agree, but the clone URLs I see here on code use the ssh://git@... prefix and slashes (no colon).

EDIT: the previous comment did inspire me to try with https://codeberg.org/gentoo/gentoolkit and git@codeberg.org:gentoo/gentoolkit, both of which reproduce the same error.

yes, when it's `git@...` I agree, but the clone URLs I see here on code use the `ssh://git@...` prefix and slashes (no colon). EDIT: the previous comment did inspire me to try with `https://codeberg.org/gentoo/gentoolkit` and `git@codeberg.org:gentoo/gentoolkit`, both of which reproduce the same error.

oliverpool commented 2026年01月02日 20:20:23 +01:00

Forgejo attempts to open a PR targeting main instead of master:

https://codeberg.org/gentoo/gentoolkit/compare/master...laumann:eclean-pkgdir-var should work

Edit: Only for the "traditional PR flow". The AGit flow correctly targets master, so there is something else going wrong. Maybe a Codeberg admin can retrieve the log (please make a new attempt a record the date+time of the error)

Forgejo attempts to open a PR targeting `main` instead of `master`: https://codeberg.org/gentoo/gentoolkit/compare/master...laumann:eclean-pkgdir-var should work Edit: Only for the "traditional PR flow". The AGit flow correctly targets master, so there is something else going wrong. Maybe a Codeberg admin can retrieve the log (please make a new attempt a record the date+time of the error)

laumann commented 2026年01月02日 21:22:47 +01:00

@oliverpool wrote in #2283 (comment):

Forgejo attempts to open a PR targeting main instead of master:

You're right, the default branch was set to main but it should've been master. Not sure how I missed that, I've stared at that URL quite a bit 😅

https://codeberg.org/gentoo/gentoolkit/compare/master...laumann:eclean-pkgdir-var should work

It works!

Edit: Only for the "traditional PR flow". The AGit flow correctly targets master, so there is something else going wrong. Maybe a Codeberg admin can retrieve the log (please make a new attempt a record the date+time of the error)

Will do!

@oliverpool wrote in https://codeberg.org/Codeberg/Community/issues/2283#issuecomment-9491381: > Forgejo attempts to open a PR targeting `main` instead of `master`: You're right, the default branch was set to `main` but it should've been `master`. Not sure how I missed that, I've stared at that URL quite a bit 😅 > https://codeberg.org/gentoo/gentoolkit/compare/master...laumann:eclean-pkgdir-var should work It works! > Edit: Only for the "traditional PR flow". The AGit flow correctly targets master, so there is something else going wrong. Maybe a Codeberg admin can retrieve the log (please make a new attempt a record the date+time of the error) Will do!

laumann commented 2026年01月02日 21:24:54 +01:00

@oliverpool I think the AGit flow targets the default branch - we just got the default branch on gentoo/gentoolkit changed from main to master, and now the AGit push worked: gentoo/gentoolkit#1

@oliverpool I think the AGit flow targets the default branch - we just got the default branch on gentoo/gentoolkit changed from main to master, and now the AGit push worked: https://codeberg.org/gentoo/gentoolkit/pulls/1

laumann commented 2026年01月03日 11:18:24 +01:00

I think we can consider this issue resolved, but I think the error message could be improved somewhat. Aside from the URL showing a non-existing branch (main, not master). I didn't notice any warnings that the default branch was set to an invalid value (that's not to say there might have been some that I missed).

Could/Should I file a feature request somewhere? Would it be forgejo/forgejo, or maybe Codeberg-Infrastructure/forgejo?

I think we can consider this issue resolved, but I think the error message could be improved somewhat. Aside from the URL showing a non-existing branch (main, not master). I didn't notice any warnings that the default branch was set to an invalid value (that's not to say there might have been some that I missed). Could/Should I file a feature request somewhere? Would it be forgejo/forgejo, or maybe Codeberg-Infrastructure/forgejo?

oliverpool commented 2026年01月08日 22:18:52 +01:00

Great that this issue is resolved! Feel free to close this issue while we try to get to the root-cause.

---

There are a couple of safeguards in Forgejo to prevent deleting the default branch (or setting the default branch to a non-existing one), so I can't reproduce your bug at all.

Do you know how the gentoolkit repo was set up? Was it created here, migrated from somewhere else?

Once we can reproduce this bug, we can open an issue in forgejo/forgejo

Great that this issue is resolved! Feel free to close this issue while we try to get to the root-cause. --- There are a couple of safeguards in Forgejo to prevent deleting the default branch (or setting the default branch to a non-existing one), so I can't reproduce your bug at all. Do you know how the gentoolkit repo was set up? Was it created here, migrated from somewhere else? Once we can reproduce this bug, we can open an issue in [forgejo/forgejo](https://codeberg.org/forgejo/forgejo/issues/new/choose)

laumann commented 2026年01月09日 06:51:06 +01:00

Great, thanks! @thesamesam can you elaborate on how the gentoo/gentoolkit was created?

Now that the gentoolkit repo is fixed, I don't suppose we can set the default branch back to the non-existing main? Maybe we could reproduce with one of the other gentoo git repos if it's created in the same way?

Great, thanks! @thesamesam can you elaborate on how the gentoo/gentoolkit was created? Now that the gentoolkit repo is fixed, I don't suppose we can set the default branch back to the non-existing `main`? Maybe we could reproduce with one of the other gentoo git repos if it's created in the same way?