[GH-ISSUE #3606] "Get server info from frps failed!" with Basic Auth details in URL

gitea-mirror commented

2026-05-05 13:51:39 -06:00

Owner

Copy link

Originally created by @MariuszT on GitHub (Sep 9, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3606

Bug Description

I want simple access to my dashboard without putting Basic Auth details every time. That's why I prepared a URL to my dashboard with the user and password in a URL like this: https://user:password@example.com:7000. When I open such a URL I have a communication error and a popup with the message "Get server info from frps failed!". After that, when I open the same page but without Basic Auth details, everything works correctly.

Obviously, it's a low priority issue, but it will be great to have a fix for this. Thanks for your awesome work!

frpc Version

0.51.3

frps Version

0.51.3

System Architecture

linux/amd64 Debian

Configurations

[common]
bind_addr = example.com
bind_port = 7000
dashboard_addr = example.com
dashboard_port = 7500
dashboard_user = user
dashboard_pwd = pass
dashboard_tls_mode = true
dashboard_tls_cert_file = /example.com.cer
dashboard_tls_key_file = /example.com.key
authentication_method = token
token = token123
subdomain_host = example.com
vhost_http_port = 80
vhost_https_port = 443
tls_only = false
tls_cert_file = /example.com.cer
tls_key_file = /example.com.key
tls_trusted_ca_file = /ca.cer

Logs

root@frp:/opt/frp# /opt/frp/frps -c /opt/frp/frps.ini
2023/09/09 11:08:47 [I] [root.go:204] frps uses config file: /opt/frp/frps.ini
2023/09/09 11:08:47 [I] [service.go:206] frps tcp listen on example.com:7000
2023/09/09 11:08:47 [I] [service.go:267] http service listen on example.com:80
2023/09/09 11:08:47 [I] [service.go:282] https service listen on example.com:443
2023/09/09 11:08:47 [I] [service.go:318] Dashboard listen on example.com:7500
2023/09/09 11:08:47 [I] [root.go:213] frps started successfully

Steps to reproduce

Run FRP
Open FRP dashboard with Basic Auth user and password in URL

Affected area

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

Originally created by @MariuszT on GitHub (Sep 9, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3606 ### Bug Description I want simple access to my dashboard without putting Basic Auth details every time. That's why I prepared a URL to my dashboard with the user and password in a URL like this: https://user:password@example.com:7000. When I open such a URL I have a communication error and a popup with the message "Get server info from frps failed!". After that, when I open the same page but without Basic Auth details, everything works correctly. Obviously, it's a low priority issue, but it will be great to have a fix for this. Thanks for your awesome work! ### frpc Version 0.51.3 ### frps Version 0.51.3 ### System Architecture linux/amd64 Debian ### Configurations [common] bind_addr = example.com bind_port = 7000 dashboard_addr = example.com dashboard_port = 7500 dashboard_user = user dashboard_pwd = pass dashboard_tls_mode = true dashboard_tls_cert_file = /example.com.cer dashboard_tls_key_file = /example.com.key authentication_method = token token = token123 subdomain_host = example.com vhost_http_port = 80 vhost_https_port = 443 tls_only = false tls_cert_file = /example.com.cer tls_key_file = /example.com.key tls_trusted_ca_file = /ca.cer ### Logs root@frp:/opt/frp# /opt/frp/frps -c /opt/frp/frps.ini 2023/09/09 11:08:47 [I] [root.go:204] frps uses config file: /opt/frp/frps.ini 2023/09/09 11:08:47 [I] [service.go:206] frps tcp listen on example.com:7000 2023/09/09 11:08:47 [I] [service.go:267] http service listen on example.com:80 2023/09/09 11:08:47 [I] [service.go:282] https service listen on example.com:443 2023/09/09 11:08:47 [I] [service.go:318] Dashboard listen on example.com:7500 2023/09/09 11:08:47 [I] [root.go:213] frps started successfully ### Steps to reproduce 1. Run FRP 2. Open FRP dashboard with Basic Auth user and password in URL ### 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 13:51:39 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:51:42 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Oct 10, 2023):

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

@github-actions[bot] commented on GitHub (Oct 10, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

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

[PR #2878] [CLOSED] Dev #4651

No Branch/Tag specified