[GH-ISSUE #2843] login to server failed: dial tcp {IP:PORT}: i/o timeout #2274

Closed
opened 2026-05-05 13:27:55 -06:00 by gitea-mirror · 19 comments
Owner

Originally created by @rootGH on GitHub (Mar 15, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2843

Bug Description

VPS IP:PORT has been switched off already

frpc Version

0.40.0

frps Version

0.40.0

System Architecture

windows/amd64

Configurations

Client
[common]
server_addr = {IP}
server_port = 7000

[RDP]
type = tcp
local_ip = 127.0.0.1
local_port = 3389
remote_port = 7001

Server
[common]
bind_port = 7000

Logs

D:\frp_0.40.0_windows_amd64>frpc.exe
2022/03/15 09:25:40 [W] [service.go:105] login to server failed: dial tcp {IP:PORT}: i/o timeout
dial tcp {IP:PORT}: i/o timeout

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 @rootGH on GitHub (Mar 15, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2843 ### Bug Description VPS IP:PORT has been switched off already ### frpc Version 0.40.0 ### frps Version 0.40.0 ### System Architecture windows/amd64 ### Configurations Client [common] server_addr = {IP} server_port = 7000 [RDP] type = tcp local_ip = 127.0.0.1 local_port = 3389 remote_port = 7001 Server [common] bind_port = 7000 ### Logs D:\frp_0.40.0_windows_amd64>frpc.exe 2022/03/15 09:25:40 [W] [service.go:105] login to server failed: dial tcp {IP:PORT}: i/o timeout dial tcp {IP:PORT}: i/o timeout ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:27:55 -06:00
Author
Owner

@Qpp0 commented on GitHub (Mar 16, 2022):

same here

<!-- gh-comment-id:1068795157 --> @Qpp0 commented on GitHub (Mar 16, 2022): same here
Author
Owner

@Becods commented on GitHub (Mar 16, 2022):

post the log of frps, pls

<!-- gh-comment-id:1068924179 --> @Becods commented on GitHub (Mar 16, 2022): post the log of frps, pls
Author
Owner

@rootGH commented on GitHub (Mar 16, 2022):

no logs, only two lines
D:\frp_0.40.0_windows_amd64>frpc.exe
2022/03/15 09:25:40 [W] [service.go:105] login to server failed: dial tcp {IP:PORT}: i/o timeout
dial tcp {IP:PORT}: i/o timeout

<!-- gh-comment-id:1068927561 --> @rootGH commented on GitHub (Mar 16, 2022): > no logs, only two lines D:\frp_0.40.0_windows_amd64>frpc.exe 2022/03/15 09:25:40 [W] [service.go:105] login to server failed: dial tcp {IP:PORT}: i/o timeout dial tcp {IP:PORT}: i/o timeout
Author
Owner

@rootGH commented on GitHub (Mar 16, 2022):

post the log of frps, pls

no logs, only two lines
D:\frp_0.40.0_windows_amd64>frpc.exe
2022/03/15 09:25:40 [W] [service.go:105] login to server failed: dial tcp {IP:PORT}: i/o timeout
dial tcp {IP:PORT}: i/o timeout

<!-- gh-comment-id:1068928250 --> @rootGH commented on GitHub (Mar 16, 2022): > post the log of frps, pls no logs, only two lines D:\frp_0.40.0_windows_amd64>frpc.exe 2022/03/15 09:25:40 [W] [service.go:105] login to server failed: dial tcp {IP:PORT}: i/o timeout dial tcp {IP:PORT}: i/o timeout
Author
Owner

@Pil0tXia commented on GitHub (Mar 17, 2022):

me too here

<!-- gh-comment-id:1070816960 --> @Pil0tXia commented on GitHub (Mar 17, 2022): me too here
Author
Owner

@Becods commented on GitHub (Mar 20, 2022):

Use tcping to test if the port is open properly

<!-- gh-comment-id:1073159536 --> @Becods commented on GitHub (Mar 20, 2022): Use tcping to test if the port is open properly
Author
Owner

@scmplie commented on GitHub (Mar 21, 2022):

Have you found a solution

<!-- gh-comment-id:1073456240 --> @scmplie commented on GitHub (Mar 21, 2022): Have you found a solution
Author
Owner

@Pil0tXia commented on GitHub (Mar 21, 2022):

solved, this problem mostly happens in cloud servers, the source port range should be *

<!-- gh-comment-id:1073457765 --> @Pil0tXia commented on GitHub (Mar 21, 2022): solved, this problem mostly happens in cloud servers, the source port range should be *
Author
Owner

@scmplie commented on GitHub (Mar 21, 2022):

solved, this problem mostly happens in cloud servers, the source port range should be *

how to do it, buddy
is it means that i need to open all the tcp+udp port

<!-- gh-comment-id:1073470734 --> @scmplie commented on GitHub (Mar 21, 2022): > solved, this problem mostly happens in cloud servers, the source port range should be * how to do it, buddy is it means that i need to open all the tcp+udp port
Author
Owner

@scmplie commented on GitHub (Mar 21, 2022):

solved, this problem mostly happens in cloud servers, the source port range should be *

我也搞好了,我用内网那个ping外网的IP发现ping不通,然后发现路由器的网络控制把我那个frp服务器给限时了,改了一下就好了。

<!-- gh-comment-id:1073529883 --> @scmplie commented on GitHub (Mar 21, 2022): > solved, this problem mostly happens in cloud servers, the source port range should be * 我也搞好了,我用内网那个ping外网的IP发现ping不通,然后发现路由器的网络控制把我那个frp服务器给限时了,改了一下就好了。
Author
Owner

@fantasyEthan commented on GitHub (Mar 31, 2022):

I encountered the same problem. I use Aliyun ECS + computer in edu domain. I followed the instructions and set the firewalls of ecs. How did you solve these problems?

<!-- gh-comment-id:1084457094 --> @fantasyEthan commented on GitHub (Mar 31, 2022): I encountered the same problem. I use Aliyun ECS + computer in edu domain. I followed the instructions and set the firewalls of ecs. How did you solve these problems?
Author
Owner

@marcuswang6 commented on GitHub (Apr 1, 2022):

腾讯云 同样有这个问题 设置了防火墙也没有用。

<!-- gh-comment-id:1086049702 --> @marcuswang6 commented on GitHub (Apr 1, 2022): 腾讯云 同样有这个问题 设置了防火墙也没有用。
Author
Owner

@ArthurWang0829 commented on GitHub (Apr 1, 2022):

请问下这个是怎么改?阿里云ping起来回报正常,是端口不对?

<!-- gh-comment-id:1086083725 --> @ArthurWang0829 commented on GitHub (Apr 1, 2022): > 请问下这个是怎么改?阿里云ping起来回报正常,是端口不对?
Author
Owner

@github-actions[bot] commented on GitHub (May 2, 2022):

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

<!-- gh-comment-id:1114382861 --> @github-actions[bot] commented on GitHub (May 2, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Author
Owner

@CaesarHolland commented on GitHub (Jan 9, 2023):

My cloud server is Tencent cloud, I solved the problem by add a firewall rule (open port 7000 of tcp) on cloud server

<!-- gh-comment-id:1375203439 --> @CaesarHolland commented on GitHub (Jan 9, 2023): My cloud server is Tencent cloud, I solved the problem by add a firewall rule (open port 7000 of tcp) on cloud server
Author
Owner

@liugeng518 commented on GitHub (Feb 11, 2023):

怎么解决的?

<!-- gh-comment-id:1426597159 --> @liugeng518 commented on GitHub (Feb 11, 2023): 怎么解决的?
Author
Owner

@wshidaijingshen commented on GitHub (Mar 25, 2023):

怎么解决的?

我是客户端的 公网ip 地址写错了,好好检查下
I solved this by correcting the server_addr in frpc.ini .
Then problems gone.

<!-- gh-comment-id:1483872527 --> @wshidaijingshen commented on GitHub (Mar 25, 2023): > 怎么解决的? 我是客户端的 公网ip 地址写错了,好好检查下 I solved this by correcting the server_addr in frpc.ini . Then problems gone.
Author
Owner

@52Lau commented on GitHub (Apr 17, 2023):

image
如楼上所说 放开 *

<!-- gh-comment-id:1510639894 --> @52Lau commented on GitHub (Apr 17, 2023): ![image](https://user-images.githubusercontent.com/37538641/232370717-4aa9cbb0-49ec-4b89-a0e2-c13cac8d961b.png) 如楼上所说 放开 *
Author
Owner

@luccachiang commented on GitHub (Jun 8, 2023):

It turns out that the port 6000 and 7000 should both be opened (I referred to one guide with these two ports). In my case, this solves my problem.

<!-- gh-comment-id:1581976821 --> @luccachiang commented on GitHub (Jun 8, 2023): It turns out that the port 6000 and 7000 should both be opened (I referred to one guide with these two ports). In my case, this solves my problem.
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#2274
No description provided.