mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #3151] https2http #2526
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#2526
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @amDosion on GitHub (Oct 28, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3151
Bug Description
[W] [control.go:175] [ab1436d24e82fa3a] [plugin_https2http] start error: proxy [plugin_https2http] domain conf check error: custom domain [abc.abc.com] should not belong to subdomain_host [abc.com]
[common]
server_addr=abc.com
token=123456
server_port = 5443
[plugin_https2http]
type=https
custom_domains=abc.abc.com
plugin=https2http
plugin_local_addr=192.168.50.7:8088 我需要转发的ip和端口
plugin_tls_crt_path=./mnt/user/frpc/lspon/abc.cert Lets Encrypt机构X3签发的
plugin_tls_key_path=./mnt/user/frpc/lspon/abc.key Lets Encrypt机构X3签发的
plugin_host_header_rewrite=192.168.50.7
plugin_header_X-From-Where=frp
无论我们怎么修改始终会报错，或者报错证书路径不存在。
如果可以，希望得到大佬的回应，同时也我给大佬发了邮件，希望能付费远程帮忙解决.
frpc Version
0.44
frps Version
0.44
System Architecture
linux/amd64
Configurations
[common]
server_addr=abc.com
token=123456
server_port = 5443
[plugin_https2http]
type=https
custom_domains=abc.abc.com
plugin=https2http
plugin_local_addr=192.168.50.7:8088 我需要转发的ip和端口
plugin_tls_crt_path=./mnt/user/frpc/lspon/abc.cert Lets Encrypt机构X3签发的
plugin_tls_key_path=./mnt/user/frpc/lspon/abc.key Lets Encrypt机构X3签发的
plugin_host_header_rewrite=192.168.50.7
plugin_header_X-From-Where=frp
Logs
[W] [control.go:175] [ab1436d24e82fa3a] [plugin_https2http] start error: proxy [plugin_https2http] domain conf check error: custom domain [abc.abc.com] should not belong to subdomain_host [abc.com]
Steps to reproduce
...
Affected area
@Becods commented on GitHub (Oct 28, 2022):
frps不要开启subdomain
@amDosion commented on GitHub (Oct 28, 2022):
大佬，你好，我后面的也删除了，但是还是不行. 实在是不知道咋回事.
frps在国外服务器上，所有的端口全部放行了，
192.168.50.7 是本地的网站，同时FRPC, 也在本地，不知道是证书不支持，还是什么原因, 我看你github的说明是,crt证书，但是我这个是cert，证书的服务商是Let's Encrypt 提供的
------------------ 原始邮件 ------------------
发件人: "fatedier/frp" @.>;
发送时间: 2022年10月28日(星期五) 晚上9:03
@.>;
@.@.>;
主题: Re: [fatedier/frp] https2http (Issue #3151)
frps不要开启subdomain
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
@superzjg commented on GitHub (Nov 2, 2022):
把证书扩展名改成crt试一下，或者调试时换一个证书试一下，比如使用openssl自签名证书。
把subdomain先关闭。
把以下两句先注释掉，我发现有些web不需要用这两句：
plugin_host_header_rewrite=192.168.50.7
plugin_header_X-From-Where=frp
@amDosion commented on GitHub (Nov 2, 2022):
已经找到解决办法了，
[lsky.lspon.com]
type = https
custom_domains = lsky.lspon.com
接下来的配置是支持 https 的重点配置
配置插件，将 https 请求转换成 http 请求后再发送给本地 Web 服务程序
plugin = https2http
转换成 http 后，发送到本机的 10000 端口
plugin_local_addr = 192.168.50.7:17900
指定成你在前面部分导出的证书的路径
plugin_crt_path = ./lspon.cert
plugin_key_path = ./lspon.key
frps在本机穿透可能是 frp 的 Bug？这里必须写成 127.0.0.1
#plugin_host_header_rewrite = 192.168.50.7
指定代理方式为 frp
#plugin_header_X-From-Where = frp
[lsky]
type = http
local_ip = 192.168.50.7
local_port = 17900
custom_domains = lsky.lspon.com
有些网站要同时开启http的穿透， 这样https才会正常， 估计是bug。
------------------ 原始邮件 ------------------
发件人: "fatedier/frp" @.>;
发送时间: 2022年11月2日(星期三) 中午12:27
@.>;
@.@.>;
主题: Re: [fatedier/frp] https2http (Issue #3151)
把证书扩展名改成crt试一下，或者调试时换一个证书试一下，比如使用openssl自签名证书。
把subdomain先关闭。
把以下两句先注释掉，我发现有些web不需要用这两句：
plugin_host_header_rewrite=192.168.50.7
plugin_header_X-From-Where=frp
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
@github-actions[bot] commented on GitHub (Dec 3, 2022):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.