mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #3107] connection write timeout #2492
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#2492
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 @pxzhang94 on GitHub (Sep 23, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3107
Bug Description
[W] [service.go:97] login to server failed: connection write timeout
connection write timeout
frpc Version
0.29.1
frps Version
0.29.1
System Architecture
linux/amd64
Configurations
default
Logs
No response
Steps to reproduce
...
Affected area
@Becods commented on GitHub (Sep 23, 2022):
Update your frp, and
@pxzhang94 commented on GitHub (Sep 23, 2022):
I already update my frp to version 0.44.0, and the only information in log file is "2022/09/23 22:32:07 [W] [service.go:128] login to server failed: connection write timeout", and the configuration of frpc.ini is "
[common]
tls_enable = true
server_addr = XXX
server_port = 7000
log_file = ./frpc.log
[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = XXX"
@Becods commented on GitHub (Sep 23, 2022):
Paste your startup command.
@pxzhang94 commented on GitHub (Sep 23, 2022):
Do you mean this "./frpc -c ./frpc.ini"?
@Becods commented on GitHub (Sep 23, 2022):
Check if your server port is open and can be connected properly.
Use tcping.
@github-actions[bot] commented on GitHub (Oct 24, 2022):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
@yudonglin commented on GitHub (Dec 31, 2022):
Ok so @Becods 's suggestion makes me realize what is the problem here... make sure to go to "Security Group" on the server end and switch your 7000 port protocol type from "customize tcp" to "customize udp". This fix my problem.
@kaifeiji commented on GitHub (Jan 28, 2023):
Try changing your bind_port in frps.ini and server_port in frpc.ini to another port number, like 6789. Works for me.
A rough guess: GFW or your ISP monitored some "unusual" network traffic on this port, and then block or restrict the port.
@wk989898 commented on GitHub (Jun 16, 2023):
Try to use kcp protocol
@N-E-E commented on GitHub (Oct 12, 2024):
correct. I fix the problem by using kcp protocol