[GH-ISSUE #2732] login to server failed

gitea-mirror commented

2026-05-05 13:24:18 -06:00

Owner

Copy link

Originally created by @Justinmaggie on GitHub (Jan 3, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2732

Bug Description

login to server failed: dial tcp xxxxxxx: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.
dial tcp xxxxxxx: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

frpc Version

3.71

frps Version

3.71

System Architecture

Windows amd64

Configurations

frps
[common] bind_addr = 0.0.0.0 bind_port = 7000 dashboard_user = xxxxx #监控的用户名 dashboard_pwd = xxxxxx #监控的密码 dashboard_port = 7500

frpc

[common] server_addr = xx.xx.xx.xx #你的公网机器的ip地址 server_port = 7000 [ssh] type = tcp local_ip = 127.0.0.1 local_port = 3389 remote_port = 6000

Logs

No response

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 @Justinmaggie on GitHub (Jan 3, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2732 ### Bug Description login to server failed: dial tcp xxxxxxx: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. dial tcp xxxxxxx: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 ### frpc Version 3.71 ### frps Version 3.71 ### System Architecture Windows amd64 ### Configurations frps [common] bind_addr = 0.0.0.0 bind_port = 7000 dashboard_user = xxxxx #监控的用户名 dashboard_pwd = xxxxxx #监控的密码 dashboard_port = 7500 frpc [common] server_addr = xx.xx.xx.xx #你的公网机器的ip地址 server_port = 7000 [ssh] type = tcp local_ip = 127.0.0.1 local_port = 3389 remote_port = 6000 ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:24:18 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:24:21 -06:00

Author

Owner

Copy link

@Becods commented on GitHub (Jan 5, 2022):

Try to check if the port is open (this type of problem is particularly common with cloud servers).

@Becods commented on GitHub (Jan 5, 2022): Try to check if the port is open (this type of problem is particularly common with cloud servers).

gitea-mirror commented

2026-05-05 13:24:22 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Feb 5, 2022):

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 (Feb 5, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:43:39 -06:00

[PR #2184] [MERGED] Add user remote address info log #4519

No Branch/Tag specified