github-starred/frp

Fork 0

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

[GH-ISSUE #2164] 如何删除服务器dashboard里失效的内网穿透 #1724

New issue

Closed

opened 2026-05-05 13:06:23 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 13:06:23 -06:00

Owner

Originally created by @zhengfan2014 on GitHub (Dec 25, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/2164

The solution you want

删除frp dashboard里失效的穿透
Alternatives considered

How to implement this function

加个删除按钮
Application scenarios of this function

治疗强迫症

Originally created by @zhengfan2014 on GitHub (Dec 25, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/2164  **The solution you want**  删除frp dashboard里失效的穿透 **Alternatives considered**  **How to implement this function**  加个删除按钮 **Application scenarios of this function**  治疗强迫症

gitea-mirror

2026-05-05 13:06:23 -06:00

closed this issue
added the
lifecycle/stale

no plan
labels

gitea-mirror commented

2026-05-05 13:06:27 -06:00

Author

Owner

@yuyulei commented on GitHub (Dec 25, 2020):

一方面，因为失效的代理是 frpc 发起的，担心出现，在 frps 端删除了代理，但是 frpc 端因为重启或者 reload 等又将删除的代理加了回来，造成一种明明刚删又回来了的现象。

另一方面，现在对代理的管理还处于比较简单的方式，如果以后有了统一管理的地方，可能会考虑做这类功能，但是近期内应该没有计划。

@yuyulei commented on GitHub (Dec 25, 2020): 一方面，因为失效的代理是 frpc 发起的，担心出现，在 frps 端删除了代理，但是 frpc 端因为重启或者 reload 等又将删除的代理加了回来，造成一种明明刚删又回来了的现象。另一方面，现在对代理的管理还处于比较简单的方式，如果以后有了统一管理的地方，可能会考虑做这类功能，但是近期内应该没有计划。

gitea-mirror commented

2026-05-05 13:06:27 -06:00

Author

Owner

@fatedier commented on GitHub (Dec 25, 2020):

It will be auto deleted after 7 days.

@fatedier commented on GitHub (Dec 25, 2020): It will be auto deleted after 7 days.

gitea-mirror commented

2026-05-05 13:06:28 -06:00

Author

Owner

@zngw commented on GitHub (Jan 11, 2021):

强迫症+1，每次都是restart frps

@zngw commented on GitHub (Jan 11, 2021): 强迫症+1，每次都是restart frps

gitea-mirror commented

2026-05-05 13:06:29 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 26, 2021):

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

@github-actions[bot] commented on GitHub (Feb 26, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 13:06:30 -06:00

Author

Owner

@i-iooi-i commented on GitHub (Apr 16, 2023):

确实，在7500管理页面看到了一长串失效的端口。。。。。难受

@i-iooi-i commented on GitHub (Apr 16, 2023): 确实，在7500管理页面看到了一长串失效的端口。。。。。难受

gitea-mirror commented

2026-05-05 13:06:30 -06:00

Author

Owner

@baymax55 commented on GitHub (Jul 10, 2023):