[GH-ISSUE #3124] SFTP does not work over frp

gitea-mirror commented

2026-05-05 13:36:51 -06:00

Owner

Originally created by @Nuckerr on GitHub (Oct 10, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3124

Bug Description

I have a server, with sftp. I can connect fine using it's ip, however if I put it under frp with this config;

[code_server]
type = tcp
local_ip = 192.168.0.148
local_port = 22
remote_port = 2007

it gives me
Permission denied, please try again.

frpc Version

0.43.0

frps Version

0.39.1

System Architecture

linux/amd64

Configurations

[code_server]
type = tcp
local_ip = 192.168.0.148
local_port = 22
remote_port = 2007

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 @Nuckerr on GitHub (Oct 10, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3124 ### Bug Description I have a server, with sftp. I can connect fine using it's ip, however if I put it under frp with this config; ``` [code_server] type = tcp local_ip = 192.168.0.148 local_port = 22 remote_port = 2007 ``` it gives me `Permission denied, please try again.` ### frpc Version 0.43.0 ### frps Version 0.39.1 ### System Architecture linux/amd64 ### Configurations ``` [code_server] type = tcp local_ip = 192.168.0.148 local_port = 22 remote_port = 2007 ``` ### 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 - [ ] Others

gitea-mirror

2026-05-05 13:36:51 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:36:54 -06:00

Author

Owner

@Becods commented on GitHub (Oct 11, 2022):

Permission denied, please try again indicates that the error occurred on your sftp server and has nothing to do with frp.

@Becods commented on GitHub (Oct 11, 2022): `Permission denied, please try again` indicates that the error occurred on your sftp server and has nothing to do with frp.

gitea-mirror commented

2026-05-05 13:36:55 -06:00

Author

Owner

@Nuckerr commented on GitHub (Oct 11, 2022):

Well the password is definitely right. And I can sftp when using my internal ip inside the network, no issues. Only through frp does this error occur

@Nuckerr commented on GitHub (Oct 11, 2022): Well the password is definitely right. And I can sftp when using my internal ip inside the network, no issues. Only through frp does this error occur

gitea-mirror commented

2026-05-05 13:36:57 -06:00

Author

Owner

@Elara6331 commented on GitHub (Oct 13, 2022):

Is it possible that your SFTP server is configured to only accept internal IPs?

@Elara6331 commented on GitHub (Oct 13, 2022): Is it possible that your SFTP server is configured to only accept internal IPs?

gitea-mirror commented

2026-05-05 13:36:58 -06:00

Author

Owner

@Nuckerr commented on GitHub (Oct 13, 2022):

I think that is most likely, how do I configure this?

@Nuckerr commented on GitHub (Oct 13, 2022): I think that is most likely, how do I configure this?

gitea-mirror commented

2026-05-05 13:36:58 -06:00

Author

Owner

@Nuckerr commented on GitHub (Oct 18, 2022):

@Arsen6331?

@Nuckerr commented on GitHub (Oct 18, 2022): @Arsen6331?

gitea-mirror commented

2026-05-05 13:36:59 -06:00

Author

Owner

@Elara6331 commented on GitHub (Oct 18, 2022):

That depends on which SFTP server you're using. Look at the docs of whichever one you're using.

@Elara6331 commented on GitHub (Oct 18, 2022): That depends on which SFTP server you're using. Look at the docs of whichever one you're using.

gitea-mirror commented

2026-05-05 13:36:59 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 18, 2022):

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

@github-actions[bot] commented on GitHub (Nov 18, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.