[GH-ISSUE #3154] 服务端开放客户端远程端口无法连接

gitea-mirror commented

2026-05-05 13:37:46 -06:00

Owner

Copy link

Originally created by @wxjeek on GitHub (Oct 31, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3154

Bug Description

我搭建了一个cs端，客户端注册到服务端是ok的，服务端也监听了客户端配置的远程端口，服务端本地连接客户端网络端口是ok的，但是我把服务端的远程端口开放，其他客户端无法连接此监听端口

frpc Version

0.45.0

frps Version

0.45.0

System Architecture

clinet windows/amd64 & server linux/amd64

Configurations

主页简单配置

Logs

No response

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @wxjeek on GitHub (Oct 31, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3154 ### Bug Description 我搭建了一个cs端，客户端注册到服务端是ok的，服务端也监听了客户端配置的远程端口，服务端本地连接客户端网络端口是ok的，但是我把服务端的远程端口开放，其他客户端无法连接此监听端口 ### frpc Version 0.45.0 ### frps Version 0.45.0 ### System Architecture clinet windows/amd64 & server linux/amd64 ### Configurations 主页简单配置 ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [X] Others

gitea-mirror

2026-05-05 13:37:46 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:37:49 -06:00

Author

Owner

Copy link

@Becods commented on GitHub (Oct 31, 2022):

大部分需要gslt的服务端的连接ip必须是向gslt注册时使用的ip

所以，frp不兼容此类游戏服务器的穿透，也不可能去适配

@Becods commented on GitHub (Oct 31, 2022): 大部分需要gslt的服务端的连接ip必须是向gslt注册时使用的ip 所以，frp不兼容此类游戏服务器的穿透，也不可能去适配 ![CM6PHS7AGGJPN31Y2DI83MS](https://user-images.githubusercontent.com/35525491/199038452-464e5499-ed44-492a-b1c4-c0440483d388.png)

gitea-mirror commented

2026-05-05 13:37:49 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Dec 1, 2022):

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

@github-actions[bot] commented on GitHub (Dec 1, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified