mirror of https://github.com/go-gitea/gitea
Git with a cup of tea, painless self-hosted git service
Mirror for internal git.with.parts use
https://git.with.parts
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2.4 KiB
2.4 KiB
| date | title | slug | weight | toc | draft | menu |
|---|---|---|---|---|---|---|
| 2016-11-08T16:00:00+02:00 | Troubleshooting | troubleshooting | 10 | true | false | [{sidebar [{parent help} {name Troubleshooting} {weight 20} {identifier troubleshooting}]}] |
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, 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:
- 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 the
git 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 connection can be made.
- On the server:
- Make sure the repository exists and is correctly named.
- Check the permissions of the
.sshdirectory in the system user's home directory. - Verify that the correct public keys are added to
.ssh/authorized_keys. Try to runRewrite '.ssh/authorized_keys' file (for Gitea SSH keys)on the Gitea 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 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:
- On the server:
- Make sure that the
gitsystem user has a usable shell set- Verify this with
getent passwd git | cut -d: -f7 usermodorchshcan be used to modify this.
- Verify this with
- Ensure that the
gitea servcommand in.ssh/authorized_keysuses the correct configuration file.
- Make sure that the
Missing releases after migrating repository with tags
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