mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #2736] Subdomain Bug #2187
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#2187
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @felix530-h on GitHub (Jan 4, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2736
Bug Description
Thanks for the great github repository.
I want to make multiple services reachable using frp. I have set the following in the config:
frps.ini:
[common]
bind_port = 7000
vhost_http_port = 8480
subdomain_host = test.abc
frpc.ini
[common]
server_addr = 127.0.0.1
server_port = 7000
[web-01]
type = http
local_ip = 127.0.0.1
local_port = 80
subdomain = web01
custom_domains = test.abc
[web-02]
type = http
local_ip = 192.168.178.1
local_port = 80
subdomain = web02
custom_domains = test.abc
as soon as I start frpc I get the following error message:
[web-02] start error: router config conflict
But if I start only one subdomain service then don't get any error message.
frpc Version
0.38.0
frps Version
0.38.0
System Architecture
linux_amd64
Configurations
frpc.ini
[common]
server_addr = 127.0.0.1
server_port = 7000
[web-01]
type = http
local_ip = 127.0.0.1
local_port = 80
subdomain = web01
custom_domains = test.abc
[web-02]
type = http
local_ip = 192.168.178.1
local_port = 80
subdomain = web02
custom_domains = test.abc
Logs
error: router config conflict
Steps to reproduce
...
Affected area
@fatedier commented on GitHub (Jan 5, 2022):
Remove
custom_domains@felix530-h commented on GitHub (Jan 5, 2022):
Thanks for the fast support. Without "custom_domains" it works.