[GH-ISSUE #3093] It works with TLS correctly, but fails when adding kcp. #2477

Closed
opened 2026-05-05 13:35:34 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @guorouda on GitHub (Sep 8, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3093

Bug Description

It works with TLS correctly, but fails when adding kcp.

Only output this message show as below in my terminal.
2022/09/08 16:33:11 [W] [service.go:128] login to server failed: connection write timeout connection write timeout
Does my network reset the connection ? Or It can't work with tls and kcp.

frpc Version

0.44.0

frps Version

0.44.0

System Architecture

Server: linux/amd64, Client: windows/amd64

Configurations

Client
[common]
server_addr = X.X.X.X
server_port = 7000
protocol = kcp
tls_enable = true
tls_cert_file = D:\dev\frp_0.44.1_windows_amd64\client.crt
tls_key_file = D:\dev\frp_0.44.1_windows_amd64\client.key
tls_trusted_ca_file = D:\dev\frp_0.44.1_windows_amd64\ca.crt

Server:
[common]
bind_port = 7000
kcp_bind_port = 7000
tls_cert_file = /home/ubuntu/server.crt
tls_key_file = /home/ubuntu/server.key
tls_trusted_ca_file = /home/ubuntu/ca.crt

Logs

No response

Steps to reproduce

...

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @guorouda on GitHub (Sep 8, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3093 ### Bug Description It works with TLS correctly, but fails when adding kcp. Only output this message show as below in my terminal. `2022/09/08 16:33:11 [W] [service.go:128] login to server failed: connection write timeout connection write timeout` Does my network reset the connection ? Or It can't work with tls and kcp. ### frpc Version 0.44.0 ### frps Version 0.44.0 ### System Architecture Server: linux/amd64, Client: windows/amd64 ### Configurations Client [common] server_addr = X.X.X.X server_port = 7000 protocol = kcp tls_enable = true tls_cert_file = D:\dev\frp_0.44.1_windows_amd64\client.crt tls_key_file = D:\dev\frp_0.44.1_windows_amd64\client.key tls_trusted_ca_file = D:\dev\frp_0.44.1_windows_amd64\ca.crt Server: [common] bind_port = 7000 kcp_bind_port = 7000 tls_cert_file = /home/ubuntu/server.crt tls_key_file = /home/ubuntu/server.key tls_trusted_ca_file = /home/ubuntu/ca.crt ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:35:34 -06:00
Author
Owner

@fatedier commented on GitHub (Sep 9, 2022):

You can deploy both frpc and frps in the same local machine to test if it's normal.

Then you can confirm if the configuration is correct avoiding network problems.

<!-- gh-comment-id:1241429089 --> @fatedier commented on GitHub (Sep 9, 2022): You can deploy both frpc and frps in the same local machine to test if it's normal. Then you can confirm if the configuration is correct avoiding network problems.
Author
Owner

@guorouda commented on GitHub (Sep 9, 2022):

This approach is great. Thanks.

And it's my honor to get reply from THE AUTHOR himslef.

<!-- gh-comment-id:1241471568 --> @guorouda commented on GitHub (Sep 9, 2022): This approach is great. Thanks. And it's my honor to get reply from THE AUTHOR himslef.
Author
Owner

@github-actions[bot] commented on GitHub (Oct 10, 2022):

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

<!-- gh-comment-id:1272669402 --> @github-actions[bot] commented on GitHub (Oct 10, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
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: github-starred/frp#2477
No description provided.