[GH-ISSUE #3727] Router config conflict when proxies.name same in two frqc instances

gitea-mirror commented

2026-05-05 13:54:57 -06:00

Owner

Originally created by @spring-reader on GitHub (Oct 27, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3727

Bug Description

I run two instances frpc on one pc, and they have their own toml config.
And have one same "proxies.name" in both toml config.

like belows
a.toml

[[proxies]]
name = "name_a"
type = "http"
localIP = "127.0.0.1"
localPort = 18888
customDomains = ["xxxx.com"]

b.toml

[[proxies]]
name = "name_a"
type = "http"
localIP = "127.0.0.1"
localPort = 17777
customDomains = ["ccccc.com"]

Then run two instances in different shell

./frpc -c ./a.toml 
./frpc -c ./b.toml

The client A can run normally, but the client B failed.
The error message like this:

bash[71394]: 2023/10/27 14:33:36 [I] [service.go:299] [5423eb12a9166106] login to server success, get run id [5423eb12a9166106]
bash[71394]: 2023/10/27 14:33:36 [I] [proxy_manager.go:156] [5423eb12a9166106] proxy added: [ssh name_a]
bash[71394]: 2023/10/27 14:33:37 [W] [control.go:171] [5423eb12a9166106] [ssh] start error: proxy [ssh] already exists
bash[71394]: 2023/10/27 14:33:37 [W] [control.go:171] [5423eb12a9166106] [name_a] start error: proxy [name_a] already exists

By the way , this use is feasible in v0.51

frpc Version

0.52.3

frps Version

0.52.3

System Architecture

arm64

Configurations

a.toml

[[proxies]]
name = "name_a"
type = "http"
localIP = "127.0.0.1"
localPort = 18888
customDomains = ["xxxx.com"]

b.toml

[[proxies]]
name = "name_a"
type = "http"
localIP = "127.0.0.1"
localPort = 17777
customDomains = ["ccccc.com"]

Logs

bash[71394]: 2023/10/27 14:33:36 [I] [service.go:299] [5423eb12a9166106] login to server success, get run id [5423eb12a9166106]
bash[71394]: 2023/10/27 14:33:36 [I] [proxy_manager.go:156] [5423eb12a9166106] proxy added: [ssh name_a]
bash[71394]: 2023/10/27 14:33:37 [W] [control.go:171] [5423eb12a9166106] [ssh] start error: proxy [ssh] already exists
bash[71394]: 2023/10/27 14:33:37 [W] [control.go:171] [5423eb12a9166106] [name_a] start error: proxy [name_a] already exists

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 @spring-reader on GitHub (Oct 27, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3727 ### Bug Description I run two instances frpc on one pc, and they have their own toml config. And have one same "proxies.name" in both toml config. like belows a.toml ``` [[proxies]] name = "name_a" type = "http" localIP = "127.0.0.1" localPort = 18888 customDomains = ["xxxx.com"] ``` b.toml ``` [[proxies]] name = "name_a" type = "http" localIP = "127.0.0.1" localPort = 17777 customDomains = ["ccccc.com"] ``` Then run two instances in different shell ``` ./frpc -c ./a.toml ./frpc -c ./b.toml ``` The client A can run normally, but the client B failed. The error message like this: ``` bash[71394]: 2023/10/27 14:33:36 [I] [service.go:299] [5423eb12a9166106] login to server success, get run id [5423eb12a9166106] bash[71394]: 2023/10/27 14:33:36 [I] [proxy_manager.go:156] [5423eb12a9166106] proxy added: [ssh name_a] bash[71394]: 2023/10/27 14:33:37 [W] [control.go:171] [5423eb12a9166106] [ssh] start error: proxy [ssh] already exists bash[71394]: 2023/10/27 14:33:37 [W] [control.go:171] [5423eb12a9166106] [name_a] start error: proxy [name_a] already exists ``` By the way , this use is feasible in v0.51 ### frpc Version 0.52.3 ### frps Version 0.52.3 ### System Architecture arm64 ### Configurations a.toml ``` [[proxies]] name = "name_a" type = "http" localIP = "127.0.0.1" localPort = 18888 customDomains = ["xxxx.com"] ``` b.toml ``` [[proxies]] name = "name_a" type = "http" localIP = "127.0.0.1" localPort = 17777 customDomains = ["ccccc.com"] ``` ### Logs ``` bash[71394]: 2023/10/27 14:33:36 [I] [service.go:299] [5423eb12a9166106] login to server success, get run id [5423eb12a9166106] bash[71394]: 2023/10/27 14:33:36 [I] [proxy_manager.go:156] [5423eb12a9166106] proxy added: [ssh name_a] bash[71394]: 2023/10/27 14:33:37 [W] [control.go:171] [5423eb12a9166106] [ssh] start error: proxy [ssh] already exists bash[71394]: 2023/10/27 14:33:37 [W] [control.go:171] [5423eb12a9166106] [name_a] start error: proxy [name_a] already exists ``` ### 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:54:57 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:55:00 -06:00

Author

Owner

@xqzr commented on GitHub (Oct 28, 2023):

name 从来都是唯一的

@xqzr commented on GitHub (Oct 28, 2023): `name` 从来都是唯一的

gitea-mirror commented

2026-05-05 13:55:01 -06:00

Author

Owner

@superzjg commented on GitHub (Oct 29, 2023):

I guess this is a bug in the old version, which has been fixed in the new release.

@superzjg commented on GitHub (Oct 29, 2023): I guess this is a bug in the old version, which has been fixed in the new release.

gitea-mirror commented

2026-05-05 13:55:02 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 29, 2023):

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