mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #2757] Load balancer for frp http proxy for horizontal scaling. #2203
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#2203
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 @anand-010 on GitHub (Jan 12, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2757
Describe the feature request
Nginx or other load balancer technique for dynamic loads.
I have already seen the subdomains assigning to each server which is not flexible, scalable and dynamic.
May be there needs to be extra headers or something from proxy connection and user connection for the load balancer to route.
Describe alternatives you've considered
Assigning subdomains to each server manually is the current solutionwhich is not flexible, scalable and dynamic.
Affected area
@fatedier commented on GitHub (Jan 12, 2022):
I can't get your point. Can you describe more or draw a simple flow chart?
@anand-010 commented on GitHub (Jan 12, 2022):
Here is the flow chart i am created.

Before that i am created plugin for authentication for each reverse proxy users.
Each http connections and it's associated reverse proxy connection must be forward to same vm otherwise it doesn't work.
How do we deal with this situations.
@fatedier commented on GitHub (Jan 12, 2022):
As you said, load-balance by DNS is a simple way. You can resolve
xxx.group1.comandxxx.group2.comto different VMs.This project is not designed for this scenario. It's not an easy feature, especially for TCP connections.
@anand-010 commented on GitHub (Jan 13, 2022):
Do you have any suggestions how to implement it.
is there any header or other specific data's to uniquely identify proxy connection and http user connections ?.