[GH-ISSUE #5025] 验证错误

gitea-mirror commented

2026-05-05 14:31:05 -06:00

Owner

Copy link

Originally created by @interesthacker on GitHub (Oct 20, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5025

Bug Description

frpc.exe使用verify命令验证配置文件时，其默认寻找的文件为frpc.ini，无法验证frpc.toml

frps验证时一直显示未指定配置文件

frpc Version

0.65

frps Version

0.65

System Architecture

windows/amd64

Configurations

frpc.exe使用verify命令验证配置文件时，其默认查找的文件为frpc.ini，无法验证frpc.toml，frps验证时一直显示未指定配置文件

Logs

No response

Steps to reproduce

...

Affected area

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

Originally created by @interesthacker on GitHub (Oct 20, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/5025 ### Bug Description frpc.exe使用verify命令验证配置文件时，其默认寻找的文件为frpc.ini，无法验证frpc.toml <img width="815" height="75" alt="Image" src="https://github.com/user-attachments/assets/4f698ce8-6e23-4d89-9717-f2cfbc07f389" /> frps验证时一直显示未指定配置文件 <img width="819" height="132" alt="Image" src="https://github.com/user-attachments/assets/289aad21-4ee4-4b52-b4b3-894edec82cc3" /> ### frpc Version 0.65 ### frps Version 0.65 ### System Architecture windows/amd64 ### Configurations frpc.exe使用verify命令验证配置文件时，其默认查找的文件为frpc.ini，无法验证frpc.toml，frps验证时一直显示未指定配置文件 ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:31:05 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:31:09 -06:00

Author

Owner

Copy link

@ly360 commented on GitHub (Oct 21, 2025):

使用-c参数指定配置文件。

你可以使用-h命令查看更多可以使用的参数。

@ly360 commented on GitHub (Oct 21, 2025): 使用-c参数指定配置文件。你可以使用-h命令查看更多可以使用的参数。

gitea-mirror commented

2026-05-05 14:31:09 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Nov 5, 2025):

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

@github-actions[bot] commented on GitHub (Nov 5, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

No Branch/Tag specified