github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00

[GH-ISSUE #1186] How to trigger events/notifications in frp server when it detected one of the client is offline? #928

New issue

Closed

opened 2026-05-05 12:35:25 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 12:35:25 -06:00

Owner

Originally created by @jerrychong25 on GitHub (Apr 8, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1186

Hi,

Currently I have implemented frp communication between 5 clients and 1 server.

So far everythings are working fine.

However, I can't trigger events/notifications in frp server when it detected one of client is offline.

This is because I can only know the client is down when error displayed inside the logs.

So, how could I do to trigger events/notifications to another website/application so that I could display this error details and subsequently proceed backup action or etc?

Thanks.

Originally created by @jerrychong25 on GitHub (Apr 8, 2019). Original GitHub issue: https://github.com/fatedier/frp/issues/1186 Hi, Currently I have implemented frp communication between 5 clients and 1 server. So far everythings are working fine. However, I can't trigger events/notifications in frp server when it detected one of client is offline. This is because I can only know the client is down when error displayed inside the logs. So, how could I do to trigger events/notifications to another website/application so that I could display this error details and subsequently proceed backup action or etc? Thanks.

gitea-mirror closed this issue

2026-05-05 12:35:27 -06:00

gitea-mirror commented

2026-05-05 12:35:29 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 9, 2019):

frps support API for getting proxies status such as /api/proxy/tcp.

You can try to call this API at intervals to check proxies status and do what you want.

@fatedier commented on GitHub (Apr 9, 2019): frps support API for getting proxies status such as `/api/proxy/tcp`. You can try to call this API at intervals to check proxies status and do what you want.

gitea-mirror commented

2026-05-05 12:35:30 -06:00

Author

Owner

@jerrychong25 commented on GitHub (Apr 9, 2019):

frps support API for getting proxies status such as /api/proxy/tcp.

You can try to call this API at intervals to check proxies status and do what you want.

Any documentation on this API section?

For example:
My frps server domain name is http://example.com/

So I could check proxies status via http://example.com/api/proxy/tcp?

Thanks.

@jerrychong25 commented on GitHub (Apr 9, 2019): > frps support API for getting proxies status such as `/api/proxy/tcp`. > > You can try to call this API at intervals to check proxies status and do what you want. Any documentation on this API section? For example: My frps server domain name is **http://example.com/** So I could check proxies status via **http://example.com/api/proxy/tcp**? Thanks.

gitea-mirror commented

2026-05-05 12:35:31 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 9, 2019):

You should set dashboard params to enable this feature.

# frps.ini
[common]
dashboard_addr = 0.0.0.0
dashboard_port = 7500

# dashboard user and passwd for basic auth protect, if not set, both default value is admin
dashboard_user = admin
dashboard_pwd = admin

The api is http://127.0.0.1:7500/api/proxy/tcp.

It's designed to display data on dashboard, no documentation now, maybe future.

@fatedier commented on GitHub (Apr 9, 2019): You should set dashboard params to enable this feature. ```ini # frps.ini [common] dashboard_addr = 0.0.0.0 dashboard_port = 7500 # dashboard user and passwd for basic auth protect, if not set, both default value is admin dashboard_user = admin dashboard_pwd = admin ``` The api is `http://127.0.0.1:7500/api/proxy/tcp`. It's designed to display data on dashboard, no documentation now, maybe future.

gitea-mirror commented

2026-05-05 12:35:32 -06:00

Author

Owner

@jerrychong25 commented on GitHub (Apr 9, 2019):

You should set dashboard params to enable this feature.
# frps.ini
[common]
dashboard_addr = 0.0.0.0
dashboard_port = 7500

# dashboard user and passwd for basic auth protect, if not set, both default value is admin
dashboard_user = admin
dashboard_pwd = admin
The api is http://127.0.0.1:7500/api/proxy/tcp.

It's designed to display data on dashboard, no documentation now, maybe future.

Tested it is working, and it returns JSON data for all my clients.

But how could I do the authentication step entered with username admin and password admin when calling this API from my application side?

In my PC, it would pop up a screen to prompt input of dashboard username and password. So I could enter these details myself. But impossible for my application to do this step.

@jerrychong25 commented on GitHub (Apr 9, 2019): > You should set dashboard params to enable this feature. > > ```ini > # frps.ini > [common] > dashboard_addr = 0.0.0.0 > dashboard_port = 7500 > > # dashboard user and passwd for basic auth protect, if not set, both default value is admin > dashboard_user = admin > dashboard_pwd = admin > ``` > > The api is `http://127.0.0.1:7500/api/proxy/tcp`. > > It's designed to display data on dashboard, no documentation now, maybe future. Tested it is working, and it returns JSON data for all my clients. But how could I do the authentication step entered with username **admin** and password **admin** when calling this API from my application side? In my PC, it would pop up a screen to prompt input of dashboard username and password. So I could enter these details myself. But impossible for my application to do this step.

gitea-mirror commented

2026-05-05 12:35:32 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 9, 2019):

Try to search http basic auth for more details.

@fatedier commented on GitHub (Apr 9, 2019): Try to search `http basic auth` for more details.