-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LFS gives 404 error, after migrating gitea service from server to another server #26628
Comments
What's your Gitea version? |
Gitea Version: 1.20.0 |
Can you upgrade to 1.20.3 and try again? |
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. |
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. |
I did not manage to solve that automatically. I did manual change the corresponding files/database entries. |
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 . |
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. |
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: |
Description
Hi there,
recently we had to move our gitea service from one machine to a newer machine.
Process:
/etc/gitea
/var/lib/gitea
/var/lib/gitea/home/.ssh
/var/lib/gitea/repositories
/var/lib/gitea/lfs
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.
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:
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
The text was updated successfully, but these errors were encountered: