[GH-ISSUE #4334] 能否实现一条命令生成https的端口转发链接

gitea-mirror commented

2026-05-05 14:12:11 -06:00

Owner

Copy link

Originally created by @xhzkp on GitHub (Jul 11, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4334

Describe the feature request

https://github.com/fatedier/frp/issues/4325
我上面贴子的功能需求最终用 serveo.net 实现了, 但可能是因为这个网站在国外的原因, 即便像下面命令,加了ServerAliveInterval=60参数也不能长时间稳定使用, 另外自定义二级域名或使用自己的域名也需要一些复杂的设置
ssh -o ServerAliveInterval=60 -R 80:localhost:4458 serveo.net
上面命令生成的链接类似如下, 直接就支持了https, 而且几乎就是瞬间生成的, 也不用装客户端, 只要一个ssh内置的或第三方的都行:
https://a32735b3a631882e6926fc766bbe73d8.serveo.net

serveo的操作方式的确太简单了, 直接就生成了 HTTPS的端口转发链接, 那有没有可能, 也用类似的方式, 在要公开某个服务端口的电脑的ssh中, 也执行一个操作FRPS服务端的命令, 然后也直接生成HTTPS的端口转发链接呢?

下面的链接是部署自己的seveo 服务器
https://github.com/taichunmin/docker-serveo-server

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

Originally created by @xhzkp on GitHub (Jul 11, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4334 ### Describe the feature request https://github.com/fatedier/frp/issues/4325 我上面贴子的功能需求最终用 serveo.net 实现了, 但可能是因为这个网站在国外的原因, 即便像下面命令,加了ServerAliveInterval=60参数也不能长时间稳定使用, 另外自定义二级域名或使用自己的域名也需要一些复杂的设置 ssh -o ServerAliveInterval=60 -R 80:localhost:4458 serveo.net 上面命令生成的链接类似如下, 直接就支持了https, 而且几乎就是瞬间生成的, 也不用装客户端, 只要一个ssh内置的或第三方的都行: https://a32735b3a631882e6926fc766bbe73d8.serveo.net serveo的操作方式的确太简单了, 直接就生成了 HTTPS的端口转发链接, 那有没有可能, 也用类似的方式, 在要公开某个服务端口的电脑的ssh中, 也执行一个操作FRPS服务端的命令, 然后也直接生成HTTPS的端口转发链接呢? 下面的链接是部署自己的seveo 服务器 https://github.com/taichunmin/docker-serveo-server ### 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

gitea-mirror

2026-05-05 14:12:11 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:12:14 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Aug 3, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Aug 3, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified