Troubleshooting

    For issues reaching repositories over while the gitea web front-end, buthttps based git repository access works fine, consider looking into the following.

    • 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 ) to ensure a connectioncan be made.
    3. and the repository exists.

    In this case, look into the following settings:

    • On the server:
      • Make sure that the git system user has a usable shell set
      • Verify this with getent passwd git | cut -d: -f7
      • usermod or chsh can be used to modify this.
      • Ensure that the gitea serv command in .ssh/authorized_keys uses thecorrect configuration file.

        Missing releases after migrating repository with tags

    git push —tags

    • (Re-)sync tags of all repositories within gitea:
      gitea admin repo-sync-releases