[GH-ISSUE #3609] [ASK] How to trigger reauthenticate when one of client proxies are rejected after running

gitea-mirror commented

2026-05-05 13:51:39 -06:00

Owner

Copy link

Originally created by @auzty on GitHub (Sep 13, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3609

Describe the feature request

my case are :

frpc A connected with subdomain proxies john and alice
i want to kick out the frpc A (re-auth) because the john proxy already rejected on my handler

i'm using frp v0.51.3
the current behavior are both of the proxies john and alice still running, (need exiting the frpc and then reconnecting again to check the NewProxy operation handler)

any ideas?

Describe alternatives you've considered

currently i'm forking the frp repository, and then patching the Ping operation to send proxies details when doing heartbeat and then i'm checking with the external handler

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @auzty on GitHub (Sep 13, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3609 ### Describe the feature request my case are : 1. frpc **A** connected with subdomain proxies **john** and **alice** 2. i want to kick out the frpc **A** (re-auth) because the **john** proxy already rejected on my handler i'm using frp v0.51.3 the current behavior are both of the proxies **john** and **alice** still running, (need exiting the frpc and then reconnecting again to check the NewProxy operation handler) any ideas? ### Describe alternatives you've considered currently i'm forking the frp repository, and then patching the Ping operation to send proxies details when doing *heartbeat* and then i'm checking with the external handler ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [X] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:51:39 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:51:42 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Oct 14, 2023):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Oct 14, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified