[GH-ISSUE #4970] No connection could be made because the target machine actively refused it

gitea-mirror commented

2026-05-05 14:29:52 -06:00

Owner

Copy link

Originally created by @peoplelikethesun on GitHub (Sep 6, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4970

Bug Description

I think the parameters of this configuration file really need to be sorted out. The complete configuration update was two years ago. Or because it is a window, the parameters are not recognized in camel case naming

It's really misleading

frpc Version

0.64.0

frps Version

0.64.0

System Architecture

window server 2025

Configurations

Misconfiguration：
[common]
serverAddr = "47.x.x.x"
serverPort = 7000
loginFailExit = false
log.to = "./frpc.log"
log.level = "debug"
log.maxDays = 3
auth.method = "token"
token = "1K02kgan"

[web1]
name = "web1"
type = "tcp"
localIP = "192.168.0.101"
localPort = 8080
remotePort = 3001

Correct configuration:
[common]
server_addr = "47.238.x.x"
server_port = 7000
loginFailExit = false
log.to = "./frpc.log"
log.level = "debug"
log.maxDays = 3
auth.method = "token"
token = "1K02kgan"

[web1]
name = "web1"
type = "tcp"
local_ip = "127.0.0.1"
local_port = 8080
remote_port = 3001

Logs

No connection could be made because the target machine actively refused it.. With loginFailExit enabled, no additional retries will be attempted......

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 @peoplelikethesun on GitHub (Sep 6, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4970 ### Bug Description I think the parameters of this configuration file really need to be sorted out. The complete configuration update was two years ago. Or because it is a window, the parameters are not recognized in camel case naming It's really misleading ### frpc Version 0.64.0 ### frps Version 0.64.0 ### System Architecture window server 2025 ### Configurations Misconfiguration： [common] serverAddr = "47.x.x.x" serverPort = 7000 loginFailExit = false log.to = "./frpc.log" log.level = "debug" log.maxDays = 3 auth.method = "token" token = "1K02kgan" [web1] name = "web1" type = "tcp" localIP = "192.168.0.101" localPort = 8080 remotePort = 3001 Correct configuration: [common] server_addr = "47.238.x.x" server_port = 7000 loginFailExit = false log.to = "./frpc.log" log.level = "debug" log.maxDays = 3 auth.method = "token" token = "1K02kgan" [web1] name = "web1" type = "tcp" local_ip = "127.0.0.1" local_port = 8080 remote_port = 3001 ### Logs No connection could be made because the target machine actively refused it.. With loginFailExit enabled, no additional retries will be attempted...... ### 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 14:29:52 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:29:55 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Sep 6, 2025):

Since you know what is right and what is wrong, you can continue using the correct configuration.

Otherwise, please follow the documentation completely.

@fatedier commented on GitHub (Sep 6, 2025): Since you know what is right and what is wrong, you can continue using the correct configuration. Otherwise, please follow the documentation completely.

gitea-mirror commented

2026-05-05 14:29:56 -06:00

Author

Owner

Copy link

@peoplelikethesun commented on GitHub (Sep 7, 2025):

Since you know what is right and what is wrong, you can continue using the correct configuration.

Otherwise, please follow the documentation completely.

How can I explain the problem of camelCase parameters not being recognized? Did I use it incorrectly without following the documentation? Please advise

@peoplelikethesun commented on GitHub (Sep 7, 2025): > Since you know what is right and what is wrong, you can continue using the correct configuration. > > Otherwise, please follow the documentation completely. How can I explain the problem of camelCase parameters not being recognized? Did I use it incorrectly without following the documentation? Please advise

gitea-mirror commented

2026-05-05 14:29:57 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Sep 8, 2025):

https://github.com/fatedier/frp?tab=readme-ov-file#access-your-computer-in-a-lan-network-via-ssh

I recommend starting by testing the simplest document example, then gradually adding configuration options.

@fatedier commented on GitHub (Sep 8, 2025): https://github.com/fatedier/frp?tab=readme-ov-file#access-your-computer-in-a-lan-network-via-ssh I recommend starting by testing the simplest document example, then gradually adding configuration options.

gitea-mirror commented

2026-05-05 14:29:57 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Sep 23, 2025):

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

@github-actions[bot] commented on GitHub (Sep 23, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

No Branch/Tag specified