[GH-ISSUE #4900] SSh tunnel gateway fails to connect with proxy bind address given 127.0.0.1

gitea-mirror commented

2026-05-05 14:28:14 -06:00

Owner

Originally created by @chiragmv on GitHub (Jul 26, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4900

Bug Description

When using ssh tunnel gateway and proxy bind to localhost, ssh client fails to connect.

frpc Version

dbclient as ssh client

frps Version

0.63.0

System Architecture

dbclient on armv7 frps on x86_64 Linux

Configurations

bindAddr = "0.0.0.0"
bindPort = 62000
sshTunnelGateway.bindPort = 60000
proxyBindAddr = "127.0.0.1"
log.level = "trace"

Logs

No logs on FRPS

dbclient:

dbclient -y -R :80:127.0.0.1:80 v0@x.x.x.x -p 60000 tcp --remote_port XXXX --proxy_name abc

          dbclient: Connection to v0@x.x.x.x:60000 exited: Connect failed: Connection refused

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 @chiragmv on GitHub (Jul 26, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4900 ### Bug Description When using ssh tunnel gateway and proxy bind to localhost, ssh client fails to connect. ### frpc Version dbclient as ssh client ### frps Version 0.63.0 ### System Architecture dbclient on armv7 frps on x86_64 Linux ### Configurations bindAddr = "0.0.0.0" bindPort = 62000 sshTunnelGateway.bindPort = 60000 proxyBindAddr = "127.0.0.1" log.level = "trace" ### Logs No logs on FRPS dbclient: dbclient -y -R :80:127.0.0.1:80 v0@x.x.x.x -p 60000 tcp --remote_port XXXX --proxy_name abc dbclient: Connection to v0@x.x.x.x:60000 exited: Connect failed: Connection refused ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [x] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:28:14 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 14:28:18 -06:00

Author

Owner

@fatedier commented on GitHub (Jul 28, 2025):

You should check whether frps is listening on port 60000, and then verify if the network environment is functioning properly.

@fatedier commented on GitHub (Jul 28, 2025): You should check whether frps is listening on port 60000, and then verify if the network environment is functioning properly.

gitea-mirror commented

2026-05-05 14:28:19 -06:00

Author

Owner

@chiragmv commented on GitHub (Jul 28, 2025):

Yes It is, just comment proxyBindAddr = "127.0.0.1" and everything works fine.

@chiragmv commented on GitHub (Jul 28, 2025): Yes It is, just comment proxyBindAddr = "127.0.0.1" and everything works fine.

gitea-mirror commented

2026-05-05 14:28:20 -06:00

Author

Owner

@chiragmv commented on GitHub (Jul 28, 2025):

and when I use bindport (62000) and connect frpc client, everything works fine

problem is when use sshTunnelgateway with local proxyBindAddr , ssh client cannot connect to frps

@chiragmv commented on GitHub (Jul 28, 2025): and when I use bindport (62000) and connect frpc client, everything works fine problem is when use sshTunnelgateway with local proxyBindAddr , ssh client cannot connect to frps