[GH-ISSUE #5302] [Feature Request] #4087

Open
opened 2026-05-05 14:35:12 -06:00 by gitea-mirror · 0 comments
Owner

Originally created by @liuxing1981 on GitHub (May 1, 2026).
Original GitHub issue: https://github.com/fatedier/frp/issues/5302

Describe the feature request

I try to expose the 1883 port via frpc for mqtt broker in Server B with frp 0.68.
And i have started the frps in Server A, of course the 1883 port is listening in Server A.
But when the mqtt client which is running in Iot device try to create a connection to 1883 port in Server A,
the connection always disconnect by frps service. The Iot device received the Fin package from Server A.
Could you please show me how to config the frp for keeping the connection alive with mqtt?

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 @liuxing1981 on GitHub (May 1, 2026). Original GitHub issue: https://github.com/fatedier/frp/issues/5302 ### Describe the feature request I try to expose the 1883 port via frpc for mqtt broker in Server B with frp 0.68. And i have started the frps in Server A, of course the 1883 port is listening in Server A. But when the mqtt client which is running in Iot device try to create a connection to 1883 port in Server A, the connection always disconnect by frps service. The Iot device received the Fin package from Server A. Could you please show me how to config the frp for keeping the connection alive with mqtt? ### 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 - [x] Extensions - [ ] Others
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#4087
No description provided.