SSH not accessible / configuration issue? #119

Closed
opened 2025-11-02 03:09:48 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @redradrat on GitHub (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.

Originally created by @redradrat on GitHub (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 - [x] 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.
GiteaMirror added the type/bugtopic/deployment labels 2025-11-02 03:09:48 -06:00
Author
Owner

@redradrat commented on GitHub (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.

@redradrat commented on GitHub (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.
Author
Owner

@bkcsoft commented on GitHub (Dec 12, 2016):

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

@bkcsoft commented on GitHub (Dec 12, 2016): @tboerger @xinity IIRC you guys knows the docker-image best
Author
Owner

@tboerger commented on GitHub (Dec 13, 2016):

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

@tboerger commented on GitHub (Dec 13, 2016): Will get into that directly when I'm launching try.gitea.io
Author
Owner

@tboerger commented on GitHub (Dec 14, 2016):

So https://github.com/go-gitea/gitea/pull/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.

@tboerger commented on GitHub (Dec 14, 2016): So https://github.com/go-gitea/gitea/pull/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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#119