Troubleshooting
This page contains some common seen issues and their solutions.
SSH issues
For issues reaching repositories over ssh
while the gitea web front-end, buthttps
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 thefollowing things:
- On the client:
- Ensure the public and private ssh keys are added to the correct Gitea user.
- Make sure there are no issues in the remote url, ensure the name of thegit user (before the @) is spelled correctly.
- Ensure public and private ssh keys are correct on client machine.
- Try to connect using ssh (ssh git@myremote.example) to ensure a connectioncan be made.
- On the server:
- Make sure the repository exists and is correctly named.
- Check the permissions of the .ssh directory in the system user’s home directory.
- Verify that the correct public keys are added to .ssh/authorized_keys.Try to run Rewrite '.ssh/authorized_keys' file (for Gitea SSH keys) on theGitea admin panel.
- Read gitea logs.
- Read /var/log/auth (or similar).
- Check permissions of repositories.
The following is an example of a missing public SSH key where authenticationsucceeded, but some other setting is preventing SSH from reaching the correctrepository.
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:
- On the server:
To migrate an repository with all tags you need to do two things
- Push tags to the repository:
git push —tags
- (Re-)sync tags of all repositories within gitea:
gitea admin repo-sync-releases