Push Repo Issue

[Qhakim]

Description

Dear support team,
we overcame an issue during push my master branch from local machine to remote system. Just I would mention that our organisation use gitea system to develop our services. Below is the error message we received during pushing our repo.

Enumerating objects: 19, done.
Counting objects: 100% (19/19), done.
Delta compression using up to 12 threads
Compressing objects: 100% (15/15), done.
Writing objects: 100% (19/19), 112.34 KiB | 5.91 MiB/s, done.
Total 19 (delta 0), reused 0 (delta 0), pack-reused 0
error: RPC failed; HTTP 307 curl 22 The requested URL returned error: 307
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date

Gitea Version

1.22

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

linux

How are you running Gitea?

We are download gitea build from github assets and deploy it to linux VM

Database

SQLite

[lunny]

Can you get error logs from Gitea?

[af2005]

Had a similar (or the same?) issue.
I had a repository under an organisation, say foo/code.git and renamed the organisation to bar. So the repo was now available under bar/code.git.
My local repository still had the old https://example.com/foo/code.git url saved and I was getting the same

error: RPC failed; HTTP 307 curl 22 The requested URL returned error: 307

Don't know if that is intended for renamed organisations, but I understood that as long no other organisation claims the foo name, everything should be redirected.

[Zettat123]

Looks similar to #28460

[GiteaBot]

We close issues that need feedback from the author if there were no new comments for a month. 🍵