[GH-ISSUE #2463] 开启加密后似乎有些问题 #1954

New issue

Closed

opened 2026-05-05 13:15:28 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 13:15:28 -06:00

Owner

Originally created by @GravenCh on GitHub (Jun 27, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2463

客户端和服务端都是使用的最新版本FRP

开启了加密参数之后，每次第一次ssh都是失败的，第二次就可以成功

场景：
使用frp访问远程机器，通过密钥文件登陆，第一次永远是失败的，第二次或许可以成功，也有可能第三次才能成功

其他配置：
关闭了mux
设置了pool_count

错误提示：
kex_exchange_identification: Connection closed by remote host

附ssh时服务端日志（IP已经脱敏）：
2021/06/27 16:33:10 [W] [proxy.go:133] [3d7ca5f87cec6b07] [Server-ssh] failed to send message to work connection from pool: write tcp 172.27.0.16:18000->xxx:36044: write: connection timed out, times: 63
2021/06/27 16:33:10 [W] [proxy.go:133] [3d7ca5f87cec6b07] [Server-ssh] failed to send message to work connection from pool: write tcp 172.27.0.16:18000->xxx:36050: write: connection timed out, times: 64
2021/06/27 16:33:15 [I] [proxy.go:162] [3d7ca5f87cec6b07] [Server-ssh] get a user connection [xxx:11383]

问题也同样出现在https的穿透上，会提示SSL证书错误，同样是第二或者第三次就成功

Originally created by @GravenCh on GitHub (Jun 27, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2463 客户端和服务端都是使用的最新版本FRP 开启了加密参数之后，每次第一次ssh都是失败的，第二次就可以成功场景：使用frp访问远程机器，通过密钥文件登陆，第一次永远是失败的，第二次或许可以成功，也有可能第三次才能成功其他配置：关闭了mux 设置了pool_count 错误提示： kex_exchange_identification: Connection closed by remote host 附ssh时服务端日志（IP已经脱敏）： 2021/06/27 16:33:10 [W] [proxy.go:133] [3d7ca5f87cec6b07] [Server-ssh] failed to send message to work connection from pool: write tcp 172.27.0.16:18000->xxx:36044: write: connection timed out, times: 63 2021/06/27 16:33:10 [W] [proxy.go:133] [3d7ca5f87cec6b07] [Server-ssh] failed to send message to work connection from pool: write tcp 172.27.0.16:18000->xxx:36050: write: connection timed out, times: 64 2021/06/27 16:33:15 [I] [proxy.go:162] [3d7ca5f87cec6b07] [Server-ssh] get a user connection [xxx:11383] 问题也同样出现在https的穿透上，会提示SSL证书错误，同样是第二或者第三次就成功

gitea-mirror

2026-05-05 13:15:28 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:15:31 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 5, 2021):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Aug 5, 2021): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.