Skip to content
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

SSH not accessible / configuration issue? #377

Closed
1 of 3 tasks
redradrat opened this issue Dec 12, 2016 · 4 comments · Fixed by #386
Closed
1 of 3 tasks

SSH not accessible / configuration issue? #377

redradrat opened this issue Dec 12, 2016 · 4 comments · Fixed by #386

Comments

@redradrat
Copy link

redradrat commented Dec 12, 2016

  • Gitea version (or commit ref): master
  • Git version: 2.8.3
  • Operating system: gitea/gitea Docker Image | Alpine 3.4
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • SQLite

Description

There might be something wrong with the sshd config on the gitea docker image. Spinning up a fresh container and adding my ssh key, logging in with

ssh -l git INSTANCEADDRESS -p PORT

is not possible.

Output sshd.log

rexec line 21: Unsupported option PrintLastLog
User git not allowed because account is locked
input_userauth_request: invalid user git
Failed none for invalid user git from XXX.XXX.XXX.XXX port XXXXX ssh2
Failed publickey for invalid user git from XXX.XXX.XXX.XXX port XXXXX ssh2
Connection closed by XXX.XXX.XXX.XXX port XXXXX

With the latest gogs image that is not the case.

@redradrat
Copy link
Author

redradrat commented Dec 12, 2016

To clarify:

gogs responds to the ssh login with

PTY allocation request failed on channel 0
Hi there, You've successfully authenticated, but Gogs does not provide shell access.
If this is unexpected, please log in with password and setup Gogs under another user.
Connection to XXX.XXX.XXX.XXX closed.

Which is the expected response, and confirms the sshd config.

@bkcsoft
Copy link
Member

bkcsoft commented Dec 12, 2016

@tboerger @xinity IIRC you guys knows the docker-image best

@tboerger
Copy link
Member

Will get into that directly when I'm launching try.gitea.io

@tboerger
Copy link
Member

So #386 will solve this issue. But be warned that we would like to restructure some of the volume directories because it got currently a pretty weird too deep nested structure.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants