mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #3770] frpc config reload fails saying it requires web server port #3000
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#3000
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 @rbose21 on GitHub (Nov 14, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3770
Bug Description
I have an frpc client running fine, but if I update its config file and try to hot reload, the command fails. See below:
If I dont use reload everything works fine. I want to reload the frpc config with updated changes without stopping the client. Not sure why it requires the web-server and I can see that if I add the webServer.Port to frpc config, it tries to call the API
http://127.0.0.1:7500/api/reloadso it might be getting confused with the dashboard reload.frpc Version
0.52.3
frps Version
0.52.3
System Architecture
linux/amd64
Configurations
frpc config is:
serverAddr = "x.x.x.x"
serverPort = xxxx
auth.method = "token"
auth.token = "xxxxxxxx"
log.to = "/frpc.log"
log.level = "debug"
log.maxDays = 3
includes = ["/confd/*.toml"]
Logs
No response
Steps to reproduce
Affected area
@superzjg commented on GitHub (Nov 14, 2023):
https://github.com/fatedier/frp/blob/dev/README.md#hot-reloading-frpc-configuration
@rbose21 commented on GitHub (Nov 15, 2023):
thanks for the reply. Isn't hot reload for reloading frpc with a new configuration. I am not trying to use the HTTP API, only trying to reload a running client with an updated configuration
@superzjg commented on GitHub (Nov 16, 2023):
May not support this feature.
@github-actions[bot] commented on GitHub (Dec 17, 2023):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.