[GH-ISSUE #2077] 配置tls双向验证出错 #1651

New issue

Closed

opened 2026-05-05 13:03:22 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 13:03:22 -06:00

Owner

Originally created by @lim-wei on GitHub (Nov 13, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/2077

按照文档生成对应文件，并修改相关配置后无法连接
配置如下
frpc.ini
[common] server_addr = server_port = 7000 tls_enable = true tls_cert_file = /usr/local/frp/client.crt tls_key_file = /usr/local/frp/client.key tls_trusted_ca_file = /usr/local/frp/ca.crt
frps.ini
[common] bind_port = 7000 vhost_http_port = 8084 tls_cert_file = /usr/local/frp/server.crt tls_key_file = /usr/local/frp/server.key tls_trusted_ca_file = /usr/local/frp/ca.crt
报错信息
客户端：[W] [service.go:102] login to server failed: session shutdown
session shutdown

Originally created by @lim-wei on GitHub (Nov 13, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/2077 按照文档生成对应文件，并修改相关配置后无法连接配置如下 frpc.ini ` [common] server_addr = server_port = 7000 tls_enable = true tls_cert_file = /usr/local/frp/client.crt tls_key_file = /usr/local/frp/client.key tls_trusted_ca_file = /usr/local/frp/ca.crt ` frps.ini `[common] bind_port = 7000 vhost_http_port = 8084 tls_cert_file = /usr/local/frp/server.crt tls_key_file = /usr/local/frp/server.key tls_trusted_ca_file = /usr/local/frp/ca.crt ` 报错信息客户端：[W] [service.go:102] login to server failed: session shutdown session shutdown

gitea-mirror

2026-05-05 13:03:22 -06:00

closed this issue
added the
lifecycle/stale

need-issue-template
labels

gitea-mirror commented

2026-05-05 13:03:26 -06:00

Author

Owner

@shenlijun commented on GitHub (Nov 23, 2020):

Let's Encrypt申请的证书遇到同样的问题

@shenlijun commented on GitHub (Nov 23, 2020): Let's Encrypt申请的证书遇到同样的问题

gitea-mirror commented

2026-05-05 13:03:26 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 8, 2021):

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

@github-actions[bot] commented on GitHub (Jan 8, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 13:03:27 -06:00

Author

Owner

@ppllpig commented on GitHub (Jul 1, 2023):

我是通过KCP解决的

@ppllpig commented on GitHub (Jul 1, 2023): 我是通过KCP解决的