Codeberg/Community
54
325
Fork
You've already forked Community
12

Unable to fetch after recent outage #2128

Closed
opened 2025年09月10日 03:29:26 +02:00 by AndrewKvalheim · 2 comments

Comment

Since the recent outage I’ve been unable to fetch this repository:

$ git --version
git version 2.50.1
$ git clone --verbose 'https://codeberg.org/AndrewKvalheim/configuration.git'
Cloning into 'configuration'...
POST git-upload-pack (181 bytes)
POST git-upload-pack (208 bytes)
fatal: remote error: upload-pack: not our ref 0000000000000000000000000000000000000000

In the web interface, the default branch main is listed in the drop-down menu but 404s, and the Activity page returns a status 500.

### Comment Since the [recent outage](https://social.anoxinon.de/@Codeberg/115172476459202556) I’ve been unable to fetch [this repository](https://codeberg.org/AndrewKvalheim/configuration): ```console $ git --version git version 2.50.1 $ git clone --verbose 'https://codeberg.org/AndrewKvalheim/configuration.git' Cloning into 'configuration'... POST git-upload-pack (181 bytes) POST git-upload-pack (208 bytes) fatal: remote error: upload-pack: not our ref 0000000000000000000000000000000000000000 ``` In the web interface, the default branch `main` is listed in the drop-down menu [but 404s](https://codeberg.org/AndrewKvalheim/configuration/src/branch/main), and the Activity page [returns a status 500](https://codeberg.org/AndrewKvalheim/configuration/activity).

Hi, it seems that the reference to the main branch was broken, the reference did exist but did not point to any commit.

I've manually pointed it to d95254d88227e5949ade895d61f1e783fa3c14a and this should fix the issue, although I am not sure if this commit is where main should be pointing to, you might want to fix that yourself (by simply pushing to the main branch).

Hi, it seems that the reference to the main branch was broken, the reference did exist but did not point to any commit. I've manually pointed it to d95254d88227e5949ade895d61f1e783fa3c14a and this should fix the issue, although I am not sure if this commit is where `main` should be pointing to, you might want to fix that yourself (by simply pushing to the main branch).

Looks good, thank you!

Looks good, thank you!
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2128
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?