mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #3808] connection write timeout #3030
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#3030
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 @sablea on GitHub (Nov 28, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3808
Bug Description
I have a server and a client.Both of them are ubuntu os.
When I run
./frpc -c ./frpc.ini, there is a connection write timeout error.I am certain that this error is not caused by firewall or port settings, as it worked well before today. And I always can use the ping command to connect to the server IP.
frpc Version
0.48.0
frps Version
0.48.0
System Architecture
ubuntu2004/amd64
Configurations
file frps.ini as follows:
[common] bind_port = 7000file frpc.ini as follows:
`[common]
server_addr = x.x.x.x
server_port = 7000
tls_enable = true
[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 6000`
Logs
The server's logs as follows:
when run
./frps -c ./frps.ini:2023/11/28 17:09:22 [I] [root.go:206] frps uses config file: ./frps.ini
2023/11/28 17:09:22 [I] [service.go:200] frps tcp listen on 0.0.0.0:7000
2023/11/28 17:09:22 [I] [root.go:215] frps started successfully
The client's logs as follows:
when run
./frpc -c ./frpc.ini:2023/11/28 17:11:04 [W] [service.go:134] login to server failed: connection write timeout
connection write timeout
Steps to reproduce
...
Affected area
@sablea commented on GitHub (Dec 4, 2023):
Sovled the problem by updated FRP version to 0.52.