-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reverse proxy login error on git push/clone #3973
Comments
The same happens to me. I am not using LDAP, and my reverse proxy is Apache (so I suppose this is likely not something specific to either LDAP or Nginx). My Gitea vresion is |
Updated to Cloning/pulling/pushing through ssh works; and I can log in with a browser without problems. |
Oh, I see what the problem was. Setting these:
in @brandonocasey could you try that? |
Yeah that fixed if for me as well. It seems like reverse proxy login auth actually works without those settings anyway. |
By reverse proxy login auth do you mean "getting authenticated with Gitea, going through a reverse proxy", or "doing HTTP auth in the reverse proxy in order to get to Gitea"? I believe it's the second, but I'm not sure (this should be documented). |
Sorry for the very long delay, its the second one as you thought. |
* Make reverse proxy auth optional If the option ENABLE_REVERSE_PROXY_AUTHENTICATION is enabled, make reverse proxy auth optional, instead of failing if the authentication did not succeed. Fixes #3973 Signed-off-by: Najib Idrissi <najib.idrissi.kaitouni@gmail.com> * Update http.go
1546458
(listed in the footer)git version 2.17.0
[x]
):Description
I am trying to push/clone repos in gitea. My previous configuration worked in gogs
Steps
http://127.0.0.1:3000
to ->https://test.example.com
with a valid ssl cert.https://test.example.com/test/test.git
https://test.example.com/test/test.git
https://test@test.example.com/test/test.git
Both 4/5 result in:
remote: reverse proxy login error. authUsername empty
nginx config
app.ini
The text was updated successfully, but these errors were encountered: