Unable to clone repo via SSH [Podman pod, rootless container] #8728

New Issue

GiteaMirror · 2025-11-02T08:15:41-06:00

GiteaMirror commented

2025-11-02 08:15:41 -06:00

Originally created by @ghost on GitHub (Mar 20, 2022).

Gitea Version

1.16.4

Git Version

2.30.2

Operating System

Podman rootless container on openSUSE MicroOS host

How are you running Gitea?

I am running my self-hosted Gitea instance on home server. I create simple script to run Podman's pod with Postgre and Gitea-rootless container behind Caddy reverse proxy

#!/usr/bin/env bash
set -e
podman pod create --infra -n gitea -p 3000:3000 -p 2222:2222

podman run --pod gitea --name db \
       -e POSTGRES_USER=db \
       -e POSTGRES_PASSWORD=somePassword \
       -e POSTGRES_DB=giteadb \
       -e PGDATA=/var/lib/postgresql/data/pgdata \
       -v db-data:/var/lib/postgresql/data \
       -d docker.io/library/postgres

podman run --pod gitea --name app \
       -e DB_TYPE=postgres \
       -e DB_HOST=localhost:5432 \
       -e DB_NAME=giteadb \
       -e DB_USER=db \
       -e DB_PASSWD=somePassword \
       -v gitea-data:/var/lib/gitea \
       -v gitea-config:/etc/gitea \
       -d docker.io/gitea/gitea:latest-rootless

Caddyfile

my.gitea.instance:443 {
	reverse_proxy HOST_IP:3000
}

I use built-it SSH server so in installation wizard on browser I put port 2222 in config and my domain name

[server]
...
SSH_DOMAIN              = my.gitea.instance
HTTP_PORT               = 3000
ROOT_URL                = https://my.gitea.instance/
DISABLE_SSH             = false
...
START_SSH_SERVER        = true
SSH_PORT                = 2222
SSH_LISTEN_PORT         = 2222
BUILTIN_SSH_SERVER_USER = git
...
DOMAIN                  = my.gitea.instance

Database

PostgreSQL

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

I've setup added server, user and port in my sshd_config, added my public key to my user account, created repo and during clone I received an error:

> git clone ssh://git@my.gitea.instance:2222/asterops/test.git
Cloning into 'test'...
git@my.gitea.instance: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

On the Gitea's log I see only these two lines (I've increased log level to debug):

2022/03/20 11:23:56 modules/ssh/ssh.go:260:sshConnectionFailed() [W] Failed connection from 10.0.2.100:36362 with error: [ssh: no auth passed yet]
2022/03/20 11:23:56 modules/ssh/ssh.go:262:sshConnectionFailed() [W] Failed authentication attempt from 10.0.2.100:36362

I also manually run Update the '.ssh/authorized_keys' file with Gitea SSH keys. cron task from UI but it didn't change anything. What else can I check?

Screenshots

No response

Originally created by @ghost on GitHub (Mar 20, 2022). ### Gitea Version 1.16.4 ### Git Version 2.30.2 ### Operating System Podman rootless container on openSUSE MicroOS host ### How are you running Gitea? I am running my self-hosted Gitea instance on home server. I create simple script to run Podman's [pod](https://developers.redhat.com/blog/2019/01/15/podman-managing-containers-pods#) with Postgre and Gitea-rootless container behind Caddy reverse proxy ``` bash #!/usr/bin/env bash set -e podman pod create --infra -n gitea -p 3000:3000 -p 2222:2222 podman run --pod gitea --name db \ -e POSTGRES_USER=db \ -e POSTGRES_PASSWORD=somePassword \ -e POSTGRES_DB=giteadb \ -e PGDATA=/var/lib/postgresql/data/pgdata \ -v db-data:/var/lib/postgresql/data \ -d docker.io/library/postgres podman run --pod gitea --name app \ -e DB_TYPE=postgres \ -e DB_HOST=localhost:5432 \ -e DB_NAME=giteadb \ -e DB_USER=db \ -e DB_PASSWD=somePassword \ -v gitea-data:/var/lib/gitea \ -v gitea-config:/etc/gitea \ -d docker.io/gitea/gitea:latest-rootless ``` Caddyfile ``` my.gitea.instance:443 { reverse_proxy HOST_IP:3000 } ``` I use built-it SSH server so in installation wizard on browser I put port 2222 in config and my domain name ``` ini [server] ... SSH_DOMAIN = my.gitea.instance HTTP_PORT = 3000 ROOT_URL = https://my.gitea.instance/ DISABLE_SSH = false ... START_SSH_SERVER = true SSH_PORT = 2222 SSH_LISTEN_PORT = 2222 BUILTIN_SSH_SERVER_USER = git ... DOMAIN = my.gitea.instance ``` ### Database PostgreSQL ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Description I've setup added server, user and port in my `sshd_config`, added my public key to my user account, created repo and during clone I received an error: ``` bash > git clone ssh://git@my.gitea.instance:2222/asterops/test.git Cloning into 'test'... git@my.gitea.instance: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ``` On the Gitea's log I see only these two lines (I've increased log level to debug): ``` bash 2022/03/20 11:23:56 modules/ssh/ssh.go:260:sshConnectionFailed() [W] Failed connection from 10.0.2.100:36362 with error: [ssh: no auth passed yet] 2022/03/20 11:23:56 modules/ssh/ssh.go:262:sshConnectionFailed() [W] Failed authentication attempt from 10.0.2.100:36362 ``` I also manually run `Update the '.ssh/authorized_keys' file with Gitea SSH keys.` cron task from UI but it didn't change anything. What else can I check? ### Screenshots _No response_

GiteaMirror added the type/question issue/needs-feedback labels 2025-11-02 08:15:42 -06:00

GiteaMirror closed this issue

2025-11-02 08:15:42 -06:00

GiteaMirror commented

2025-11-02 08:15:42 -06:00

@techknowlogick commented on GitHub (Apr 12, 2022):

I also manually run Update the '.ssh/authorized_keys' file with Gitea SSH keys. cron task from UI but it didn't change anything. What else can I check?

Rootless doesn't use the authorized_key file as it runs an SSH server internal to the golang binary and fetches keys directly from the database.

You mention changing sshd_config, can you provide more details on that, as above opensshd is not used. Do you mean your ~/.ssh/config?

Are you able to attempt connecting using ssh directly (ssh -vvv -p 2222 git@example.com)? This will give more details on if the expected key is being sent.

@techknowlogick commented on GitHub (Apr 12, 2022): > I also manually run Update the '.ssh/authorized_keys' file with Gitea SSH keys. cron task from UI but it didn't change anything. What else can I check? Rootless doesn't use the authorized_key file as it runs an SSH server internal to the golang binary and fetches keys directly from the database. You mention changing ssh**d**_config, can you provide more details on that, as above opensshd is not used. Do you mean your `~/.ssh/config`? Are you able to attempt connecting using ssh directly (`ssh -vvv -p 2222 git@example.com`)? This will give more details on if the expected key is being sent.

GiteaMirror commented

2025-11-02 08:15:42 -06:00

@polyurethanegoose commented on GitHub (Apr 15, 2022):

@AsterOps Please verify that this is not connected to issue #17175 I've got the same problem with same message in logs with rootless Podman container and found out that i had to add -o PubkeyAcceptedKeyTypes=+ssh-rsa -o PubkeyAcceptedAlgorithms=+ssh-rsa to my clone commands.

@polyurethanegoose commented on GitHub (Apr 15, 2022): @AsterOps Please verify that this is not connected to issue #17175 I've got the same problem with same message in logs with rootless Podman container and found out that i had to add `-o PubkeyAcceptedKeyTypes=+ssh-rsa -o PubkeyAcceptedAlgorithms=+ssh-rsa` to my clone commands.

GiteaMirror commented

2025-11-02 08:15:43 -06:00

@fengjiongmax commented on GitHub (May 26, 2022):

I have a similar issue but I'm not sure if I have the same environment( search keyword no auth passed yet brought me here).

my environment is with truenas scale box and gitea installed via truenas charts, so my installed version is 1.16.8.

After a fresh install, I add the ssh pub key from gitea web UI, and ssh [git@gitea] -T failed.

ssh -vvv log:
ssh log with ssh info defined in .ssh/config
ssh log file with bare ssh command

Gitea log shows the same warning as OP.

2022/06/04 03:40:09 modules/ssh/ssh.go:260:sshConnectionFailed() [W] Failed connection from 172.16.33.133:55610 with error: [ssh: no auth passed yet]
2022/06/04 03:40:09 modules/ssh/ssh.go:262:sshConnectionFailed() [W] Failed authentication attempt from 172.16.33.133:55610

is there anything I can do to provide more information?

@fengjiongmax commented on GitHub (May 26, 2022): I have a similar issue but I'm not sure if I have the same environment( search keyword `no auth passed yet` brought me here). my environment is with truenas scale box and gitea installed via [truenas charts](https://truecharts.org/apps/stable/gitea/), so my installed version is `1.16.8`. After a fresh install, I add the ssh pub key from gitea web UI, and `ssh [git@gitea] -T` failed. `ssh -vvv` log: [ssh log with ssh info defined in .ssh/config](https://gist.github.com/fengjiongmax/ae81f2ae2f18016178ba224d5d4a3ac0#file-ssh-vvv) [ssh log file with bare ssh command](https://gist.github.com/fengjiongmax/ae81f2ae2f18016178ba224d5d4a3ac0#file-ssh-vvv-with-ip) Gitea log shows the same warning as OP. ``` 2022/06/04 03:40:09 modules/ssh/ssh.go:260:sshConnectionFailed() [W] Failed connection from 172.16.33.133:55610 with error: [ssh: no auth passed yet] 2022/06/04 03:40:09 modules/ssh/ssh.go:262:sshConnectionFailed() [W] Failed authentication attempt from 172.16.33.133:55610 ``` is there anything I can do to provide more information?

GiteaMirror commented

2025-11-02 08:15:43 -06:00

@wxiaoguang commented on GitHub (Oct 19, 2022):

About the problem for rootless container:

https://github.com/go-gitea/gitea/issues/17798

This issue is inactive for long time and Gitea 1.16.x is out-dated. Feel free to re-open or open a new issue if there is any other problem.

@wxiaoguang commented on GitHub (Oct 19, 2022): About the problem for rootless container: * https://github.com/go-gitea/gitea/issues/17798 This issue is inactive for long time and Gitea 1.16.x is out-dated. Feel free to re-open or open a new issue if there is any other problem.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#8728