[GH-ISSUE #3856] connect to server error: dial tcp 0.0.0.0:7000: connectex: No connection could be made because the target machine actively refused it. #3064

Closed
opened 2026-05-05 13:59:03 -06:00 by gitea-mirror · 7 comments
Owner

Originally created by @wo4wangle on GitHub (Dec 17, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3856

Bug Description

Addr is "117.13.194.95", why connect with 0.0.0.0? what's the issue
"telnet 117.13.194.95 7000" can connect to target in client.

frpc Version

0.53.0

frps Version

0.53.0

System Architecture

windows/amd64

Configurations

client

C:\portableApp\frp_0.53.0_windows_amd64>type frpc.toml
Addr = "117.13.194.95"
serverPort = 7000

proxies
name = "rdp"
type = "tcp"
localIP = "127.0.0.1"
localPort = 3389
remotePort = 6000

server

[root@VM-16-13-opencloudos frp_0.53.0_linux_amd64]# cat frps.toml
bindPort = 7000

Logs

client

C:\portableApp\frp_0.53.0_windows_amd64>frpc.exe -c frpc.toml
2023/12/18 01:50:05 [I] [root.go:141] start frpc service for config file [frpc.toml]
2023/12/18 01:50:05 [I] [service.go:288] try to connect to server...
2023/12/18 01:50:07 [W] [service.go:291] connect to server error: dial tcp 0.0.0.0:7000: connectex: No connection could be made because the target machine actively refused it.
2023/12/18 01:50:07 [I] [service.go:288] try to connect to server...
2023/12/18 01:50:07 [W] [service.go:291] connect to server error: dial tcp 0.0.0.0:7000: operation was canceled
2023/12/18 01:50:07 [I] [root.go:159] frpc service for config file [frpc.toml] stopped
login to the server failed: dial tcp 0.0.0.0:7000: connectex: No connection could be made because the target machine actively refused it.. With loginFailExit enabled, no additional retries will be attempted

server

[root@VM-16-13-opencloudos frp_0.53.0_linux_amd64]# ps -ef |grep -in frp
97:root 2175042 1 0 01:16 ? 00:00:00 ./frps -c frps.toml
[root@VM-16-13-opencloudos frp_0.53.0_linux_amd64]# cat nohup.out
2023/12/18 01:16:39 [I] [root.go:104] frps uses config file: frps.toml
2023/12/18 01:16:39 [I] [service.go:225] frps tcp listen on 0.0.0.0:7000
2023/12/18 01:16:39 [I] [root.go:113] frps started successfully

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 @wo4wangle on GitHub (Dec 17, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3856 ### Bug Description Addr is "117.13.194.95", why connect with 0.0.0.0? what's the issue "telnet 117.13.194.95 7000" can connect to target in client. ### frpc Version 0.53.0 ### frps Version 0.53.0 ### System Architecture windows/amd64 ### Configurations #### client C:\portableApp\frp_0.53.0_windows_amd64>type frpc.toml Addr = "117.13.194.95" serverPort = 7000 [[proxies]] name = "rdp" type = "tcp" localIP = "127.0.0.1" localPort = 3389 remotePort = 6000 #### server [root@VM-16-13-opencloudos frp_0.53.0_linux_amd64]# cat frps.toml bindPort = 7000 ### Logs #### client C:\portableApp\frp_0.53.0_windows_amd64>frpc.exe -c frpc.toml 2023/12/18 01:50:05 [I] [root.go:141] start frpc service for config file [frpc.toml] 2023/12/18 01:50:05 [I] [service.go:288] try to connect to server... 2023/12/18 01:50:07 [W] [service.go:291] connect to server error: dial tcp 0.0.0.0:7000: connectex: No connection could be made because the target machine actively refused it. 2023/12/18 01:50:07 [I] [service.go:288] try to connect to server... 2023/12/18 01:50:07 [W] [service.go:291] connect to server error: dial tcp 0.0.0.0:7000: operation was canceled 2023/12/18 01:50:07 [I] [root.go:159] frpc service for config file [frpc.toml] stopped login to the server failed: dial tcp 0.0.0.0:7000: connectex: No connection could be made because the target machine actively refused it.. With loginFailExit enabled, no additional retries will be attempted #### server [root@VM-16-13-opencloudos frp_0.53.0_linux_amd64]# ps -ef |grep -in frp 97:root 2175042 1 0 01:16 ? 00:00:00 ./frps -c frps.toml [root@VM-16-13-opencloudos frp_0.53.0_linux_amd64]# cat nohup.out 2023/12/18 01:16:39 [I] [root.go:104] frps uses config file: frps.toml 2023/12/18 01:16:39 [I] [service.go:225] frps tcp listen on 0.0.0.0:7000 2023/12/18 01:16:39 [I] [root.go:113] frps started successfully ### 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
Author
Owner

@superzjg commented on GitHub (Dec 18, 2023):

https://github.com/fatedier/frp/blob/dev/conf/frpc_full_example.toml#L9

<!-- gh-comment-id:1859461598 --> @superzjg commented on GitHub (Dec 18, 2023): https://github.com/fatedier/frp/blob/dev/conf/frpc_full_example.toml#L9
Author
Owner

@wo4wangle commented on GitHub (Dec 18, 2023):

https://github.com/fatedier/frp/blob/dev/conf/frpc_full_example.toml#L9

It works, thank you

<!-- gh-comment-id:1861089182 --> @wo4wangle commented on GitHub (Dec 18, 2023): > https://github.com/fatedier/frp/blob/dev/conf/frpc_full_example.toml#L9 It works, thank you
Author
Owner

@vule20 commented on GitHub (Mar 13, 2024):

I'm having the same problem. I've looked at these configurations files but I havent been able resolve it. Please help me if you know it. Basically the frps is hosted on a server with a public IP, which I can only ssh into with a ssh -i ssh_key username@public_ip (exactly like how you would do with AWS). Here's my config file

image

image

<!-- gh-comment-id:1995157072 --> @vule20 commented on GitHub (Mar 13, 2024): I'm having the same problem. I've looked at these configurations files but I havent been able resolve it. Please help me if you know it. Basically the frps is hosted on a server with a public IP, which I can only ssh into with a ssh -i ssh_key username@public_ip (exactly like how you would do with AWS). Here's my config file <img width="304" alt="image" src="https://github.com/fatedier/frp/assets/63137043/ba8d6486-49f6-4e44-bb5e-13166fd7fbef"> ![image](https://github.com/fatedier/frp/assets/63137043/a6e8682b-197b-47a9-81e8-a9bfd18b9eb2)
Author
Owner

@darld commented on GitHub (Apr 26, 2024):

I'm having the same problem. I've looked at these configurations files but I havent been able resolve it. Please help me if you know it. Basically the frps is hosted on a server with a public IP, which I can only ssh into with a ssh -i ssh_key username@public_ip (exactly like how you would do with AWS). Here's my config file

Possible aws block frps?

<!-- gh-comment-id:2078703997 --> @darld commented on GitHub (Apr 26, 2024): > I'm having the same problem. I've looked at these configurations files but I havent been able resolve it. Please help me if you know it. Basically the frps is hosted on a server with a public IP, which I can only ssh into with a ssh -i ssh_key username@public_ip (exactly like how you would do with AWS). Here's my config file Possible aws block frps?
Author
Owner

@vule20 commented on GitHub (Apr 26, 2024):

Hi @darld , I've able to solve the problem. Thanks

<!-- gh-comment-id:2078776903 --> @vule20 commented on GitHub (Apr 26, 2024): Hi @darld , I've able to solve the problem. Thanks
Author
Owner

@darld commented on GitHub (Apr 26, 2024):

Hi @darld , I've able to solve the problem. Thanks

I able to connect now as I need to change the 7000 port from ipv6 to ipv4 in the Aws ec2 instance security. But even connected, but my port of local server still unable to exposed to public internet.

<!-- gh-comment-id:2079037232 --> @darld commented on GitHub (Apr 26, 2024): > Hi @darld , I've able to solve the problem. Thanks I able to connect now as I need to change the 7000 port from ipv6 to ipv4 in the Aws ec2 instance security. But even connected, but my port of local server still unable to exposed to public internet.
Author
Owner

@vule20 commented on GitHub (Apr 26, 2024):

Could you make a screenshot on the log on both the server and the client ?

<!-- gh-comment-id:2079599046 --> @vule20 commented on GitHub (Apr 26, 2024): Could you make a screenshot on the log on both the server and the client ?
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#3064
No description provided.