[GH-ISSUE #4506] Port unavailable when port is in fact available #3558

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

Originally created by @hykilpikonna on GitHub (Oct 23, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4506

Bug Description

image

frpc Version

0.61.0

frps Version

0.61.0

System Architecture

linux/amd64

Configurations

bindPort = 999
bindAddr = "51.222.176.204"

auth.method = "token"
auth.token = "..."

allowPorts = [
    {single = 80}
]
serverAddr = "51.222.176.204"
serverPort = 999

[auth]
token = "..."

[[proxies]]
name = "aquadx-allnet"
type = "tcp"
localIP = "127.0.0.1"
localPort = 81
remotePort = 80

Logs

2024-10-23 06:47:57.255 [W] [server/control.go:394] [6ffb8f01cd709bbc] new proxy [aquadx-allnet] type [tcp] error: port unavailable

Steps to reproduce

  1. Have multiple IPv4 on your server
  2. Serve port 80 on one IPv4
  3. Bind frps to another IPv4
  4. Try to create a tunnel that serve on port 80 on this other IPv4 using frps
  5. Observe error

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @hykilpikonna on GitHub (Oct 23, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4506 ### Bug Description ![image](https://github.com/user-attachments/assets/a29faf47-8b5e-4a8b-9f26-995d56ba293d) ### frpc Version 0.61.0 ### frps Version 0.61.0 ### System Architecture linux/amd64 ### Configurations ```toml bindPort = 999 bindAddr = "51.222.176.204" auth.method = "token" auth.token = "..." allowPorts = [ {single = 80} ] ``` ```toml serverAddr = "51.222.176.204" serverPort = 999 [auth] token = "..." [[proxies]] name = "aquadx-allnet" type = "tcp" localIP = "127.0.0.1" localPort = 81 remotePort = 80 ``` ### Logs 2024-10-23 06:47:57.255 [W] [server/control.go:394] [6ffb8f01cd709bbc] new proxy [aquadx-allnet] type [tcp] error: port unavailable ### Steps to reproduce 1. Have multiple IPv4 on your server 2. Serve port 80 on one IPv4 3. Bind frps to another IPv4 4. Try to create a tunnel that serve on port 80 on this other IPv4 using frps 5. Observe error ### Affected area - [ ] Docs - [X] 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:17:04 -06:00
Author
Owner

@solisinvictum commented on GitHub (Oct 23, 2024):

have exact the same issue after updating to 0.6.1.

found now way to fix this. even as root, with no single port open, i get this error on both end (server and client).

my "fix" is now, to stay on 0.6.0

<!-- gh-comment-id:2432304658 --> @solisinvictum commented on GitHub (Oct 23, 2024): have exact the same issue after updating to 0.6.1. found now way to fix this. even as root, with no single port open, i get this error on both end (server and client). my "fix" is now, to stay on 0.6.0
Author
Owner

@github-actions[bot] commented on GitHub (Nov 14, 2024):

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

<!-- gh-comment-id:2475106631 --> @github-actions[bot] commented on GitHub (Nov 14, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d 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#3558
No description provided.