[GH-ISSUE #1712] Dashboard anti-brute force #1351

New issue

Closed

opened 2026-05-05 12:51:33 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 12:51:33 -06:00

Owner

Originally created by @befantasy on GitHub (Mar 20, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/1712

Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly.
(为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。)
(请不要在 issue 评论中出现无意义的加1，我也是 等内容，将会被直接删除。)
(由于个人精力有限，和系统环境，网络环境等相关的求助问题请转至其他论坛或社交平台。)

Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST

What version of frp are you using (./frpc -v or ./frps -v)?
FRP 0.32.0

What operating system and processor architecture are you using (go env)?

Configures you used:

Steps to reproduce the issue:
1.
2.
3.

Describe the results you received:

Describe the results you expected:
dashboard可否加入brute force机制？本打算使用nginx反代frp 7500端口，借助fail2ban和ngixn来实现。但搞了半天，反代不成功。不知道有什么办法可以解决dashboard的brute force破解？

Additional information you deem important (e.g. issue happens only occasionally):

Can you point out what caused this issue (optional)

Originally created by @befantasy on GitHub (Mar 20, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/1712 Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly. (为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。) (请不要在 issue 评论中出现无意义的 **加1**，**我也是** 等内容，将会被直接删除。) (由于个人精力有限，和系统环境，网络环境等相关的求助问题请转至其他论坛或社交平台。) Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST **What version of frp are you using (./frpc -v or ./frps -v)?** FRP 0.32.0 **What operating system and processor architecture are you using (`go env`)?** **Configures you used:** **Steps to reproduce the issue:** 1. 2. 3. **Describe the results you received:** **Describe the results you expected:** dashboard可否加入brute force机制？本打算使用nginx反代frp 7500端口，借助fail2ban和ngixn来实现。但搞了半天，反代不成功。不知道有什么办法可以解决dashboard的brute force破解？ **Additional information you deem important (e.g. issue happens only occasionally):** **Can you point out what caused this issue (optional)**

gitea-mirror closed this issue

2026-05-05 12:51:34 -06:00

gitea-mirror commented

2026-05-05 12:51:36 -06:00

Author

Owner

@befantasy commented on GitHub (Mar 20, 2020):

补充一下，刚才用nginx反代，防火墙只允许localhost连接7500端口，搞定了。
但还是希望FRP能原生支持时间窗口内密码重试次数限制。

@befantasy commented on GitHub (Mar 20, 2020): 补充一下，刚才用nginx反代，防火墙只允许localhost连接7500端口，搞定了。但还是希望FRP能原生支持时间窗口内密码重试次数限制。

gitea-mirror commented

2026-05-05 12:51:36 -06:00

Author

Owner

@mmiker commented on GitHub (Mar 21, 2020):

搭车提个建议，客户端的static_file 的显示格式可否美化一下，比如加个html的.,现在这样看着有点丑。

@mmiker commented on GitHub (Mar 21, 2020): 搭车提个建议，客户端的static_file 的显示格式可否美化一下，比如加个html的<table>.,现在这样看着有点丑。

gitea-mirror commented

2026-05-05 12:51:37 -06:00

Author

Owner

@forcemeter commented on GitHub (Mar 22, 2020):