frps 多个_同时穿透多个内网web服务，提示冲突

What version of frp are you using (./frpc -v or ./frps -v)?

0.27.1

What operating system and processor architecture are you using (go env)?

宿主机：Ubuntu16.04

容器：Alpine Linux 3.10.1

Configures you used:

frps.ini

[common]

#frp服务器监听地址，如果是IPV6地址必须用中括号包围

bind_addr = 0.0.0.0

#frp服务器监听端口

bind_port = 7000

#kcp的udp监听端口，如果不设那就不启用

#kcp_bind_port = 7000

#指定使用的协议，默认tcp，可选kcp

#protocol = kcp

#如果要使用vitual host，就必须设置

vhost_http_port = 8080

vhost_http_port = 5000

#vhost_https_port = 443

#Web后台监听端口

dashboard_port = 7500

#Web后台的用户名和密码

dashboard_user = admin

dashboard_pwd = admi

#日志输出，可以设置为具体的日志文件或者console

log_file = /var/log/frps.log

frpc.ini

[common]

server_addr = ngrok.spring-cloud.tk

server_port = 7000

[web1]

type = http

local_port = 80

custom_domains = ngrok.spring-cloud.tk

subdomain = w1

remote_port = 5000

[web2]

type = http

local_port = 80

custom_domains = ngrok.spring-cloud.tk

subdomain = w2

remote_port = 8080

Steps to reproduce the issue:

同时穿透多个内网web服务

单个web服务穿透是可以

3.已配置通配符域名

Describe the results you received:

frpc.exe -c frpc.ini

2019/07/17 15:45:59 [I] [service.go:221] login to server success, get run id [045646284fe11c1c], server udp port [0]

2019/07/17 15:45:59 [I] [proxy_manager.go:137] [045646284fe11c1c] proxy added: [web1 web2]

2019/07/17 15:46:00 [I] [control.go:144] [web1] start proxy success

2019/07/17 15:46:00 [W] [control.go:142] [web2] start error: router config conflict

2019/07/17 15:46:33 [W] [control.go:142] [web2] start error: router config conflict

2019/07/17 15:47:06 [W] [control.go:142] [web2] start error: router config conflict

2019/07/17 15:47:39 [W] [control.go:142] [web2] start error: router config conflict

2019/07/17 15:48:12 [W] [control.go:142] [web2] start error: router config conflict

2019/07/17 15:48:45 [W] [control.go:142] [web2] start error: router config conflict

2019/07/17 15:49:18 [W] [control.go:142] [web2] start error: router config conflict

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Can you point out what caused this issue (optional)