mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #3093] It works with TLS correctly, but fails when adding kcp. #2477
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#2477
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 timeoutDoes 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
@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.
@guorouda commented on GitHub (Sep 9, 2022):
This approach is great. Thanks.
And it's my honor to get reply from THE AUTHOR himslef.
@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.