[GH-ISSUE #5014] 在0.65版本中默认配置启动frpc端web管理报错请问怎么解决? #3948

Closed
opened 2026-05-05 14:30:49 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @xmlzy on GitHub (Oct 6, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5014

Bug Description

防火墙已关闭,端口无占用
配置文件为如下

frpc.toml

webServer.addr = "127.0.0.1"
webServer.port = 7400
webServer.user = "admin"
webServer.password = "admin"

在终端执行
./frpc reload -c frpc.toml

报错Get "http://127.0.0.1:7400/api/reload?strictConfig=true": dial tcp 127.0.0.1:7400: connect: connection refused

frpc Version

0.65.0

frps Version

未使用

System Architecture

linux/amd64 or windows/amd64

Configurations

frpc.toml

webServer.addr = "127.0.0.1"
webServer.port = 7400
webServer.user = "admin"
webServer.password = "admin"

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 @xmlzy on GitHub (Oct 6, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/5014 ### Bug Description 防火墙已关闭,端口无占用 配置文件为如下 # frpc.toml webServer.addr = "127.0.0.1" webServer.port = 7400 webServer.user = "admin" webServer.password = "admin" 在终端执行 ./frpc reload -c frpc.toml 报错Get "http://127.0.0.1:7400/api/reload?strictConfig=true": dial tcp 127.0.0.1:7400: connect: connection refused ### frpc Version 0.65.0 ### frps Version 未使用 ### System Architecture linux/amd64 or windows/amd64 ### Configurations # frpc.toml webServer.addr = "127.0.0.1" webServer.port = 7400 webServer.user = "admin" webServer.password = "admin" ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### 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:30:49 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Oct 24, 2025):

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

<!-- gh-comment-id:3440097832 --> @github-actions[bot] commented on GitHub (Oct 24, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#3948
No description provided.