-
I've been having this issue where the SFTP daemon built in SFTPGo consistently keeps dropping connections when a file transfer occurs, but not when just browsing through the files. Due to this, I can't perform any file transfers between client and server over SFTP. File transfers over WebDAV work fine. SSHFS-Win Manager results in:
While the server shows the following log messages:
If a more detailed log is needed, I'm willing to provide. I'd also like to note that the SFTPGo server is behind a proxy. I'm also not 100% sure it's SFTPGo specific, although the normal OpenSSH server SFTP subsystem seems to be fine. So really any advice would be appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Turns out changing the port from 21 worked, although I'm not to clear on why. Especially considering it was able to display directory content change paths just fine. I don't believe there were any other services using the port. There were also no errors on reserving port 21 on the server side of things. This may have to do with ports numbered less than 1024 being considered privileged ports? But again, nothing on the server side when opening the port. The router did change before it stopped working, but I couldn't see why this would explain the issue. If anyone has an explanation, I'd appreciate it, I'll leave the question open for a bit longer, otherwise, this question does have a solution, despite being incomplete. |
Beta Was this translation helpful? Give feedback.
-
You have a transfer stalled since 17 minutes. The issue seems unrelated to SFTPGo. Anyway, I no longer provide free support, check the support policy. This is the only way to prevent SFTPGo from being discontinued/archived and it is necessary because most of people just ask and never give anything back spontaneously. Thanks for understanding |
Beta Was this translation helpful? Give feedback.
Turns out changing the port from 21 worked, although I'm not to clear on why. Especially considering it was able to display directory content change paths just fine. I don't believe there were any other services using the port. There were also no errors on reserving port 21 on the server side of things. This may have to do with ports numbered less than 1024 being considered privileged ports? But again, nothing on the server side when opening the port. The router did change before it stopped working, but I couldn't see why this would explain the issue. If anyone has an explanation, I'd appreciate it, I'll leave the question open for a bit longer, otherwise, this question does have a soluti…