[GH-ISSUE #4215] Server can bind to 80 but client failed to connect with it

gitea-mirror commented

2026-05-05 14:08:27 -06:00

Owner

Originally created by @SoftCoderCritic on GitHub (May 12, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4215

Bug Description

here is the simple config for testing

server:

bindPort = 80

client:

serverAddr = server ip
serverPort = 80

[[proxies]]
name = "ssh"
type = "tcp"
localIP = "127.0.0.1"
localPort = 22
remotePort = 12552

I can successfully use port 1080, and any port greater than 1024 without any issues, but I'm unable to use common ports like 80 and 443. The firewall accepts all incoming ports, and when I start the server with sudo, it successfully binds to port 80. However, when I start the client, it continuously tries to connect to the server. If I switch to a different port, the connection is established immediately.

Here are the relevant logs:

[sub/root.go:142] Starting frpc service with the configuration file [./frpc.toml].
[client/service.go:294] Attempting to connect to server...
Could there be any configuration I might have missed? I'm open to testing any suggestions. Any help would be greatly appreciated.

frpc Version

latest

frps Version

latest

System Architecture

linux/amd64, mac/arm64

Configurations

server:

bindPort = 80

client:

serverAddr = server ip
serverPort = 80

[[proxies]]
name = "ssh"
type = "tcp"
localIP = "127.0.0.1"
localPort = 22
remotePort = 12552

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 @SoftCoderCritic on GitHub (May 12, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4215 ### Bug Description here is the simple config for testing server: ``` bindPort = 80 ``` client: ``` serverAddr = server ip serverPort = 80 [[proxies]] name = "ssh" type = "tcp" localIP = "127.0.0.1" localPort = 22 remotePort = 12552 ``` I can successfully use port 1080, and any port greater than 1024 without any issues, but I'm unable to use common ports like 80 and 443. The firewall accepts all incoming ports, and when I start the server with sudo, it successfully binds to port 80. However, when I start the client, it continuously tries to connect to the server. If I switch to a different port, the connection is established immediately. Here are the relevant logs: [sub/root.go:142] Starting frpc service with the configuration file [./frpc.toml]. [client/service.go:294] Attempting to connect to server... Could there be any configuration I might have missed? I'm open to testing any suggestions. Any help would be greatly appreciated. ### frpc Version latest ### frps Version latest ### System Architecture linux/amd64, mac/arm64 ### Configurations server: ``` bindPort = 80 ``` client: ``` serverAddr = server ip serverPort = 80 [[proxies]] name = "ssh" type = "tcp" localIP = "127.0.0.1" localPort = 22 remotePort = 12552 ``` ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [X] Others

gitea-mirror

2026-05-05 14:08:27 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:08:30 -06:00

Author

Owner

@xqzr commented on GitHub (May 12, 2024):

ISP 可能会阻止 80 端口传入

@xqzr commented on GitHub (May 12, 2024): ISP 可能会阻止 80 端口传入

gitea-mirror commented

2026-05-05 14:08:31 -06:00

Author

Owner

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