github-starred/frp
2
0
Fork 0
mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00
Code Issues 40 Projects Packages Wiki Activity Actions 1

[GH-ISSUE #2807] Fails to connect multiple clients #2244

New issue
Closed
opened 2026-05-05 13:26:36 -06:00 by gitea-mirror · 6 comments
gitea-mirror commented 2026-05-05 13:26:36 -06:00
Owner
Copy link

Originally created by @JimBeam2019 on GitHub (Feb 18, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2807

Bug Description

Hi there, I'm having a problem exposing two different localhost clients to the internet with HTTPS protocol through a cloud server.

For example, I have a cloud server running frps (see the frps.ini below) and trying to expose a localhost client A and client B (the configurations are frpc.ini A and frpc.ini B), which are from device A and B respectively. My goal is that if the user type https://www.mydomain.com/test01 in a browser, the cloud server would connect them to client A and vice versa, if it is https://www.mydomain.com/test02, it should link to client B.

With the frps up and running, when I started client A first, the connection with it went through, but then I tried client B and it return the error message [W] [control.go:447] [3d336c85a6d62de2] new proxy [web_test_B] error: router config conflict. The result went the same with the similar error message as I started client B first and then client A second.

I was wondering if it is a bug, so could you try the configurations above to see if it is indeed a bug there. Please any advice will be greatly appreciated. Cheers.

frpc Version

0.39.1

frps Version

0.39.1

System Architecture

linux/arm64

Configurations

frps.ini

[common]
bind_port = 7000
vhost_http_port = 80
vhost_https_port = 443
max_pool_count = 10
dashboard_port = 7500
dashboard_user = admin
dashboard_pwd = admin

frpc.ini A in device A

[common]
server_addr = <SERVER_IP_ADDRESS>
server_port = 7000

[web_test_A]
type = https
local_port = 443
custom_domains = www.mydomain.com
locations = /test01

frpc.ini B in device B

[common]
server_addr = <SERVER_IP_ADDRESS>
server_port = 7000

[web_test_B]
type = https
local_port = 443
custom_domains = www.mydomain.com
locations = /test02

Logs

frps

2022/02/18 16:37:30 [I] [root.go:200] frps uses config file: ./frps.ini
2022/02/18 16:37:30 [I] [service.go:193] frps tcp listen on 0.0.0.0:7000
2022/02/18 16:37:30 [I] [service.go:236] http service listen on 0.0.0.0:80
2022/02/18 16:37:30 [I] [service.go:251] https service listen on 0.0.0.0:443
2022/02/18 16:37:30 [I] [service.go:292] Dashboard listen on 0.0.0.0:7500
2022/02/18 16:37:30 [I] [root.go:209] frps started successfully
2022/02/18 16:37:38 [I] [service.go:449] [69e341f9404978cc] client login info: ip [*.*.*.*:46891] version [0.39.1] hostname [] os [linux] arch [arm64]                                                                           
2022/02/18 16:37:38 [I] [https.go:51] [69e341f9404978cc] [web_test_A] https proxy listen for host [www.mydomain.com]                                                                                                        
2022/02/18 16:37:38 [I] [control.go:451] [69e341f9404978cc] new proxy [web_test_A] success
2022/02/18 16:37:52 [I] [proxy.go:179] [69e341f9404978cc] [web_test_A] get a user connection [*.*.*.*:46907]                                                                                                             
2022/02/18 16:37:57 [I] [proxy.go:179] [69e341f9404978cc] [web_test_A] get a user connection [*.*.*.*:46910]                                                                                                             
2022/02/18 16:37:57 [I] [proxy.go:179] [69e341f9404978cc] [web_test_A] get a user connection [*.*.*.*:46911]                                                                                                             
2022/02/18 16:38:06 [I] [proxy.go:179] [69e341f9404978cc] [web_test_A] get a user connection [*.*.*.*:46924]                                                                                                             
2022/02/18 16:38:07 [I] [proxy.go:179] [69e341f9404978cc] [web_test_A] get a user connection [*.*.*.*:46926]                                                                                                             
2022/02/18 16:38:44 [I] [dashboard_api.go:70] Http request: [/api/serverinfo]
2022/02/18 16:38:44 [I] [dashboard_api.go:63] Http response [/api/serverinfo]: code [200]
2022/02/18 16:42:03 [I] [service.go:449] [3d336c85a6d62de2] client login info: ip [*.*.*.*:47723] version [0.39.1] hostname [] os [linux] arch [arm64]                                                                           
2022/02/18 16:42:03 [I] [proxy.go:88] [3d336c85a6d62de2] [web_test_B] proxy closing
2022/02/18 16:42:03 [W] [control.go:447] [3d336c85a6d62de2] new proxy [web_test_B] error: router config conflict

frpc.ini A in device A

2022/02/18 16:37:38 [I] [service.go:327] [69e341f9404978cc] login to server success, get run id [69e341f9404978cc], server udp port [0]                                                                                                 
2022/02/18 16:37:38 [I] [proxy_manager.go:144] [69e341f9404978cc] proxy added: [web_test_A]
2022/02/18 16:37:38 [I] [control.go:181] [69e341f9404978cc] [web_test_A] start proxy success
...

frpc.ini B in device B

2022/02/18 16:42:03 [I] [service.go:327] [d4adff90b8cfd91d] login to server success, get run id [d4adff90b8cfd91d], server udp port [0]                                                                                                 
2022/02/18 16:42:03 [I] [proxy_manager.go:144] [d4adff90b8cfd91d] proxy added: [web_test_B]
2022/02/18 16:42:03 [W] [control.go:179] [d4adff90b8cfd91d] [web_test_B] start error: router config conflict

Steps to reproduce

  1. Run the frps in a cloud under the server domain.
  2. Run the frpc with a similar config like the frpc A in a PC, using the server domain from step 1.
  3. Run the frpc with a similar config like the frpc B in a different PC, using the server domain from step 1.
    ...

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @JimBeam2019 on GitHub (Feb 18, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2807 ### Bug Description Hi there, I'm having a problem exposing two different localhost clients to the internet with HTTPS protocol through a cloud server. For example, I have a _cloud server_ running frps (see the **frps.ini** below) and trying to expose a localhost _**client A**_ and _**client B**_ (the configurations are **frpc.ini A** and **frpc.ini B**), which are from device A and B respectively. My goal is that if the user type `https://www.mydomain.com/test01` in a browser, the cloud server would connect them to _**client A**_ and vice versa, if it is `https://www.mydomain.com/test02`, it should link to _**client B**_. With the frps up and running, when I started _**client A**_ first, the connection with it went through, but then I tried _**client B**_ and it return the error message `[W] [control.go:447] [3d336c85a6d62de2] new proxy [web_test_B] error: router config conflict`. The result went the same with the similar error message as I started _**client B**_ first and then _**client A**_ second. I was wondering if it is a bug, so could you try the configurations above to see if it is indeed a bug there. Please any advice will be greatly appreciated. Cheers. ### frpc Version 0.39.1 ### frps Version 0.39.1 ### System Architecture linux/arm64 ### Configurations **frps.ini** ```ini [common] bind_port = 7000 vhost_http_port = 80 vhost_https_port = 443 max_pool_count = 10 dashboard_port = 7500 dashboard_user = admin dashboard_pwd = admin ``` **frpc.ini A** in device A ```ini [common] server_addr = <SERVER_IP_ADDRESS> server_port = 7000 [web_test_A] type = https local_port = 443 custom_domains = www.mydomain.com locations = /test01 ``` **frpc.ini B** in device B ```ini [common] server_addr = <SERVER_IP_ADDRESS> server_port = 7000 [web_test_B] type = https local_port = 443 custom_domains = www.mydomain.com locations = /test02 ``` ### Logs **frps** ```sh 2022/02/18 16:37:30 [I] [root.go:200] frps uses config file: ./frps.ini 2022/02/18 16:37:30 [I] [service.go:193] frps tcp listen on 0.0.0.0:7000 2022/02/18 16:37:30 [I] [service.go:236] http service listen on 0.0.0.0:80 2022/02/18 16:37:30 [I] [service.go:251] https service listen on 0.0.0.0:443 2022/02/18 16:37:30 [I] [service.go:292] Dashboard listen on 0.0.0.0:7500 2022/02/18 16:37:30 [I] [root.go:209] frps started successfully 2022/02/18 16:37:38 [I] [service.go:449] [69e341f9404978cc] client login info: ip [*.*.*.*:46891] version [0.39.1] hostname [] os [linux] arch [arm64] 2022/02/18 16:37:38 [I] [https.go:51] [69e341f9404978cc] [web_test_A] https proxy listen for host [www.mydomain.com] 2022/02/18 16:37:38 [I] [control.go:451] [69e341f9404978cc] new proxy [web_test_A] success 2022/02/18 16:37:52 [I] [proxy.go:179] [69e341f9404978cc] [web_test_A] get a user connection [*.*.*.*:46907] 2022/02/18 16:37:57 [I] [proxy.go:179] [69e341f9404978cc] [web_test_A] get a user connection [*.*.*.*:46910] 2022/02/18 16:37:57 [I] [proxy.go:179] [69e341f9404978cc] [web_test_A] get a user connection [*.*.*.*:46911] 2022/02/18 16:38:06 [I] [proxy.go:179] [69e341f9404978cc] [web_test_A] get a user connection [*.*.*.*:46924] 2022/02/18 16:38:07 [I] [proxy.go:179] [69e341f9404978cc] [web_test_A] get a user connection [*.*.*.*:46926] 2022/02/18 16:38:44 [I] [dashboard_api.go:70] Http request: [/api/serverinfo] 2022/02/18 16:38:44 [I] [dashboard_api.go:63] Http response [/api/serverinfo]: code [200] 2022/02/18 16:42:03 [I] [service.go:449] [3d336c85a6d62de2] client login info: ip [*.*.*.*:47723] version [0.39.1] hostname [] os [linux] arch [arm64] 2022/02/18 16:42:03 [I] [proxy.go:88] [3d336c85a6d62de2] [web_test_B] proxy closing 2022/02/18 16:42:03 [W] [control.go:447] [3d336c85a6d62de2] new proxy [web_test_B] error: router config conflict ``` **frpc.ini A** in device A ```sh 2022/02/18 16:37:38 [I] [service.go:327] [69e341f9404978cc] login to server success, get run id [69e341f9404978cc], server udp port [0] 2022/02/18 16:37:38 [I] [proxy_manager.go:144] [69e341f9404978cc] proxy added: [web_test_A] 2022/02/18 16:37:38 [I] [control.go:181] [69e341f9404978cc] [web_test_A] start proxy success ... ``` **frpc.ini B** in device B ```sh 2022/02/18 16:42:03 [I] [service.go:327] [d4adff90b8cfd91d] login to server success, get run id [d4adff90b8cfd91d], server udp port [0] 2022/02/18 16:42:03 [I] [proxy_manager.go:144] [d4adff90b8cfd91d] proxy added: [web_test_B] 2022/02/18 16:42:03 [W] [control.go:179] [d4adff90b8cfd91d] [web_test_B] start error: router config conflict ``` ### Steps to reproduce 1. Run the frps in a cloud under the server domain. 2. Run the frpc with a similar config like the frpc A in a PC, using the server domain from step 1. 3. Run the frpc with a similar config like the frpc B in a different PC, using the server domain from step 1. ... ### Affected area - [X] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [X] Developer Infrastructure - [X] Client Plugin - [X] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:26:36 -06:00
gitea-mirror commented 2026-05-05 13:26:40 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Feb 18, 2022):

locations is not supported for https. It only supports http.

For https, frps will not decode your request data, it just forward the connection to your client.

<!-- gh-comment-id:1044271900 --> @fatedier commented on GitHub (Feb 18, 2022): `locations` is not supported for `https`. It only supports `http`. For `https`, frps will not decode your request data, it just forward the connection to your client.
gitea-mirror commented 2026-05-05 13:26:41 -06:00
Author
Owner
Copy link

@ghost commented on GitHub (Feb 18, 2022):

locations is not supported for https. It only supports http.

For https, frps will not decode your request data, it just forward the connection to your client.

so you are saying that if we have 2 HTTPS clients (SSL certificates on client side, not on server side), FRP library is useless? There is no way to connect?
did I get it right ?

<!-- gh-comment-id:1044392411 --> @ghost commented on GitHub (Feb 18, 2022): > `locations` is not supported for `https`. It only supports `http`. > > For `https`, frps will not decode your request data, it just forward the connection to your client. so you are saying that if we have 2 HTTPS clients (SSL certificates on client side, not on server side), FRP library is useless? There is no way to connect? did I get it right ?
gitea-mirror commented 2026-05-05 13:26:42 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Feb 19, 2022):

You can use different domains for each HTTPS service.

<!-- gh-comment-id:1045970083 --> @fatedier commented on GitHub (Feb 19, 2022): You can use different domains for each HTTPS service.
gitea-mirror commented 2026-05-05 13:26:42 -06:00
Author
Owner
Copy link

@ghost commented on GitHub (Feb 19, 2022):

You can use different domains for each HTTPS service.

do you mean, use different subdomain for each HTTPS service ?

<!-- gh-comment-id:1045973203 --> @ghost commented on GitHub (Feb 19, 2022): > You can use different domains for each HTTPS service. do you mean, use different subdomain for each HTTPS service ?
gitea-mirror commented 2026-05-05 13:26:43 -06:00
Author
Owner
Copy link

@ghost commented on GitHub (Mar 12, 2022):

Hey @JimBeam2019 I figured out how to do this, here is my config:

frps.ini:

[common]
bind_port = 7000
vhost_http_port = 80
vhost_https_port = 443
dashboard_port = 7001
dashboard_user = username
dashboard_pwd = supersecurepassword

frpc.ini (1st client, in my case it's the main domain):

[common]
server_addr = xxx.xxx.xxx.xxx
server_port = 7000

[http]
type = http
local_ip = 0.0.0.0
local_port = 80
custom_domains = example.com

[https]
type = https
local_ip = 0.0.0.0
local_port = 443
custom_domains = example.com

frpc.ini (2nd client, in my case it's a sub-domain):

[common]
server_addr = xxx.xxx.xxx.xxx
server_port = 7000

[http-sub]
type = http
local_ip = 0.0.0.0
local_port = 80
custom_domains = sub.example.com

[https-sub]
type = https
local_ip = 0.0.0.0
local_port = 443
custom_domains = sub.example.com

Hope this helps

<!-- gh-comment-id:1065964641 --> @ghost commented on GitHub (Mar 12, 2022): Hey @JimBeam2019 I figured out how to do this, here is my config: **frps.ini:** `[common]` `bind_port = 7000` `vhost_http_port = 80` `vhost_https_port = 443` `dashboard_port = 7001` `dashboard_user = username` `dashboard_pwd = supersecurepassword` **frpc.ini (1st client, in my case it's the main domain):** `[common]` `server_addr = xxx.xxx.xxx.xxx` `server_port = 7000` `[http]` `type = http` `local_ip = 0.0.0.0` `local_port = 80` `custom_domains = example.com` `[https]` `type = https` `local_ip = 0.0.0.0` `local_port = 443` `custom_domains = example.com` **frpc.ini (2nd client, in my case it's a sub-domain):** `[common]` `server_addr = xxx.xxx.xxx.xxx` `server_port = 7000` `[http-sub]` `type = http` `local_ip = 0.0.0.0` `local_port = 80` `custom_domains = sub.example.com` `[https-sub]` `type = https` `local_ip = 0.0.0.0` `local_port = 443` `custom_domains = sub.example.com` Hope this helps
gitea-mirror commented 2026-05-05 13:26:44 -06:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Apr 12, 2022):

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

<!-- gh-comment-id:1095737803 --> @github-actions[bot] commented on GitHub (Apr 12, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
new
master
copilot/review-pull-request-5198
v0.68.1
v0.68.0
v0.67.0
v0.66.0
v0.65.0
v0.64.0
v0.63.0
v0.62.1
v0.62.0
v0.61.2
v0.61.1
v0.61.0
v0.60.0
v0.59.0
v0.58.1
v0.58.0
v0.57.0
v0.56.0
v0.55.1
v0.55.0
v0.54.0
v0.53.2
v0.53.1
v0.53.0
v0.52.3
v0.52.2
v0.52.1
v0.52.0
v0.51.3
v0.51.2
v0.51.1
v0.51.0
v0.50.0
v0.49.0
v0.48.0
v0.47.0
v0.46.1
v0.46.0
v0.45.0
v0.44.0
v0.43.0
v0.42.0
v0.41.0
v0.40.0
v0.39.1
v0.39.0
v0.38.0
v0.37.1
v0.37.0
v0.36.2
v0.36.1
v0.36.0
v0.35.1
v0.35.0
v0.34.3
v0.34.2
v0.34.1
v0.34.0
v0.33.0
v0.32.1
v0.32.0
v0.31.2
v0.31.1
v0.31.0
v0.30.0
v0.29.1
v0.29.0
v0.28.2
v0.28.1
v0.28.0
v0.27.1
v0.27.0
v0.26.0
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.1
v0.24.0
v0.23.3
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.0
v0.19.1
v0.19.0
v0.18.0
v0.17.0
v0.16.1
v0.16.0
v0.15.1
v0.15.0
v0.14.1
v0.14.0
v0.13.0
v0.12.0
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.1
v0.8.0
v0.7.0
v0.6.0
v0.5.0
v0.3.0
v0.2.0
v0.1.0
Labels
Clear labels   
In Progress

   
WIP

   
WaitingForInfo

   
bug

   
doc

   
duplicate

   
easy

   
enhancement

   
future

   
help wanted

   
invalid

   
lifecycle/stale

   
need-issue-template

   
need-usage-help

   
no plan

   
proposal

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
todo
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#2244
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?