mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #5054] multiple vhosts port frps #3973
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#3973
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 @Kirutian on GitHub (Nov 13, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5054
Bug Description
Currently unable to add multiple vhostHTTPS ports
Nextcloud needs multiple ports from a domain to configure it properly. When I try to add multiple vhost ports, the server does not start.
frpc Version
0.65.0
frps Version
0.65.0
System Architecture
rocky9/linux/amd64
Configurations
frps.toml
bindPort = 7227
auth.token = "secret"
vhostHTTPPort = 80
vhostHTTPSPort = 443
vhostHTTPSPort = 8443
Logs
json: cannot unmarshal string into Go value of type v1.ServerConfig
Steps to reproduce
...
Affected area
@Kirutian commented on GitHub (Nov 23, 2025):
I've not been able to find a way to do this. Reviewing the source code I can not add this function without significant changes. Im going to start working on an alternative method.
@Kirutian commented on GitHub (Nov 29, 2025):
There are forks that add the range:tcp_port definition. I wonder if there is a way to do this without forking? Can any one provide any insight?
@Kirutian commented on GitHub (Nov 29, 2025):
It appears before the shift to toml from ini, the range:tcp_port definition is no longer possible. I wonder what the replacement is.
@github-actions[bot] commented on GitHub (Dec 14, 2025):
Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.