github-starred/frp
2
0
Fork 0
mirror of https://github.com/fatedier/frp.git synced 2026-05-15 16:15:49 -06:00
Code Issues 40 Projects Packages Wiki Activity Actions 1

[GH-ISSUE #1392] 个别网页出现401错误 #1100

New issue
Closed
opened 2026-05-05 12:42:35 -06:00 by gitea-mirror · 8 comments
gitea-mirror commented 2026-05-05 12:42:35 -06:00
Owner
Copy link

Originally created by @Nisekoi5 on GitHub (Aug 17, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1392

What version of frp are you using (./frpc -v or ./frps -v)?
frps: 0.28.2
frpc: 0.28.2

What operating system and processor architecture are you using (go env)?
Server: CentOS7
Client: Openwrt x86

Configures you used:
Server:

[common]
bind_port = 7000
dashboard_port = 7500
dashboard_user = *******
dashboard_pwd = *******
vhost_http_port = 10080
token = ********
vhost_https_port = 10443
subdomain_host = 域名.com

Client:

[common]
server_addr = 域名
server_port = 7000
token = ******

[lede]
type = http
local_ip = 192.168.51.1
local_port = 80
subdomain = lede

[dsmqb]
type = http
local_ip = 192.168.51.235
local_port = 12321
subdomain = qb

Steps to reproduce the issue:

  1. ./frps -c ./frps.ini
  2. ./frpc -c ./frpc.ini
  3. 打开网站 qb.域名.com:10080 与lede.域名.com:10080
  4. qb报错 HTTP ERROR 401,lede正常打开
  5. 打开qb所代理的网页，即192.168.51.235:12321正常打开

Describe the results you received:
Server:

2019/08/17 12:36:09 [I] [service.go:146] frps tcp listen on 0.0.0.0:7000
2019/08/17 12:36:09 [I] [service.go:188] http service listen on 0.0.0.0:10080
2019/08/17 12:36:09 [I] [service.go:209] https service listen on 0.0.0.0:10443
2019/08/17 12:36:09 [I] [service.go:239] Dashboard listen on 0.0.0.0:7500
2019/08/17 12:36:09 [I] [root.go:204] Start frps success
2019/08/17 12:36:16 [I] [service.go:356] client login info: ip [116.238.192.154:12870] version [0.28.2] hostname [] os [linux] arch [amd64]
2019/08]/17 12:36:16 [I] [tcp.go:66] [de5b26d25a8b2faa] [ssh] tcp proxy listen port [6000]
2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [ssh] success
2019/08/17 12:36:16 [I] [https.go:65] [de5b26d25a8b2faa] [pve] https proxy listen for host [pve.域名.com]
2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [pve] success
2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [na] http proxy listen for host [na.域名.com] location [] group []
2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [na] success
2019/08/17 12:36:16 [I] [https.go:65] [de5b26d25a8b2faa] [nas] https proxy listen for host [nas.域名.com]
2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [nas] success
2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [web] http proxy listen for host [web.域名.com] location [] group []
2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [web] success
2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [lede] http proxy listen for host [lede.域名.com] location [] group []
2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [lede] success
2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [phot] http proxy listen for host [phot.域名.com] location [] group []
2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [phot] success
2019/08/17 12:36:16 [I] [tcp.go:66] [de5b26d25a8b2faa] [win] tcp proxy listen port [6001]
2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [win] success
2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [dsmqb] http proxy listen for host [qb.域名.com] location [] group []
2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [dsmqb] success
2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [pan] http proxy listen for host [pan123.域名.com] location [] group []
2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [pan] success
2019/08/17 12:36:34 [I] [proxy.go:84] [de5b26d25a8b2faa] [dsmqb] get a new work connection: [116.238.192.154:12870]
2019/08/17 12:36:36 [I] [proxy.go:84] [de5b26d25a8b2faa] [dsmqb] get a new work connection: [116.238.192.154:12870]
2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870]
2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870]
2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870]
2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870]
2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870]
2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870]

Client:

root@Openwrt:/koolshare/frpc# ./frpc -c ./frpc.ini
2019/08/17 12:41:07 [I] [service.go:224] login to server success, get run id [614ca8faa8455b6a], server udp port [0]
2019/08/17 12:41:07 [I] [proxy_manager.go:137] [614ca8faa8455b6a] proxy added: [web lede phot ssh pve pan dsmqb nas na win]
2019/08/17 12:41:07 [I] [control.go:144] [pve] start proxy success
2019/08/17 12:41:07 [I] [control.go:144] [nas] start proxy success
2019/08/17 12:41:07 [I] [control.go:144] [na] start proxy success
2019/08/17 12:41:07 [I] [control.go:144] [win] start proxy success
2019/08/17 12:41:07 [I] [control.go:144] [dsmqb] start proxy success
2019/08/17 12:41:07 [I] [control.go:144] [lede] start proxy success
2019/08/17 12:41:07 [I] [control.go:144] [web] start proxy success
2019/08/17 12:41:07 [I] [control.go:144] [pan] start proxy success
2019/08/17 12:41:07 [I] [control.go:144] [phot] start proxy success
2019/08/17 12:41:07 [I] [control.go:144] [ssh] start proxy success

Describe the results you expected:
网页qb所代理的网页为bt软件qbittorrent 的web界面，外部端口为12321,软件是使用docker运行的。此处附上docker配置图与网页打开界面
docker配置
https://i.loli.net/2019/08/17/xyg7JfCkbzS8ohV.png
内网打开qbittorrent
https://i.loli.net/2019/08/17/3y6LTknMYbgKfp5.png
frp打开lede
https://i.loli.net/2019/08/17/R3EOtwcsZpYFMhb.png
frp打开qb
https://i.loli.net/2019/08/17/qI9lm4B5t2rC76R.png

我想用内网穿透实现在外网添加种子等操作。但是无论怎么设置都出现http 401错误，且只在这一个页面上出现。在仪表盘或者服务器日志均无异常。

Additional information you deem important (e.g. issue happens only occasionally):

Can you point out what caused this issue (optional)

Originally created by @Nisekoi5 on GitHub (Aug 17, 2019). Original GitHub issue: https://github.com/fatedier/frp/issues/1392 **What version of frp are you using (./frpc -v or ./frps -v)?** frps: 0.28.2 frpc: 0.28.2 **What operating system and processor architecture are you using (`go env`)?** Server: CentOS7 Client: Openwrt x86 **Configures you used:** Server: ``` [common] bind_port = 7000 dashboard_port = 7500 dashboard_user = ******* dashboard_pwd = ******* vhost_http_port = 10080 token = ******** vhost_https_port = 10443 subdomain_host = 域名.com ``` Client: ``` [common] server_addr = 域名 server_port = 7000 token = ****** [lede] type = http local_ip = 192.168.51.1 local_port = 80 subdomain = lede [dsmqb] type = http local_ip = 192.168.51.235 local_port = 12321 subdomain = qb ``` **Steps to reproduce the issue:** 1. ./frps -c ./frps.ini 2. ./frpc -c ./frpc.ini 3. 打开网站 `qb.域名.com:10080` 与`lede.域名.com:10080` 4. `qb`报错 HTTP ERROR 401,`lede`正常打开 5. 打开`qb`所代理的网页，即`192.168.51.235:12321`正常打开 **Describe the results you received:** Server: ``` 2019/08/17 12:36:09 [I] [service.go:146] frps tcp listen on 0.0.0.0:7000 2019/08/17 12:36:09 [I] [service.go:188] http service listen on 0.0.0.0:10080 2019/08/17 12:36:09 [I] [service.go:209] https service listen on 0.0.0.0:10443 2019/08/17 12:36:09 [I] [service.go:239] Dashboard listen on 0.0.0.0:7500 2019/08/17 12:36:09 [I] [root.go:204] Start frps success 2019/08/17 12:36:16 [I] [service.go:356] client login info: ip [116.238.192.154:12870] version [0.28.2] hostname [] os [linux] arch [amd64] 2019/08]/17 12:36:16 [I] [tcp.go:66] [de5b26d25a8b2faa] [ssh] tcp proxy listen port [6000] 2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [ssh] success 2019/08/17 12:36:16 [I] [https.go:65] [de5b26d25a8b2faa] [pve] https proxy listen for host [pve.域名.com] 2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [pve] success 2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [na] http proxy listen for host [na.域名.com] location [] group [] 2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [na] success 2019/08/17 12:36:16 [I] [https.go:65] [de5b26d25a8b2faa] [nas] https proxy listen for host [nas.域名.com] 2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [nas] success 2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [web] http proxy listen for host [web.域名.com] location [] group [] 2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [web] success 2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [lede] http proxy listen for host [lede.域名.com] location [] group [] 2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [lede] success 2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [phot] http proxy listen for host [phot.域名.com] location [] group [] 2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [phot] success 2019/08/17 12:36:16 [I] [tcp.go:66] [de5b26d25a8b2faa] [win] tcp proxy listen port [6001] 2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [win] success 2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [dsmqb] http proxy listen for host [qb.域名.com] location [] group [] 2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [dsmqb] success 2019/08/17 12:36:16 [I] [http.go:124] [de5b26d25a8b2faa] [pan] http proxy listen for host [pan123.域名.com] location [] group [] 2019/08/17 12:36:16 [I] [control.go:398] [de5b26d25a8b2faa] new proxy [pan] success 2019/08/17 12:36:34 [I] [proxy.go:84] [de5b26d25a8b2faa] [dsmqb] get a new work connection: [116.238.192.154:12870] 2019/08/17 12:36:36 [I] [proxy.go:84] [de5b26d25a8b2faa] [dsmqb] get a new work connection: [116.238.192.154:12870] 2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870] 2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870] 2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870] 2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870] 2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870] 2019/08/17 12:38:52 [I] [proxy.go:84] [de5b26d25a8b2faa] [lede] get a new work connection: [116.238.192.154:12870] ``` Client: ``` root@Openwrt:/koolshare/frpc# ./frpc -c ./frpc.ini 2019/08/17 12:41:07 [I] [service.go:224] login to server success, get run id [614ca8faa8455b6a], server udp port [0] 2019/08/17 12:41:07 [I] [proxy_manager.go:137] [614ca8faa8455b6a] proxy added: [web lede phot ssh pve pan dsmqb nas na win] 2019/08/17 12:41:07 [I] [control.go:144] [pve] start proxy success 2019/08/17 12:41:07 [I] [control.go:144] [nas] start proxy success 2019/08/17 12:41:07 [I] [control.go:144] [na] start proxy success 2019/08/17 12:41:07 [I] [control.go:144] [win] start proxy success 2019/08/17 12:41:07 [I] [control.go:144] [dsmqb] start proxy success 2019/08/17 12:41:07 [I] [control.go:144] [lede] start proxy success 2019/08/17 12:41:07 [I] [control.go:144] [web] start proxy success 2019/08/17 12:41:07 [I] [control.go:144] [pan] start proxy success 2019/08/17 12:41:07 [I] [control.go:144] [phot] start proxy success 2019/08/17 12:41:07 [I] [control.go:144] [ssh] start proxy success ``` **Describe the results you expected:** 网页`qb`所代理的网页为bt软件`qbittorrent` 的web界面，外部端口为12321,软件是使用docker运行的。此处附上docker配置图与网页打开界面 docker配置 https://i.loli.net/2019/08/17/xyg7JfCkbzS8ohV.png 内网打开qbittorrent https://i.loli.net/2019/08/17/3y6LTknMYbgKfp5.png frp打开lede https://i.loli.net/2019/08/17/R3EOtwcsZpYFMhb.png frp打开qb https://i.loli.net/2019/08/17/qI9lm4B5t2rC76R.png 我想用内网穿透实现在外网添加种子等操作。但是无论怎么设置都出现http 401错误，且只在这一个页面上出现。在仪表盘或者服务器日志均无异常。 **Additional information you deem important (e.g. issue happens only occasionally):** **Can you point out what caused this issue (optional)**
gitea-mirror commented 2026-05-05 12:42:38 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Aug 17, 2019):

401 表示鉴权失败，这个一般是你自己的内网的 web 服务返回的，你需要确认一下是否是这方面的原因。

<!-- gh-comment-id:522251128 --> @fatedier commented on GitHub (Aug 17, 2019): 401 表示鉴权失败，这个一般是你自己的内网的 web 服务返回的，你需要确认一下是否是这方面的原因。
gitea-mirror commented 2026-05-05 12:42:39 -06:00
Author
Owner
Copy link

@bingzhangdai commented on GitHub (Jun 22, 2020):

@Nisekoi5 Same problem here. 我也只有这一个网页出错，但配置应该是没有问题的，所有的网页都是同一个配置，并且内网访问没有问题，内网也是通过一个reverse proxy访问的。

<!-- gh-comment-id:647506865 --> @bingzhangdai commented on GitHub (Jun 22, 2020): @Nisekoi5 Same problem here. 我也只有这一个网页出错，但配置应该是没有问题的，所有的网页都是同一个配置，并且内网访问没有问题，内网也是通过一个reverse proxy访问的。
gitea-mirror commented 2026-05-05 12:42:39 -06:00
Author
Owner
Copy link

@Nisekoi5 commented on GitHub (Jun 22, 2020):

@Nisekoi5 Same problem here. 我也只有这一个网页出错，但配置应该是没有问题的，所有的网页都是同一个配置，并且内网访问没有问题，内网也是通过一个reverse proxy访问的。

关闭CSRF即可

<!-- gh-comment-id:647545785 --> @Nisekoi5 commented on GitHub (Jun 22, 2020): > @Nisekoi5 Same problem here. 我也只有这一个网页出错，但配置应该是没有问题的，所有的网页都是同一个配置，并且内网访问没有问题，内网也是通过一个reverse proxy访问的。 关闭CSRF即可
gitea-mirror commented 2026-05-05 12:42:40 -06:00
Author
Owner
Copy link

@bingzhangdai commented on GitHub (Jun 23, 2020):

@Nisekoi5 Same problem here. 我也只有这一个网页出错，但配置应该是没有问题的，所有的网页都是同一个配置，并且内网访问没有问题，内网也是通过一个reverse proxy访问的。

关闭CSRF即可

感谢提醒，但似乎是关掉 Host header validation 才行。

<!-- gh-comment-id:647988608 --> @bingzhangdai commented on GitHub (Jun 23, 2020): > > @Nisekoi5 Same problem here. 我也只有这一个网页出错，但配置应该是没有问题的，所有的网页都是同一个配置，并且内网访问没有问题，内网也是通过一个reverse proxy访问的。 > > 关闭CSRF即可 感谢提醒，但似乎是关掉 Host header validation 才行。
gitea-mirror commented 2026-05-05 12:42:41 -06:00
Author
Owner
Copy link

@youthlin commented on GitHub (Apr 7, 2021):

@Nisekoi5 Same problem here. 我也只有这一个网页出错，但配置应该是没有问题的，所有的网页都是同一个配置，并且内网访问没有问题，内网也是通过一个reverse proxy访问的。

关闭CSRF即可

感谢提醒，但似乎是关掉 Host header validation 才行。

遇到同样的问题，请问是怎么关掉这个验证的呀

<!-- gh-comment-id:814579986 --> @youthlin commented on GitHub (Apr 7, 2021): > > > @Nisekoi5 Same problem here. 我也只有这一个网页出错，但配置应该是没有问题的，所有的网页都是同一个配置，并且内网访问没有问题，内网也是通过一个reverse proxy访问的。 > > > > > > 关闭CSRF即可 > > 感谢提醒，但似乎是关掉 Host header validation 才行。 遇到同样的问题，请问是怎么关掉这个验证的呀
gitea-mirror commented 2026-05-05 12:42:41 -06:00
Author
Owner
Copy link

@flybird027 commented on GitHub (Jan 10, 2022):

登陆后 --工具--选项--webUI-- 下滑找到 【验证】 这里
取消勾选 Host header 属性验证

实测有效

<!-- gh-comment-id:1008960538 --> @flybird027 commented on GitHub (Jan 10, 2022): 登陆后 --工具--选项--webUI-- 下滑找到 【验证】 这里 取消勾选 Host header 属性验证 实测有效
gitea-mirror commented 2026-05-05 12:42:41 -06:00
Author
Owner
Copy link

@shermanx commented on GitHub (Jul 6, 2022):

openwrt+nginx也出现这个问题，请教如何解决？
frpc 0.43.0

<!-- gh-comment-id:1176099767 --> @shermanx commented on GitHub (Jul 6, 2022): openwrt+nginx也出现这个问题，请教如何解决？ frpc 0.43.0
gitea-mirror commented 2026-05-05 12:42:42 -06:00
Author
Owner
Copy link

@yikexiaoyao commented on GitHub (Mar 6, 2023):

http能正常访问，但是https显示401，页面元素加载异常
image
image
求教，怎么解决，感谢

<!-- gh-comment-id:1456300710 --> @yikexiaoyao commented on GitHub (Mar 6, 2023): http能正常访问，但是https显示401，页面元素加载异常 ![image](https://user-images.githubusercontent.com/36374114/223147650-f0ce83b0-066f-4c0f-bf0a-4a361e0ec1f2.png) ![image](https://user-images.githubusercontent.com/36374114/223148113-134c0d22-b5e8-496e-a678-740d715dc575.png) 求教，怎么解决，感谢
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
new
master
copilot/review-pull-request-5198
v0.68.1
v0.68.0
v0.67.0
v0.66.0
v0.65.0
v0.64.0
v0.63.0
v0.62.1
v0.62.0
v0.61.2
v0.61.1
v0.61.0
v0.60.0
v0.59.0
v0.58.1
v0.58.0
v0.57.0
v0.56.0
v0.55.1
v0.55.0
v0.54.0
v0.53.2
v0.53.1
v0.53.0
v0.52.3
v0.52.2
v0.52.1
v0.52.0
v0.51.3
v0.51.2
v0.51.1
v0.51.0
v0.50.0
v0.49.0
v0.48.0
v0.47.0
v0.46.1
v0.46.0
v0.45.0
v0.44.0
v0.43.0
v0.42.0
v0.41.0
v0.40.0
v0.39.1
v0.39.0
v0.38.0
v0.37.1
v0.37.0
v0.36.2
v0.36.1
v0.36.0
v0.35.1
v0.35.0
v0.34.3
v0.34.2
v0.34.1
v0.34.0
v0.33.0
v0.32.1
v0.32.0
v0.31.2
v0.31.1
v0.31.0
v0.30.0
v0.29.1
v0.29.0
v0.28.2
v0.28.1
v0.28.0
v0.27.1
v0.27.0
v0.26.0
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.1
v0.24.0
v0.23.3
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.0
v0.19.1
v0.19.0
v0.18.0
v0.17.0
v0.16.1
v0.16.0
v0.15.1
v0.15.0
v0.14.1
v0.14.0
v0.13.0
v0.12.0
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.1
v0.8.0
v0.7.0
v0.6.0
v0.5.0
v0.3.0
v0.2.0
v0.1.0
Labels
Clear labels   
In Progress

   
WIP

   
WaitingForInfo

   
bug

   
doc

   
duplicate

   
easy

   
enhancement

   
future

   
help wanted

   
invalid

   
lifecycle/stale

   
need-issue-template

   
need-usage-help

   
no plan

   
proposal

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
todo
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#1100
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?