-
-
Notifications
You must be signed in to change notification settings - Fork 13.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
【frp-0.14.1】两个子域名和两个服务不能一对一的正确访问 #628
Comments
本地无法复现,建议更新到最新版本再测试下吧。 |
更新到最新版本重新测试后发现是谷歌浏览器的问题。IE上测试访问均正常,火狐Ctrl+F5强制刷新后域名可正常对应服务,谷歌浏览器基本没戏。 |
我也遇到类似的问题 多个子域名访问对不上 访问 a.xxx.net 有时候会出现 b.xxx.net 的内容 |
@fatedier 我的网站都是使用的 HTTP2,而 HTTP2 有多路复用,通过抓包,相同IP不同域名浏览器使用了同一个 TCP 连接,应该是 frp 不支持 HTTP2。(frp-0.25.0 目前测试结果一样) |
发现和 #913 问题相同 |
查阅到的连接复用相关资料 Connection Reuse,How Connection Reuse works on multiple browsers。 我的网站使用的是同一个通配域名证书,都配置了 HTTP2,符合 rfc7540 里所说的 reuse 情况。 找到的解决方法: if you do not want connection sharing to happen, have a different IP address and/or ensure no overlaps in certificates, 我把通配域名证书改成单域名证书问题解决,非 frp 的问题。 |
果然,按照您说的,把通配域名证书改成单域名证书,问题就解决了,解决困扰了我很久的问题,非常感谢! |
Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly.
(为了节约时间,提高处理问题的效率,不按照格式填写的 issue 将会直接关闭。)
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
What version of frp are you using (./frpc -v or ./frps -v)?
frps 和frpc的版本都是0.14.1
What operating system and processor architecture are you using (
go env
)?Configures you used:
在云服务器上部署frps和blog服务,在内网机器上部署gitlab服务。
实现最后能使用两个子域名分别访问两个服务。
frps配置
frpc配置1--blog服务
frpc配置2--gitlab服务
nginx配置
Steps to reproduce the issue:
Describe the results you received:
访问gitlab.example.com实际上访问的是blog服务。
Describe the results you expected:
github.example.com应该无法访问。
Additional information you deem important (e.g. issue happens only occasionally):
Can you point out what caused this issue (optional)
The text was updated successfully, but these errors were encountered: