mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #3113] Documentation for API for remote management and status check #2496
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#2496
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 @Palezvar on GitHub (Sep 29, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3113
Bug Description
Are there any APIs on FRP that we can use to check the current status of proxies and get some details for each.
If so, is any documentation available?
Thanks,
frpc Version
0.44
frps Version
0.44
System Architecture
linux/amd64
Configurations
admin_addr = 127.0.0.1
admin_port = 7400
Logs
No response
Steps to reproduce
...
Affected area
@Becods commented on GitHub (Sep 29, 2022):
https://github.com/fatedier/frp/pull/1668
or
9d077b02cf/server/dashboard_api.go (L35-L52)@Palezvar commented on GitHub (Sep 29, 2022):
Can you please elaborate on this one.
Can I actually access different proxy details and status externally using Postman or Curl? If so, what is the syntax?
My use case is that I am trying to detect new proxy connections and take some customs against them. That is the reason I am looking for an API to get a list of proxies and their details.
Thanks,
@Palezvar commented on GitHub (Oct 2, 2022):
folks, is there anyway for me to access the proxy details such as "name", "domain", "status", "encryption" remotely via an API? If not, maybe there is another method you could recommend me to harness this data via a script that runs locally on the frp server.
Please advise.
@github-actions[bot] commented on GitHub (Nov 2, 2022):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.