[GH-ISSUE #4859] 部分服务会错误的绑定到随机端口 #3832

Closed
opened 2026-05-05 14:27:05 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @xiedidan on GitHub (Jul 1, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4859

Bug Description

hi,
frp is really good, I used it for years. However I got some problems with v0.63.0

According to my configs, frps should listen to 15433 for pgsql, and listen to 50002 for doris, but it listen to random ports:

Image

Any way to fix this?

frpc Version

0.63.0

frps Version

0.63.0

System Architecture

linux/amd64

Configurations

frpc.ini:

[common]
server_addr = 123.456.789.111
server_port = 7000
token = 12345

[dinky]
type = tcp
local_port = 8888
remote_port = 8888

[ds]
type = tcp
local_port = 12345
remote_port = 12345

[pgsql]
type = tcp
local_ip = 127.0.0.1
local_port = 5432
remote_port = 15433

[doris]
type = tcp
local_ip = 127.0.0.1
local_port = 9030
remote_port = 50002

[ssh]
type = tcp
local_port = 22
remote_port = 6125

frps.ini:

[common]
bind_port = 7000

dashboard_port = 7500
dashboard_user = admin
dashboard_pwd = 12345
token = 12345

log_file = ./frps.log
log_level = info
log_max_days = 3

Logs

No response

Steps to reproduce

  1. ./frpc -c ./frpc.ini
  2. ./frps -c ./frps.ini
  3. visit server:7500

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @xiedidan on GitHub (Jul 1, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4859 ### Bug Description hi, frp is really good, I used it for years. However I got some problems with v0.63.0 According to my configs, frps should listen to 15433 for pgsql, and listen to 50002 for doris, but it listen to random ports: ![Image](https://github.com/user-attachments/assets/4bbf6d1e-eabd-4dec-b70d-dfec484b8e76) Any way to fix this? ### frpc Version 0.63.0 ### frps Version 0.63.0 ### System Architecture linux/amd64 ### Configurations frpc.ini: ``` [common] server_addr = 123.456.789.111 server_port = 7000 token = 12345 [dinky] type = tcp local_port = 8888 remote_port = 8888 [ds] type = tcp local_port = 12345 remote_port = 12345 [pgsql] type = tcp local_ip = 127.0.0.1 local_port = 5432 remote_port = 15433 [doris] type = tcp local_ip = 127.0.0.1 local_port = 9030 remote_port = 50002 [ssh] type = tcp local_port = 22 remote_port = 6125 ``` frps.ini: ``` [common] bind_port = 7000 dashboard_port = 7500 dashboard_user = admin dashboard_pwd = 12345 token = 12345 log_file = ./frps.log log_level = info log_max_days = 3 ``` ### Logs _No response_ ### Steps to reproduce 1. ./frpc -c ./frpc.ini 2. ./frps -c ./frps.ini 3. visit server:7500 ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [x] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 14:27:06 -06:00
Author
Owner

@superzjg commented on GitHub (Jul 2, 2025):

Please test the INI-to-TOML conversion and validate the output.

<!-- gh-comment-id:3026107776 --> @superzjg commented on GitHub (Jul 2, 2025): Please test the INI-to-TOML conversion and validate the output.
Author
Owner

@github-actions[bot] commented on GitHub (Jul 17, 2025):

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

<!-- gh-comment-id:3081969817 --> @github-actions[bot] commented on GitHub (Jul 17, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
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#3832
No description provided.