-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use PASV when EPSV was used before. #791
Comments
What're the error/logs that you see, when trying to switch from |
So, found the error. I was using mod_proxy. The error comes from my backend. I forced ProFTPd's mod_proxy to always use PASV, regardless what the client wants, and it's fine now. |
Glad to hear that you found the cause and the fix. Would you be willing to provide some example logs, from the client- and server-side of things, so that I can add those logs as examples, in docs, of symptoms other users might see, and how to address them? |
Unfortunately I solved it a week ago, and lost the logs. ;( The backend server I'm using doesn't support EPSV. It's a .NET library called This library, in default operation, attempts to open an EPSV connection, and then when that fails, attempts to move down the list trying different modes. ProFTPD was passing this all back to the backend. The backend was rejecting the EPSV. And then when the client next tried PASV, it was throwing an error about attempting to switch. So, to shield all that, I've forced ProFTPd's mod_proxy to always use PASV, through |
OK, thanks for the info! I'll see if there's a way to make Filed this for tracking as Castaglia/proftpd-mod_proxy#146 |
Oh wow! Thanks! It took me a couple days to work this out, so that might save others the trouble. You rock. |
I'm trying to figure out a way to solve this. It seems to be a limit in ProFTPd, that you can't switch from EPSV to PASV. However, I have a client library that tries to use EPSV, and if that fails, switches to PASV on it's own and tries that instead.
Why would changes to this be prevented? Just a limitation?
The text was updated successfully, but these errors were encountered: