[GH-ISSUE #126] 异常:ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain #29

Open
opened 2026-02-28 00:38:25 +03:00 by kerem · 7 comments
Owner

Originally created by @zhangwei911 on GitHub (Oct 21, 2023).
Original GitHub issue: https://github.com/team-ide/teamide/issues/126

异常:ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain

Originally created by @zhangwei911 on GitHub (Oct 21, 2023). Original GitHub issue: https://github.com/team-ide/teamide/issues/126 异常:ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain
Author
Owner

@team-ide commented on GitHub (Oct 24, 2023):

这个应该是SSH服务器加密方式不同,我这边看下添加加密方式,你方便说下 你的SSH服务的加密方式、SSH版本吗

<!-- gh-comment-id:1776617762 --> @team-ide commented on GitHub (Oct 24, 2023): 这个应该是SSH服务器加密方式不同,我这边看下添加加密方式,你方便说下 你的SSH服务的加密方式、SSH版本吗
Author
Owner

@zhangwei911 commented on GitHub (Oct 24, 2023):

是这样看吗?
| |
张维
|
|
@.***
|
---- 回复的原邮件 ----
| 发件人 | @.> |
| 发送日期 | 2023年10月24日 14:41 |
| 收件人 | @.
> |
| 抄送人 | @.> ,
@.
> |
| 主题 | Re: [team-ide/teamide] 异常:ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain (Issue #126) |

这个应该是SSH服务器加密方式不同,我这边看下添加加密方式,你方便说下 你的SSH服务的加密方式吗


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

<!-- gh-comment-id:1776782858 --> @zhangwei911 commented on GitHub (Oct 24, 2023): 是这样看吗? | | 张维 | | ***@***.*** | ---- 回复的原邮件 ---- | 发件人 | ***@***.***> | | 发送日期 | 2023年10月24日 14:41 | | 收件人 | ***@***.***> | | 抄送人 | ***@***.***> , ***@***.***> | | 主题 | Re: [team-ide/teamide] 异常:ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain (Issue #126) | 这个应该是SSH服务器加密方式不同,我这边看下添加加密方式,你方便说下 你的SSH服务的加密方式吗 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>
Author
Owner

@zhangwei911 commented on GitHub (Oct 24, 2023):

[root@VM-4-5-opencloudos ~]# ssh -Q cipher
3des-cbc
aes128-cbc
aes192-cbc
aes256-cbc
rijndael-cbc@lysator.liu.se
aes128-ctr
aes192-ctr
aes256-ctr
aes128-gcm@openssh.com
aes256-gcm@openssh.com
chacha20-poly1305@openssh.com
[root@VM-4-5-opencloudos ~]# ssh -Q cipher-auth
aes128-gcm@openssh.com
aes256-gcm@openssh.com
chacha20-poly1305@openssh.com
[root@VM-4-5-opencloudos ~]# ssh -Q mac
hmac-sha1
hmac-sha1-96
hmac-sha2-256
hmac-sha2-512
hmac-md5
hmac-md5-96
umac-64@openssh.com
umac-128@openssh.com
hmac-sha1-etm@openssh.com
hmac-sha1-96-etm@openssh.com
hmac-sha2-256-etm@openssh.com
hmac-sha2-512-etm@openssh.com
hmac-md5-etm@openssh.com
hmac-md5-96-etm@openssh.com
umac-64-etm@openssh.com
umac-128-etm@openssh.com

[root@VM-4-5-opencloudos ~]# ssh -V
OpenSSH_8.0p1, OpenSSL 1.1.1k FIPS 25 Mar 2021

<!-- gh-comment-id:1776802134 --> @zhangwei911 commented on GitHub (Oct 24, 2023): [root@VM-4-5-opencloudos ~]# ssh -Q cipher 3des-cbc aes128-cbc aes192-cbc aes256-cbc rijndael-cbc@lysator.liu.se aes128-ctr aes192-ctr aes256-ctr aes128-gcm@openssh.com aes256-gcm@openssh.com chacha20-poly1305@openssh.com [root@VM-4-5-opencloudos ~]# ssh -Q cipher-auth aes128-gcm@openssh.com aes256-gcm@openssh.com chacha20-poly1305@openssh.com [root@VM-4-5-opencloudos ~]# ssh -Q mac hmac-sha1 hmac-sha1-96 hmac-sha2-256 hmac-sha2-512 hmac-md5 hmac-md5-96 umac-64@openssh.com umac-128@openssh.com hmac-sha1-etm@openssh.com hmac-sha1-96-etm@openssh.com hmac-sha2-256-etm@openssh.com hmac-sha2-512-etm@openssh.com hmac-md5-etm@openssh.com hmac-md5-96-etm@openssh.com umac-64-etm@openssh.com umac-128-etm@openssh.com [root@VM-4-5-opencloudos ~]# ssh -V OpenSSH_8.0p1, OpenSSL 1.1.1k FIPS 25 Mar 2021
Author
Owner

@team-ide commented on GitHub (Oct 24, 2023):

我这边升级到同样的版本,加密方式相同,可以登录
你检查下 /etc/ssh/sshd_config/etc/ssh/ssh_config 配置中 PasswordAuthentication 值是否是 yes
ssh必须配置密码,检查密码输入是否正确

<!-- gh-comment-id:1777007422 --> @team-ide commented on GitHub (Oct 24, 2023): 我这边升级到同样的版本,加密方式相同,可以登录 你检查下 `/etc/ssh/sshd_config`、`/etc/ssh/ssh_config` 配置中 `PasswordAuthentication` 值是否是 `yes` ssh必须配置密码,检查密码输入是否正确
Author
Owner

@zhangwei911 commented on GitHub (Oct 24, 2023):

我用windterm和termius都可以

---- 回复的原邮件 ----
| 发件人 | @.> |
| 日期 | 2023年10月24日 19:15 |
| 收件人 | @.
> |
| 抄送至 | @.>@.> |
| 主题 | Re: [team-ide/teamide] 异常:ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain (Issue #126) |

我这边升级到同样的版本,加密方式相同,可以登录
你检查下 /etc/ssh/sshd_config、/etc/ssh/ssh_config 配置中 PasswordAuthentication 值是否是 yes
ssh必须配置密码,检查密码输入是否正确


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

<!-- gh-comment-id:1777039652 --> @zhangwei911 commented on GitHub (Oct 24, 2023): 我用windterm和termius都可以 ---- 回复的原邮件 ---- | 发件人 | ***@***.***> | | 日期 | 2023年10月24日 19:15 | | 收件人 | ***@***.***> | | 抄送至 | ***@***.***>***@***.***> | | 主题 | Re: [team-ide/teamide] 异常:ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain (Issue #126) | 我这边升级到同样的版本,加密方式相同,可以登录 你检查下 /etc/ssh/sshd_config、/etc/ssh/ssh_config 配置中 PasswordAuthentication 值是否是 yes ssh必须配置密码,检查密码输入是否正确 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>
Author
Owner

@team-ide commented on GitHub (Oct 25, 2023):

我这边再看看吧 复现不出来不好弄

<!-- gh-comment-id:1778406182 --> @team-ide commented on GitHub (Oct 25, 2023): 我这边再看看吧 复现不出来不好弄
Author
Owner

@w37fhy commented on GitHub (Nov 5, 2023):

我所有GCP的VPS,都无法登录,都提示 start error:ssh: handshake failed: EOF

<!-- gh-comment-id:1793755994 --> @w37fhy commented on GitHub (Nov 5, 2023): 我所有GCP的VPS,都无法登录,都提示 start error:ssh: handshake failed: EOF
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/teamide-team-ide#29
No description provided.