[GH-ISSUE #2460] Windows: A connection attempt failed... #1952

New issue

Closed

opened 2026-05-05 13:15:23 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 13:15:23 -06:00

Owner

Originally created by @oriceon on GitHub (Jun 25, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2460

Hi there. I using Windows 10 on both server and client pc, else with firewall closed...

I started server with config:

[common]
bind_port = 7000

frps.exe -c frps.ini
2021/06/25 11:36:53 [I] [root.go:200] frps uses config file: frps.ini
2021/06/25 11:36:53 [I] [service.go:192] frps tcp listen on 0.0.0.0:7000
2021/06/25 11:36:53 [I] [root.go:209] frps started successfully

Then on client pc i have:

[common]
server_addr = server public ip....
server_port = 7000
dns_server = 8.8.8.8
log_file = frpc.log

[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 6000

And i receive

frpc.exe -c frpc.ini
dial tcp server public ip....:7000: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Where i`m wrong and why connection attempt failed ?

Thanks.

Originally created by @oriceon on GitHub (Jun 25, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2460 Hi there. I using Windows 10 on both server and client pc, else with firewall closed... I started server with config: ``` [common] bind_port = 7000 ``` ``` frps.exe -c frps.ini 2021/06/25 11:36:53 [I] [root.go:200] frps uses config file: frps.ini 2021/06/25 11:36:53 [I] [service.go:192] frps tcp listen on 0.0.0.0:7000 2021/06/25 11:36:53 [I] [root.go:209] frps started successfully ``` Then on client pc i have: ``` [common] server_addr = server public ip.... server_port = 7000 dns_server = 8.8.8.8 log_file = frpc.log [ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 6000 ``` And i receive ``` frpc.exe -c frpc.ini dial tcp server public ip....:7000: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ``` Where i`m wrong and why connection attempt failed ? Thanks.

gitea-mirror

2026-05-05 13:15:23 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:15:26 -06:00

Author

Owner

@fatedier commented on GitHub (Jul 8, 2021):

You should first make sure you can visit {server_ip}:7000 from your pc.

@fatedier commented on GitHub (Jul 8, 2021): You should first make sure you can visit {server_ip}:7000 from your pc.

gitea-mirror commented

2026-05-05 13:15:26 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 8, 2021):

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

@github-actions[bot] commented on GitHub (Aug 8, 2021): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 13:15:27 -06:00

Author

Owner

@smac89 commented on GitHub (Jul 16, 2024):

Check that your server doesn't have a firewall which is blocking connections. For me, the issue was the use of ufw and not allowing access to port 7000.

@smac89 commented on GitHub (Jul 16, 2024): Check that your server doesn't have a firewall which is blocking connections. For me, the issue was the use of ufw and not allowing access to port 7000.