mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #3058] login to server failed: dial tcp 182.243.33.96:7000: i/o timeout #2450
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#2450
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 @coolxy on GitHub (Aug 12, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3058
Bug Description
I have two frpc client,one is good,another is error of :
login to server failed: dial tcp 182.243.33.96:7000: i/o timeout
why?
frpc Version
0.44
frps Version
0.44
System Architecture
linux/amd64
Configurations
I have two frpc client,one is good,another is error of :
login to server failed: dial tcp 182.243.33.96:7000: i/o timeout
why?
Logs
2022/08/12 12:24:16 [W] [service.go:128] login to server failed: dial tcp 182.243.33.96:7000: i/o timeout
dial tcp 182.243.33.96:7000: i/o timeout
Steps to reproduce
...
Affected area
@coolxy commented on GitHub (Aug 12, 2022):
Aug 12 12:21:13 qqserver systemd[1]: Started fraps service.
Aug 12 12:21:23 qqserver frpc[1314717]: 2022/08/12 12:21:23 [W] [service.go:128] login to server failed: dial tcp 182.243.33.96:7000: i/o timeout
Aug 12 12:21:23 qqserver frpc[1314717]: dial tcp 182.243.33.96:7000: i/o timeout
Aug 12 12:21:23 qqserver systemd[1]: frpc.service: Main process exited, code=exited, status=1/FAILURE
Aug 12 12:21:23 qqserver systemd[1]: frpc.service: Failed with result 'exit-code'.
@Becods commented on GitHub (Aug 12, 2022):
Open your port.
@github-actions[bot] commented on GitHub (Sep 12, 2022):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.