This page contains some common seen issues and their solutions.
For issues reaching repositories over ssh
while the gitea web front-end, but
https
based git repository access works fine, consider looking into the following.
Permission denied (publickey).
fatal: Could not read from remote repository.
This error signifies that the server rejected a log in attempt, check the following things:
@
) is spelled correctly..ssh
directory in the system user’s home directory..ssh/authorized_keys
.
Try to run Rewrite '.ssh/authorized_keys' file (for Gitea SSH keys)
on the
Gitea admin panel.The following is an example of a missing public SSH key where authentication succeeded, but some other setting is preventing SSH from reaching the correct repository.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
In this case, look into the following settings:
git
system user has a usable shell setgetent passwd git | cut -d: -f7
usermod
or chsh
can be used to modify this.gitea serv
command in .ssh/authorized_keys
uses the
correct configuration file.To migrate an repository with all tags you need to do two things
Push tags to the repository:
git push --tags
gitea admin repo-sync-releases
For issues concerning LFS data upload
batch response: Authentication required: Authorization error: <GITEA_LFS_URL>/info/lfs/objects/batch
Check that you have proper access to the repository
error: failed to push some refs to '<GIT_REPO_URL>'
Have you checked the value of LFS_HTTP_AUTH_EXPIRY
in your app.ini
file? By default your LFS token will expire after 20 minutes. If you have a slow connection or a large file (or both) it may not finish uploading within the time limit.
You may want to set this value to 60m
or 120m
.