github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-22 14:34:54 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Error during Gitea 1.21.x upgrade Add RemoteAddress to mirrors failed No such remote 'origin' #12468

New Issue
Closed
opened 2025-11-02 10:10:45 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 10:10:45 -06:00
Owner
Copy Link

Originally created by @tuzhis on GitHub (Feb 11, 2024).

Description

I encountered an error while upgrading Gitea from version 1.20.x to 1.21.x. the upgrade process fails with an error message, whereas the previous version (1.20.x) was working fine.

routers/init.go:69:mustInitCtx() [F] code.gitea.io/gitea/routers/common.InitDBEngine(ctx) failed: migrate: migration[276]: Add RemoteAddress to mirrors failed: get remote origin's address of xxx/xxx-sales failed: exit status 2 - error: No such remote 'origin'
 - error: No such remote 'origin'

Gitea Version

1.21.5

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

docker

Database

MySQL/MariaDB

Originally created by @tuzhis on GitHub (Feb 11, 2024). ### Description I encountered an error while upgrading Gitea from version 1.20.x to 1.21.x. the upgrade process fails with an error message, whereas the previous version (1.20.x) was working fine. ``` routers/init.go:69:mustInitCtx() [F] code.gitea.io/gitea/routers/common.InitDBEngine(ctx) failed: migrate: migration[276]: Add RemoteAddress to mirrors failed: get remote origin's address of xxx/xxx-sales failed: exit status 2 - error: No such remote 'origin' - error: No such remote 'origin' ``` ### Gitea Version 1.21.5 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? docker ### Database MySQL/MariaDB
GiteaMirror added the type/bug label 2025-11-02 10:10:46 -06:00
GiteaMirror commented 2025-11-02 10:10:46 -06:00
Author
Owner
Copy Link

@go-compile commented on GitHub (Feb 16, 2024):

I'm experiencing the same issue, however I beleive I have found a solution. By navigating to your Gitea's repositories folder and manually adding a remote origin with the name "origin" this resolves the issue. I believe the issue is caused by mirrors without a remote address.

Steps to resolution

  1. Open a terminal on your server and using Docker logs find the repository which is throwing the error (e.g. "xxx/xxx-sales").
  2. Find and navigate to the location gitea/git/repositories (relative to your Gitea volume).
  3. Open the repository which is throwing an error and add a remote with the name origin git remote add origin https://github.com/xxx/xxx.
  4. Repeat from step 1 until no more errors show.
@go-compile commented on GitHub (Feb 16, 2024): I'm experiencing the same issue, however I beleive I have found a solution. By navigating to your Gitea's repositories folder and **manually adding a remote origin** with the name "origin" this resolves the issue. I believe the issue is **caused by mirrors without a remote address**. ### Steps to resolution 1. Open a terminal on your server and using Docker logs find the repository which is throwing the error (e.g. "xxx/xxx-sales"). 2. Find and navigate to the location `gitea/git/repositories` (relative to your Gitea volume). 3. Open the repository which is throwing an error and add a remote with the name origin `git remote add origin https://github.com/xxx/xxx`. 4. Repeat from step 1 until no more errors show.
GiteaMirror commented 2025-11-02 10:10:46 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Feb 16, 2024):

Yes, that's exactly what the error means.
The only weird thing is that there are mirrors without origin in the first place.
This should not be possible…

@delvh commented on GitHub (Feb 16, 2024): Yes, that's exactly what the error means. The only weird thing is that there are mirrors without `origin` in the first place. This should not be possible…
GiteaMirror commented 2025-11-02 10:10:47 -06:00
Author
Owner
Copy Link

@go-compile commented on GitHub (Feb 16, 2024):

Yes, that's exactly what the error means. The only weird thing is that there are mirrors without origin in the first place. This should not be possible…

In my case I had to fix a broken Gitea instance by manually placing repository files and adopting them, among other things; all of which were done many months ago. This is likely the cause.

@go-compile commented on GitHub (Feb 16, 2024): > Yes, that's exactly what the error means. The only weird thing is that there are mirrors without `origin` in the first place. This should not be possible… In my case I had to fix a broken Gitea instance by manually placing repository files and adopting them, among other things; all of which were done many months ago. This is likely the cause.
GiteaMirror commented 2025-11-02 10:10:47 -06:00
Author
Owner
Copy Link

@tuzhis commented on GitHub (Feb 16, 2024):

2. gitea/git/repositories

I'm experiencing the same issue, however I beleive I have found a solution. By navigating to your Gitea's repositories folder and manually adding a remote origin with the name "origin" this resolves the issue. I believe the issue is caused by mirrors without a remote address.

Steps to resolution

  1. Open a terminal on your server and using Docker logs find the repository which is throwing the error (e.g. "xxx/xxx-sales").
  2. Find and navigate to the location gitea/git/repositories (relative to your Gitea volume).
  3. Open the repository which is throwing an error and add a remote with the name origin git remote add origin https://github.com/xxx/xxx.
  4. Repeat from step 1 until no more errors show.

@go-compile @delvh thank you for the response, everything is working properly after adding all the remotes.
previously, I thought it was a bug because there was no "origin" in any of the repository under the gitea/git/repositories path.

@tuzhis commented on GitHub (Feb 16, 2024): > 2\. gitea/git/repositories > I'm experiencing the same issue, however I beleive I have found a solution. By navigating to your Gitea's repositories folder and **manually adding a remote origin** with the name "origin" this resolves the issue. I believe the issue is **caused by mirrors without a remote address**. > > ### Steps to resolution > 1. Open a terminal on your server and using Docker logs find the repository which is throwing the error (e.g. "xxx/xxx-sales"). > 2. Find and navigate to the location `gitea/git/repositories` (relative to your Gitea volume). > 3. Open the repository which is throwing an error and add a remote with the name origin `git remote add origin https://github.com/xxx/xxx`. > 4. Repeat from step 1 until no more errors show. @go-compile @delvh thank you for the response, everything is working properly after adding all the remotes. previously, I thought it was a bug because there was no "origin" in any of the repository under the `gitea/git/repositories` path.
GiteaMirror commented 2025-11-02 10:10:47 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 28, 2024):

Automatically locked because of our CONTRIBUTING guidelines

@github-actions[bot] commented on GitHub (Feb 28, 2024): Automatically locked because of our [CONTRIBUTING guidelines](https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#issue-locking)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12468
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?