-
Notifications
You must be signed in to change notification settings - Fork 20
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
Refreshing/navigating directories 7 times causes failures #187
Comments
This appears to be because the passive port pool is exhausted. Increasing the size of the passive port pool to 50 it takes much longer to happen. Attempting this with vsftpd I couldn't make it happen spamming refresh with only 10 passive ports assigned so this seems to be undesired/unexpected behavior. It seems we need to be reusing these ports or releasing them so they can be reused by a new connection. These issues seem to be related: |
Off topic: This project is awesome btw. I love having auth over REST to my webserver and the new |
Thank you @paul-hansen for the detailed information (and the kind words) |
Simply refreshing a directory or navigating to a different directory quickly 7 times causes failures. Repeated additional refreshes will mostly fail but some will randomly will succeed.
I tired this with Dolphin (KDE's file manager) and the failures exhibit as a "Loading canceled" screen.
It happens in FileZilla as well, though filezilla caches directory listings so you run into it less often.
FileZilla logs this when the requests fail:
unFTP logs this when the requests fail:
When they succeed this is logged by unFTP:
I tried hosting the same directory using vsftpd and did not have this problem.
Here's how I'm running unftp:
The text was updated successfully, but these errors were encountered: