[GH-ISSUE #4035] SSH connection refused

gitea-mirror commented

2026-05-05 14:03:57 -06:00

Owner

Originally created by @Yuyang-Song on GitHub (Feb 29, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4035

Describe the feature request

When I am following the step to establish the frp connection, I find the client and server's nohup.out are like this:

2024/02/29 21:26:50 [I] [root.go:105] frps uses config file: frps.toml
2024/02/29 21:26:50 [I] [service.go:225] frps tcp listen on 0.0.0.0:7000
2024/02/29 21:26:50 [I] [root.go:114] frps started successfully
2024/02/29 21:26:50 [I] [service.go:338] dashboard listen on 0.0.0.0:7500

2024/02/29 13:28:08 [I] [root.go:142] start frpc service for config file [frpc.toml]
2024/02/29 13:28:08 [I] [service.go:287] try to connect to server...
2024/02/29 13:28:08 [I] [service.go:279] [00c4a11576340766] login to server success, get run id [00c4a11576340766]

they are not like the features I saw in the blogs like :

# tail -f nohup.out 
2018/09/14 05:33:15 [I] [service.go:130] frps tcp listen on 0.0.0.0:7000
2018/09/14 05:33:15 [I] [root.go:207] Start frps success
2018/09/14 05:49:47 [I] [service.go:130] frps tcp listen on 0.0.0.0:7000
2018/09/14 05:49:47 [I] [root.go:207] Start frps success
2018/09/14 06:28:59 [I] [service.go:319] client login info: ip [125.71.219.33:37092] version [0.21.0] hostname [] os [linux] arch [amd64]
2018/09/14 06:28:59 [I] [proxy.go:217] [93eec0dde173fc68] [ssh] tcp proxy listen port [6000]
2018/09/14 06:28:59 [I] [control.go:335] [93eec0dde173fc68] new proxy [ssh] success

This makes my ssh remote connnection refused.
How can I deal with this Problem?

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 @Yuyang-Song on GitHub (Feb 29, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4035 ### Describe the feature request When I am following the step to establish the frp connection, I find the client and server's nohup.out are like this: ``` 2024/02/29 21:26:50 [I] [root.go:105] frps uses config file: frps.toml 2024/02/29 21:26:50 [I] [service.go:225] frps tcp listen on 0.0.0.0:7000 2024/02/29 21:26:50 [I] [root.go:114] frps started successfully 2024/02/29 21:26:50 [I] [service.go:338] dashboard listen on 0.0.0.0:7500 ``` ``` 2024/02/29 13:28:08 [I] [root.go:142] start frpc service for config file [frpc.toml] 2024/02/29 13:28:08 [I] [service.go:287] try to connect to server... 2024/02/29 13:28:08 [I] [service.go:279] [00c4a11576340766] login to server success, get run id [00c4a11576340766] ``` they are not like the features I saw in the blogs like : ``` # tail -f nohup.out 2018/09/14 05:33:15 [I] [service.go:130] frps tcp listen on 0.0.0.0:7000 2018/09/14 05:33:15 [I] [root.go:207] Start frps success 2018/09/14 05:49:47 [I] [service.go:130] frps tcp listen on 0.0.0.0:7000 2018/09/14 05:49:47 [I] [root.go:207] Start frps success 2018/09/14 06:28:59 [I] [service.go:319] client login info: ip [125.71.219.33:37092] version [0.21.0] hostname [] os [linux] arch [amd64] 2018/09/14 06:28:59 [I] [proxy.go:217] [93eec0dde173fc68] [ssh] tcp proxy listen port [6000] 2018/09/14 06:28:59 [I] [control.go:335] [93eec0dde173fc68] new proxy [ssh] success ``` This makes my ssh remote connnection refused. How can I deal with this Problem? ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [X] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:03:57 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:04:00 -06:00

Author

Owner

@xqzr commented on GitHub (Mar 1, 2024):

在防火墙开放 TCP 6000

@xqzr commented on GitHub (Mar 1, 2024): 在防火墙开放 TCP 6000

gitea-mirror commented

2026-05-05 14:04:01 -06:00

Author

Owner

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