[GH-ISSUE #4863] frpc reload don't work

gitea-mirror commented

2026-05-05 14:27:11 -06:00

Owner

Copy link

Originally created by @arickxuan on GitHub (Jul 2, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4863

Bug Description

like this

frpc Version

0.63.0

frps Version

0.63.0

System Architecture

linux/arm64

Configurations

frpc.toml

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 @arickxuan on GitHub (Jul 2, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4863 ### Bug Description like this ![Image](https://github.com/user-attachments/assets/cfa58d66-7a01-4516-beb7-9c41e0bc55f5) ### frpc Version 0.63.0 ### frps Version 0.63.0 ### System Architecture linux/arm64 ### Configurations frpc.toml ### 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:27:11 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:27:14 -06:00

Author

Owner

Copy link

@superzjg commented on GitHub (Jul 2, 2025):

You must specify the configuration file using -c.
And web server port should be set if you want to use this feature

@superzjg commented on GitHub (Jul 2, 2025): You must specify the configuration file using -c. And web server port should be set if you want to use this feature

gitea-mirror commented

2026-05-05 14:27:15 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jul 17, 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 (Jul 17, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

No Branch/Tag specified