-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Unix socket: cannot pull/push over SSH #3741
Comments
When using unix sockets you should not set |
It works fine that way, but that is not what I understand from
|
Yes this description is correct only if using http protocol for gitea listener, description needs to be updated if using other protocols |
Couldn't this be done automatically when listening on a unix socket? |
It is if you have not set |
What I meant is that we could ignore |
) Update the sample configuration and config cheat sheet description for the LOCAL_ROOT_URL configuration variable to mention the special case required if PROTOCOL is set to 'unix'. Fixes #3741. Signed-off-by: Timothée Ravier <tim@siosm.fr>
[x]
):Description
With the following configuration (actual domain redacted by example.com) in the
[server]
section:Trying to perform a git pull/push via SSH results in an error :
Looks like a regression over #2232, which has been fixed months ago. Adding some good old
Printf
traces in the code, I can see thatreq.SetTransport
is called innewInternalRequest
, but theDial
function that is set up there is never called ; the error is encountered before then. ChangingLOCAL_ROOT_URL
tohttp://%(DOMAIN)s/
fixes the issue : both thereq.SetTransport
andDial
functions are called, and the request is performed on the unix socket (no log in the reverse proxy that’s listening on https://git.example.com/, and addingdeny all
on the reverse proxy do not prevent SSH pull/push), but that does not looks like to be the intended behavior.The text was updated successfully, but these errors were encountered: