[GH-ISSUE #2887] FRP Client and server versions do not match

gitea-mirror commented

2026-05-05 13:29:09 -06:00

Owner

Copy link

Originally created by @section9-lab on GitHub (Apr 8, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2887

Bug Description

When tls1.3 is enabled. frpcversion 0.32.0 is not compatible with frps0.37.1

frpc Version

0.32.0

frps Version

0.37.1

System Architecture

linux/amd64

Configurations

server_addr=proxy.xxx.xxxx.com
server_port=7002
token=xxxxxxxxxxxxxxxx
tls_enable=true
tls_cert_file = /client.crt
tls_key_file = /client.key
tls_trusted_ca_file = /root.crt
admin_addr=xx.xx.xx.xx
admin_port=7400
admin_user=xx
admin_pwd=xxxxxxx
log_file=/logs/frpc.log
log_level=info
log_max_days=1
[https_sxx33]
type=https
local_ip=xx.xx.xx.xx
local_port=443
subdomain=xxx
auth_valid_to=2099-12-31
auth_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
sign=xxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxx=

Logs

2022/04/08 18:41:37 [T] [service.go:425] start check TLS connection...
2022/04/08 18:41:37 [T] [service.go:425] success check TLS connection
2022/04/08 18:41:37 [D] [service.go:425] Accept new mux stream error:tls:client didn't provide a certificate

Steps to reproduce

./frpc -c xxxxx.cert
EOF

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @section9-lab on GitHub (Apr 8, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2887 ### Bug Description When tls1.3 is enabled. frpcversion 0.32.0 is not compatible with frps0.37.1 ### frpc Version 0.32.0 ### frps Version 0.37.1 ### System Architecture linux/amd64 ### Configurations server_addr=proxy.xxx.xxxx.com server_port=7002 token=xxxxxxxxxxxxxxxx tls_enable=true tls_cert_file = /client.crt tls_key_file = /client.key tls_trusted_ca_file = /root.crt admin_addr=xx.xx.xx.xx admin_port=7400 admin_user=xx admin_pwd=xxxxxxx log_file=/logs/frpc.log log_level=info log_max_days=1 [https_sxx33] type=https local_ip=xx.xx.xx.xx local_port=443 subdomain=xxx auth_valid_to=2099-12-31 auth_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx sign=xxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxx= ### Logs 2022/04/08 18:41:37 [T] [service.go:425] start check TLS connection... 2022/04/08 18:41:37 [T] [service.go:425] success check TLS connection 2022/04/08 18:41:37 [D] [service.go:425] Accept new mux stream error:tls:client didn't provide a certificate ### Steps to reproduce ./frpc -c xxxxx.cert EOF ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:29:09 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:29:12 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Apr 10, 2022):

Please use latest version v0.41.0. We don't promise compatibility guarantee.

@fatedier commented on GitHub (Apr 10, 2022): Please use latest version v0.41.0. We don't promise compatibility guarantee.

gitea-mirror commented

2026-05-05 13:29:13 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (May 11, 2022):

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 (May 11, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:44:09 -06:00

[PR #2302] [MERGED] bump version #4547

No Branch/Tag specified