Results 57 comments of

![CM6PHS7AGGJPN31Y2DI83MS](https://user-images.githubusercontent.com/35525491/187059237-a14750b5-52ad-48fa-b688-7ce6fd5b5fce.png)

看上去在监听ipv6实际上有可能是双栈都在监听 还是不行的话自行谷歌怎么关掉ipv6

![CM6PHS7AGGJPN31Y2DI83MS](https://user-images.githubusercontent.com/35525491/201261596-4bb2d949-57c2-4054-90fa-5905874e079e.png)

莫名其妙 请补充一下使用场景 前端http默认80 https默认443 这个不用管 非标的话还要绑域名,是不是有点多此一举 tcp映射后端nginx把http和https配置写一块就行了

Why do you propose to do this? What is the motivation for doing it? What will happen when the proposal is implemented?

https://github.com/fatedier/frp/issues/1570 > v0.31.0 已支持服务端插件,可以自行实现。 https://github.com/fatedier/frp/issues/3033 > Planned in frp v2, we want to support multiple configure registry such as static file, remote url, etc.

Please make sure that the port you are trying on has a corresponding service listening on the frpc side.

理论上来讲,当proxy的端口关闭的时候,访问端将无法主动连接至服务端,这时只能通过某种方式重新打开端口(listen),例如hook 一般情况下并不重要关闭端口,除非是为了安全或者端口不够用

https://github.com/fatedier/frp/issues/1570 > v0.31.0 已支持服务端插件,可以自行实现。 https://github.com/fatedier/frp/issues/3033 > Planned in frp v2, we want to support multiple configure registry such as static file, remote url, etc.

不能 请考虑使用端口转发