I'm pretty sure you have a configuration problem between SSH and the system because of this SSH debug message :
client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
You receive this message immediately after a successful authentication and no message from bash which means no program was launched after login.
Watch in your passwd file if you have the right settings for the gitlab user :
gitlab:x:1011:1012:GitLab,,,:/path/to/gitlab:/bin/bash
Verify bash has no weird thing in configurations files such as
- bash.bashrc
- .profile
- .bashrc
Then go up to the uper level : Gitlab-shell
Verify the /path/to/gitlab/.ssh/authorized_keys has the configuration below :
command="/path/to/gitlab/gitlab-shell/bin/gitlab-shell key-2",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa A...
with /path/to/gitlab/gitlab-shell/bin/gitlab-shell owned by the gitlab user and executable.
You can be sure gitlab-shell is fully operational by launching the command :
# /path/to/gitlab-shell/bin/gitlab-shell
Welcome to GitLab, Anonymous!
If the remote login is actually working and properly connected to the gitlab-shell, you should get the same welcome message (but matched to the user whose ssh key you used to login) before it dumps you out if you try to login remotely.
$ ssh gitlab@server
Welcome to GitLab, <your user's full name>!
Connection to <server> closed.
No message here probably indicates ssh isn't connecting you to gitlab at all.
Finally, checkout your gitlab-shell configuration (config.yml) and verify if :
http_settings:
# trailing slash is important
gitlab_url: "https://remote_server/"
ca_file: /path/to/webserver/certificate.crt
and eventually :
self_signed_cert: false
Best Answer
The answer from unixandria is correct for when it's from. Things have changed a little since then.
There's now this official section on GitLab Docs.
Also, GitLab 13.5 changed the location of the unix socket, so the Caddyfile should have this now: