Skip to content
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

如何强制HTTPS请求的端口转发 #4325

Open
3 of 11 tasks
xhzkp opened this issue Jul 9, 2024 · 4 comments
Open
3 of 11 tasks

如何强制HTTPS请求的端口转发 #4325

xhzkp opened this issue Jul 9, 2024 · 4 comments

Comments

@xhzkp
Copy link

xhzkp commented Jul 9, 2024

Describe the feature request

刚上手FRP, 对有些配置看了相关文档或教程后还是不太理解, 请求路过大佬指点江山! 非常感谢!

问题描述如下:

公网的FPRS服务端配置FRPS.toml如下:
bindPort = 7000


内网的FRPC客户端配置FRPC.toml如下:
serverAddr = "1.2.3.4"
serverPort = 7000

[[proxies]]
name = "Port 2222 Server"
type = "tcp"
localIP = "192.168.1.2"
localPort = 2222
remotePort = 6000


这里假设服务器IP1.2.3.4绑定的域名是1234.com
外网通过下面的链接可以成功访问到内网192.168.1.2主机的2222端口
http:https://1234.com:6000

但是我想强制使用https来访问2222端口, 即:
A. 当使用 http:https://1234.com:6000 访问时, 不需要对这个访问进行响应
B. 只有使用 https:https://1234.com:6000 访问时, 内网192.168.1.2主机的2222端口才能接收响应

假设我已经有 1234.com域名的https证书, 我需要怎样调整客户端或服务器的配置文件? 感谢

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
@superzjg
Copy link

superzjg commented Jul 9, 2024

@xhzkp
Copy link
Author

xhzkp commented Jul 9, 2024

https://gofrp.org/zh-cn/docs/examples/https2http/

感谢大佬支招, 我看这个配置是在客户端配置的, 把证书都放在了客户端, 这个实在不方便, 也非常不现实...
不能在服务端配置吗? 如果不能在服务端实现我的需求, 那也只能放弃了...
我的想法是, 拷贝客户端到任意一台电脑上, 然后我就能访问这台电脑, 这台电脑做一下基本的token认证就行了, 但是访问要用https访问

@JsonSong89
Copy link

自己用nginx再转一下吧
说实话我也觉得客户端配置证书很奇怪

@xhzkp
Copy link
Author

xhzkp commented Jul 9, 2024

自己用nginx再转一下吧 说实话我也觉得客户端配置证书很奇怪

现在用 serveo.net 直接支持https

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants