Hello! I have been using Gitea for several years on different projects and I am very happy! However, on the last project I needed a non-standard use. I deployed the default Gitea deployment via Helm Chart in Kubernetes. I use this instance as a mirror to existing repositories. I make all mirrors public and get access to these repositories for cloning via HTTP. Everything is going well, mirrors are successfully cloned to local devices without using authorization. However, if someone tries to clone a non-existent repository (mirror) to themselves, Gitea asks to authorize. Is it possible to disable this logic? So that Gitea gives a deny if the repo is missing or closed immediately, without authorization? Using SSSH keys in this case is impossible, for internal technical reasons.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| (Problem) Unauthenticated cloning of private repos is allowed | 0 | 62 | October 9, 2025 | |
| [SOLVED] Using regular Git ssh not working | 19 | 55402 | May 23, 2018 | |
| Using OAuth2 for Git Repo Cloning in Gitea | 1 | 1059 | September 22, 2023 | |
| Unable to clone repo with SSH | 3 | 7803 | February 3, 2023 | |
| How to Fix the Issue Where Web Authentication Is Required When Cloning a Repository, but Cloning Still Doesn’t Respond After Confirming Authorization | 0 | 71 | October 9, 2025 |