[GH-ISSUE #4146] [Feature Request] 错误配置跳过功能

gitea-mirror commented

2026-05-05 14:06:43 -06:00

Owner

Copy link

Originally created by @L-evi on GitHub (Apr 10, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4146

Describe the feature request

能够添加一个错误配置跳过的功能吗？或者允许用户配置一个兜底文件，这样子再不小心配置错误了之后，有一定的容错率
因为目前我这边配置了ssh登陆，但是我添加别的内网穿透的时候会不小心配置错误，导致要千里迢迢跑回去重新设置一下配置文件，如果在项目启动的时候感知到配置文件错误并且启动兜底文件的话，会更加好。感谢开源作者的不断付出

Describe alternatives you've considered

No response

Affected area

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

Originally created by @L-evi on GitHub (Apr 10, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4146 ### Describe the feature request 能够添加一个错误配置跳过的功能吗？或者允许用户配置一个兜底文件，这样子再不小心配置错误了之后，有一定的容错率因为目前我这边配置了ssh登陆，但是我添加别的内网穿透的时候会不小心配置错误，导致要千里迢迢跑回去重新设置一下配置文件，如果在项目启动的时候感知到配置文件错误并且启动兜底文件的话，会更加好。感谢开源作者的不断付出 ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:06:43 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:06:46 -06:00

Author

Owner

Copy link

@superzjg commented on GitHub (Apr 11, 2024):

自v0.55.0
--strict-config 的默认值已从 false 更改为 true。如果您的配置文件使用了不存在的配置项或存在拼写错误，则应用程序将引发错误。此启动参数是在 v0.53.0 版本中引入的（false）。如果希望继续使用旧的行为，则需要显式设置 --strict-config=false

@superzjg commented on GitHub (Apr 11, 2024): 自[v0.55.0](https://github.com/fatedier/frp/releases/tag/v0.55.0) --strict-config 的默认值已从 false 更改为 true。如果您的配置文件使用了不存在的配置项或存在拼写错误，则应用程序将引发错误。此启动参数是在 v0.53.0 版本中引入的（false）。如果希望继续使用旧的行为，则需要显式设置 --strict-config=false

gitea-mirror commented

2026-05-05 14:06:47 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (May 3, 2024):

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

@github-actions[bot] commented on GitHub (May 3, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:47:16 -06:00

[PR #3275] [CLOSED] add max_delay_time parameter to frpc #4712

No Branch/Tag specified