github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

LFS gives 404 error, after migrating gitea service from server to another server #11498

New Issue
Open
opened 2025-11-02 09:39:23 -06:00 by GiteaMirror · 12 comments
GiteaMirror commented 2025-11-02 09:39:23 -06:00
Owner
Copy Link

Originally created by @skoenen on GitHub (Aug 21, 2023).

Description

Hi there,

recently we had to move our gitea service from one machine to a newer machine.
Process:

  1. Setup VM
  2. Setup Gitea in docker rootless variant
  3. Declare volumes (on nfs shares) for:
  • gitea_conf => /etc/gitea
  • gitea_data => /var/lib/gitea
  • gitea_ssh => /var/lib/gitea/home/.ssh
  • repositories => /var/lib/gitea/repositories
  • lfs => /var/lib/gitea/lfs
  1. Populate the gitea database (postgres) from postgres dump file
  2. check that the mounts are readable and writable by container git user:
  • docker-compose exec -u git gitea touch .../test.txt

Normal repositories working fine so far. But lfs files pose a problem:

CMD: git lfs fetch --all
Error: [...] Not Found: [404] Not Found
gitea log: No errors mentioned, authentication works router: completed POST

After that i tried the "Associate accessible 1 OIDs" in the repo settings > lfs.

That resulted in 500 Internal Server Error
gitea log:

2023/08/21 11:43:08 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for 192.168.176.5:45578, 200 OK in 1081356.3ms @ events/events.go:18(events.Events)
2023/08/21 11:43:08 ...dules/git/command.go:281:Run() [D] git.Command.RunDir(/var/lib/gitea/repositories/stefan.koenen/lfs-test.git): /usr/bin/git -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= rev-parse
2023/08/21 11:43:08 ...dules/git/command.go:281:Run() [D] git.Command.RunDir(/var/lib/gitea/repositories/stefan.koenen/lfs-test.git): /usr/bin/git -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= cat-file --batch
2023/08/21 11:43:08 ...dules/git/command.go:281:Run() [D] git.Command.RunDir(/var/lib/gitea/repositories/stefan.koenen/lfs-test.git): /usr/bin/git -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= cat-file --batch-check
2023/08/21 11:43:08 ...dules/git/command.go:281:Run() [D] git.Command.RunDir(/var/lib/gitea/repositories/stefan.koenen/lfs-test.git): /usr/bin/git -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= for-each-ref "--format=%(objectname) %(refname)" refs/heads/ --sort=-committerdate
2023/08/21 11:43:08 ...ters/web/repo/lfs.go:551:LFSAutoAssociate() [E] LFSAutoAssociate: unable collect all LFS objects from database, expected 1, actually 0
2023/08/21 11:43:08 .../context_response.go:74:HTML() [D] Template: status/500
2023/08/21 11:43:08 ...eb/routing/logger.go:102:func1() [I] router: completed POST /stefan.koenen/lfs-test/settings/lfs/pointers/associate for 192.168.176.5:35444, 500 Internal Server Error in 74.5ms @ repo/lfs.go:527(repo.LFSAutoAssociate)

Seems to be related to #17207

I check manually for the files and they are accessible by git user and also the folder is writable. So it seems there is something in the database missing.

gitea data:

Name Value
Site Title GIT of AIS-Lab
Gitea Version 1.20.0 built with GNU Make 4.4.1, go1.20.6 : bindata, timetzdata, sqlite, sqlite_unlock_notify
Configuration File Path /etc/gitea/app.ini
Gitea Base URL https://git.ais-lab.eu/
Server Domain git.ais-lab.eu
Local Mode Disable Router Log
Run As Username git
Run Mode Prod
Git Version 2.40.1, Wire Protocol Version 2 Enabled
Repository Root Path /var/lib/gitea/repositories
Static File Root Path /var/lib/gitea
Custom File Root Path /var/lib/gitea/custom
Log Path /var/lib/gitea/log
Script Type bash
Reverse Authentication User X-WEBAUTH-USER
SSH Configuration
Enabled true
Use Built-In Server true
SSH Server Domain git.ais-lab.eu
Port 22
Listen Port 22
LFS Configuration
Enabled true
LFS Content Path {"Type":"local","Path":"/var/lib/gitea/lfs","TemporaryPath":"/var/lib/gitea/lfs/tmp","MinioConfig":{"UseSSL":false,"InsecureSkipVerify":false,"ServeDirect":false}}
LFS HTTP Auth Expiry 24h0m0s

Gitea Version

1.20.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.40.1, Wire Protocol Version 2 Enabled

Operating System

Fedora Server 37

How are you running Gitea?

Docker Image rootless version
With several NFS-Shares for large data

Database

PostgreSQL

Originally created by @skoenen on GitHub (Aug 21, 2023). ### Description Hi there, recently we had to move our gitea service from one machine to a newer machine. Process: 1. Setup VM 2. Setup Gitea in docker rootless variant 3. Declare volumes (on nfs shares) for: - gitea_conf => `/etc/gitea` - gitea_data => `/var/lib/gitea` - gitea_ssh => `/var/lib/gitea/home/.ssh` - repositories => `/var/lib/gitea/repositories` - lfs => `/var/lib/gitea/lfs` 4. Populate the gitea database (postgres) from postgres dump file 5. check that the mounts are readable and writable by container git user: - `docker-compose exec -u git gitea touch .../test.txt` Normal repositories working fine so far. But lfs files pose a problem: CMD: `git lfs fetch --all` Error: `[...] Not Found: [404] Not Found` gitea log: No errors mentioned, authentication works router: completed POST After that i tried the "Associate accessible 1 OIDs" in the repo settings > lfs. > That resulted in 500 Internal Server Error gitea log: ``` 2023/08/21 11:43:08 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for 192.168.176.5:45578, 200 OK in 1081356.3ms @ events/events.go:18(events.Events) 2023/08/21 11:43:08 ...dules/git/command.go:281:Run() [D] git.Command.RunDir(/var/lib/gitea/repositories/stefan.koenen/lfs-test.git): /usr/bin/git -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= rev-parse 2023/08/21 11:43:08 ...dules/git/command.go:281:Run() [D] git.Command.RunDir(/var/lib/gitea/repositories/stefan.koenen/lfs-test.git): /usr/bin/git -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= cat-file --batch 2023/08/21 11:43:08 ...dules/git/command.go:281:Run() [D] git.Command.RunDir(/var/lib/gitea/repositories/stefan.koenen/lfs-test.git): /usr/bin/git -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= cat-file --batch-check 2023/08/21 11:43:08 ...dules/git/command.go:281:Run() [D] git.Command.RunDir(/var/lib/gitea/repositories/stefan.koenen/lfs-test.git): /usr/bin/git -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= for-each-ref "--format=%(objectname) %(refname)" refs/heads/ --sort=-committerdate 2023/08/21 11:43:08 ...ters/web/repo/lfs.go:551:LFSAutoAssociate() [E] LFSAutoAssociate: unable collect all LFS objects from database, expected 1, actually 0 2023/08/21 11:43:08 .../context_response.go:74:HTML() [D] Template: status/500 2023/08/21 11:43:08 ...eb/routing/logger.go:102:func1() [I] router: completed POST /stefan.koenen/lfs-test/settings/lfs/pointers/associate for 192.168.176.5:35444, 500 Internal Server Error in 74.5ms @ repo/lfs.go:527(repo.LFSAutoAssociate) ``` Seems to be related to #17207 I check manually for the files and they are accessible by _git_ user and also the folder is writable. So it seems there is something in the database missing. gitea data: | Name | Value | |------|------| |Site Title | GIT of AIS-Lab | |Gitea Version | 1.20.0 built with GNU Make 4.4.1, go1.20.6 : bindata, timetzdata, sqlite, sqlite_unlock_notify | |Configuration File Path | /etc/gitea/app.ini | |Gitea Base URL | https://git.ais-lab.eu/ | |Server Domain | git.ais-lab.eu | |Local Mode | Disable Router Log | |Run As Username | git | |Run Mode | Prod | |Git Version | 2.40.1, Wire Protocol Version 2 Enabled | |Repository Root Path | /var/lib/gitea/repositories | |Static File Root Path | /var/lib/gitea | |Custom File Root Path | /var/lib/gitea/custom | |Log Path | /var/lib/gitea/log | |Script Type | bash | |Reverse Authentication User | X-WEBAUTH-USER | |__SSH Configuration__ | |Enabled | true | |Use Built-In Server | true | |SSH Server Domain | git.ais-lab.eu | |Port | 22 | |Listen Port | 22 | |__LFS Configuration__ | |Enabled | true | |LFS Content Path | {"Type":"local","Path":"/var/lib/gitea/lfs","TemporaryPath":"/var/lib/gitea/lfs/tmp","MinioConfig":{"UseSSL":false,"InsecureSkipVerify":false,"ServeDirect":false}} | |LFS HTTP Auth Expiry | 24h0m0s | ### Gitea Version 1.20.0 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.40.1, Wire Protocol Version 2 Enabled ### Operating System Fedora Server 37 ### How are you running Gitea? Docker Image __rootless__ version With several NFS-Shares for large data ### Database PostgreSQL
GiteaMirror added the type/bugissue/workaround labels 2025-11-02 09:39:23 -06:00
GiteaMirror commented 2025-11-02 09:39:23 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 21, 2023):

What's your Gitea version?

@lunny commented on GitHub (Aug 21, 2023): What's your Gitea version?
GiteaMirror commented 2025-11-02 09:39:23 -06:00
Author
Owner
Copy Link

@skoenen commented on GitHub (Aug 21, 2023):

Gitea Version: 1.20.0

@skoenen commented on GitHub (Aug 21, 2023): __Gitea Version:__ 1.20.0
GiteaMirror commented 2025-11-02 09:39:24 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 22, 2023):

Can you upgrade to 1.20.3 and try again?

@lunny commented on GitHub (Aug 22, 2023): Can you upgrade to 1.20.3 and try again?
GiteaMirror commented 2025-11-02 09:39:24 -06:00
Author
Owner
Copy Link

@zjjhot commented on GitHub (Aug 23, 2023):

MVGVHKHZ~KWLRCVS18(QV{A

hello，please try to transfer these settings from your old machine's app.ini to new machine.

@zjjhot commented on GitHub (Aug 23, 2023): ![MVGVHKHZ~KWLRCVS18(QV{A](https://github.com/go-gitea/gitea/assets/79889452/865fbce9-e17c-4b6c-afd5-8a6921a1b6e5) hello，please try to transfer these settings from your old machine's app.ini to new machine.
GiteaMirror commented 2025-11-02 09:39:24 -06:00
Author
Owner
Copy Link

@skoenen commented on GitHub (Aug 23, 2023):

I will check these values again, but the app.ini is the same as it was on the old server. The app.ini is on its own nfs share and is just mounted to the new server.

@skoenen commented on GitHub (Aug 23, 2023): I will check these values again, but the app.ini is the same as it was on the old server. The app.ini is on its own nfs share and is just mounted to the new server.
GiteaMirror commented 2025-11-02 09:39:24 -06:00
Author
Owner
Copy Link

@Woodpecker106 commented on GitHub (Dec 29, 2023):

I'm interested to know if you got to the bottom of this as I have the same issue. I just tried copying the LFS secret from my old app.ini to the new one but the issue still persists.

@Woodpecker106 commented on GitHub (Dec 29, 2023): I'm interested to know if you got to the bottom of this as I have the same issue. I just tried copying the LFS secret from my old app.ini to the new one but the issue still persists.
GiteaMirror commented 2025-11-02 09:39:24 -06:00
Author
Owner
Copy Link

@skoenen commented on GitHub (Jan 9, 2024):

I did not manage to solve that automatically. I did manual change the corresponding files/database entries.

@skoenen commented on GitHub (Jan 9, 2024): I did not manage to solve that automatically. I did manual change the corresponding files/database entries.
GiteaMirror commented 2025-11-02 09:39:25 -06:00
Author
Owner
Copy Link

@Endll commented on GitHub (Sep 7, 2024):

Same issue, copying LFS secrets doesn't work either . So is there a solution? @Woodpecker106 @zjjhot I dumped Gitea server from one Windows server to another . Then I got 404 error when I checkout a new branch .

@Endll commented on GitHub (Sep 7, 2024): Same issue, copying LFS secrets doesn't work either . So is there a solution? @Woodpecker106 @zjjhot I dumped Gitea server from one Windows server to another . Then I got 404 error when I checkout a new branch .
GiteaMirror commented 2025-11-02 09:39:25 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Sep 7, 2024):

Maybe you can try to use an admin user to do that? Looks like there is a bug here.

@lunny commented on GitHub (Sep 7, 2024): Maybe you can try to use an admin user to do that? Looks like there is a bug here.
GiteaMirror commented 2025-11-02 09:39:25 -06:00
Author
Owner
Copy Link

@Endll commented on GitHub (Sep 8, 2024):

Maybe you can try to use an admin user to do that? Looks like there is a bug here.

Thanks for the reply, but I didn't understand what to do with the admin account. I registered Gitea as a win service. I modified the LFS secret in app.ini and then restarted the service and it didn't work.

@Endll commented on GitHub (Sep 8, 2024): > Maybe you can try to use an admin user to do that? Looks like there is a bug here. Thanks for the reply, but I didn't understand what to do with the admin account. I registered Gitea as a win service. I modified the LFS secret in app.ini and then restarted the service and it didn't work.
GiteaMirror commented 2025-11-02 09:39:25 -06:00
Author
Owner
Copy Link

@Endll commented on GitHub (Sep 8, 2024):

Maybe you can try to use an admin user to do that? Looks like there is a bug here.

In addition, 404 is a git lfs error instead of a gitea error. When pulling a remote branch, if the remote branch didn't have a git lfs commit, everything is normal. However, if the remote branch has a lfs commit, then an error will occur:
$ git-lfs.exe filter-process
Error downloading object:......
[404] Not Found
[3e8666794abcf279e893f5cec0c54f52e00837bf226c96f5e2aa9c054a0ce538] Not Found
github.com/git-lfs/git-lfs/errors.newWrappedError

@Endll commented on GitHub (Sep 8, 2024): > Maybe you can try to use an admin user to do that? Looks like there is a bug here. In addition, 404 is a git lfs error instead of a gitea error. When pulling a remote branch, if the remote branch didn't have a git lfs commit, everything is normal. However, if the remote branch has a lfs commit, then an error will occur: `$ git-lfs.exe filter-process ` `Error downloading object:......` `[404] Not Found` `[3e8666794abcf279e893f5cec0c54f52e00837bf226c96f5e2aa9c054a0ce538] Not Found` `github.com/git-lfs/git-lfs/errors.newWrappedError`
GiteaMirror commented 2025-11-02 09:39:26 -06:00
Author
Owner
Copy Link

@kai11 commented on GitHub (Sep 1, 2025):

I had similar problem and answer was pretty simple - I migrated gitea files but not database.
Gitea creates new database silently and if your user created automatically as well you won't notice it until weird things like that pop up.
I copied db container to new server and lfs is back up.

@kai11 commented on GitHub (Sep 1, 2025): I had similar problem and answer was pretty simple - I migrated gitea files but not database. Gitea creates new database silently and if your user created automatically as well you won't notice it until weird things like that pop up. I copied db container to new server and lfs is back up.
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 issue/workaround 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#11498
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?