[GH-ISSUE #4296] I have set up webserver, but after starting frps, I am unable to access the dashboard

gitea-mirror commented

2026-05-05 14:10:58 -06:00

Owner

Originally created by @xinoer on GitHub (Jun 24, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4296

Bug Description

I have set up webserver, but after starting frps, I am unable to access the dashboard
The ‘frps.toml’ file is as follows:
[common]
bind_port = 7000
auth.method = "token"
auth.token = "123456"

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

log_file = ./frps.log
log_level = info
log_max_days = 3

vhostHTTPSPort = 443
subdomain_host = 123.com

frpc Version

frp_0.58.0

frps Version

frp_0.58.0

System Architecture

windows_amd64

Configurations

[common]
bind_port = 7000
auth.method = "token"
auth.token = "123456"

web服务器.addr = “127.0.0.1”
web服务器.port = 7001
web服务器.user = “管理员”
web服务器.password = “管理员”

log_file = ./frps.log
log_level = info
log_max_days = 3

vhostHTTPSPort = 443
subdomain_host = 123.com

Logs

The log is as follows：
2024-06-24 10:27:29.400 [I] [frps/root.go:105] frps uses config file: frps.toml
2024-06-24 10:27:29.534 [I] [server/service.go:237] frps tcp listen on 0.0.0.0:7000
2024-06-24 10:27:29.534 [I] [frps/root.go:114] frps started successfully

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 @xinoer on GitHub (Jun 24, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4296 ### Bug Description I have set up webserver, but after starting frps, I am unable to access the dashboard The ‘frps.toml’ file is as follows: [common] bind_port = 7000 auth.method = "token" auth.token = "123456" webServer.addr = "127.0.0.1" webServer.port = 7001 webServer.user = "admin" webServer.password = "admin" log_file = ./frps.log log_level = info log_max_days = 3 vhostHTTPSPort = 443 subdomain_host = 123.com ### frpc Version frp_0.58.0 ### frps Version frp_0.58.0 ### System Architecture windows_amd64 ### Configurations [common] bind_port = 7000 auth.method = "token" auth.token = "123456" web服务器.addr = “127.0.0.1” web服务器.port = 7001 web服务器.user = “管理员” web服务器.password = “管理员” log_file = ./frps.log log_level = info log_max_days = 3 vhostHTTPSPort = 443 subdomain_host = 123.com ### Logs The log is as follows： 2024-06-24 10:27:29.400 [I] [frps/root.go:105] frps uses config file: frps.toml 2024-06-24 10:27:29.534 [I] [server/service.go:237] frps tcp listen on 0.0.0.0:7000 2024-06-24 10:27:29.534 [I] [frps/root.go:114] frps started successfully ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [X] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:10:58 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

@wuai1024 commented on GitHub (Jun 24, 2024):

现在新版的已经没有这个参数了 ~~[common]~~

webServer.addr = "0.0.0.0"

@wuai1024 commented on GitHub (Jun 24, 2024): 现在新版的已经没有这个参数了 ~~[common]~~ ```shell webServer.addr = "0.0.0.0" ```

gitea-mirror commented

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

Author

Owner

@xinoer commented on GitHub (Jun 24, 2024):

现在新版的已经没有这个参数了 ~~[common]~~
webServer.addr = "0.0.0.0"

可是我去掉[common]，也不行呀

@xinoer commented on GitHub (Jun 24, 2024): > 现在新版的已经没有这个参数了 ~[common]~ > > ```shell > webServer.addr = "0.0.0.0" > ``` 可是我去掉[common]，也不行呀

gitea-mirror commented

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

Author

Owner

@arvinws commented on GitHub (Jun 25, 2024):

参考这个可以成功http://blog.168hot.cn/448.html

@arvinws commented on GitHub (Jun 25, 2024): 参考这个可以成功http://blog.168hot.cn/448.html

gitea-mirror commented

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

Author

Owner

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

gitea-mirror commented

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

Author

Owner

@xiaoheibaobao commented on GitHub (Jul 21, 2024):

请问你的问题解决了吗
，我也是这样

@xiaoheibaobao commented on GitHub (Jul 21, 2024): 请问你的问题解决了吗，我也是这样

gitea-mirror commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Aug 13, 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 (Aug 13, 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:52 -06:00

[PR #3390] [CLOSED] Add support for loongarch64 #4740