-
-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple [[proxies]] sections in toml #4177
Comments
Need logs. |
It seems that only one HTTPS/HTTP can be configured. If multiple are needed, please use |
Thank you for your reply. Can you please help with a sample config? The full config seems to have specific fields that work under different configs:[[proxies]]
|
Sorry, I don't know why things are appearing bold in my post. |
Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close. |
Bug Description
Why is this config frpc.toml not working?
frpc.toml
serverAddr = "someserver.link"
serverPort = 7000
[[proxies]]
name = "janus"
type = "https"
customDomains = ["am_0001_jn.someserver.link"]
[proxies.plugin]
type = "https2https"
localAddr = "127.0.0.1:8089"
crtPath = "/home/pi/Documents/certificates/fullchain.pem"
keyPath = "/home/pi/Documents/certificates/am_private.pem"
hostHeaderRewrite = "127.0.0.1"
requestHeaders.set.x-from-where = "frp"
[[proxies]]
name = "web"
type = "https"
customDomains = ["am_0001_wb.someserver.link"]
[proxies.plugin]
type = "https2http"
localAddr = "127.0.0.1:8000"
crtPath = "/home/pi/Documents/certificates/fullchain.pem"
keyPath = "/home/pi/Documents/certificates/am_private.pem"
hostHeaderRewrite = "127.0.0.1"
requestHeaders.set.x-from-where = "frp"
If I remove the second proxies section, the config works. But two proxies sections seem to be only loading the second one. The first is exposing a janus https server, and the second is exposing a web http server.
frpc Version
0.57.0
frps Version
0.57.0
System Architecture
Rpi runs frpc, ec2 linux runs frps
Configurations
I have included it in the config above
Logs
No response
Steps to reproduce
...
Affected area
The text was updated successfully, but these errors were encountered: