-
Notifications
You must be signed in to change notification settings - Fork 18
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
Timeouts on LISTing #256
Comments
Also attaching paranooid log:
|
Can you configure a |
@Castaglia pls see below:
|
Thanks. Would it be possible to also get the ProFTPD debug logging, debug level 10, from the proxy, when this happens? I have a suspicion of what's happening, and am hoping that the debug logging (in combination with the ProxyLog) can provide more details. |
Hi @Castaglia, The problem happened when reading folder: /httpdocs/admin/webfonts Below extract of the log with error
And below are logs from proxy from the same time as logs above:
|
Hi @Castaglia , Thank you |
adding also logs from latests PROFTPD version with the latest PROXY version logs |
From the logs, we see that the backend FTP server is using a private IP address (192.168.50.152). We also see, in the logs, that the proxy is using a private IP address for frontend data transfers (192.168.50.105). The question is: what's the IP address of the client? (Currently it's sanitized from the logs.). Why does this matter? If the client is connecting to the proxy using a public IP address, and if the proxy is telling the client to connect to a private IP address for data transfers, then it would explain the timeouts you see when doing directory listings (which are a type of data transfer). The client would be trying to connect to a private IP address, and would not be able to do so. We've not seen the full ProFTPD configuration being used for the proxy. But if the above is the case, then configuring the proxy to provide a public IP address for data transfers, using the Reference: |
Hi @Castaglia, Adding debug loggin and configuration file If you need any more information pls let me know. Regards |
In the provided configuration, I see |
Would it also be possible to get the ProFTPD debug logging of the backend FTP server as well? For debugging issues like this, there are multiple places and multiple factors involved:
Right now, I am looking for data to help indicate whether the main factors are closer to the proxy (and any possible firewall/NAT/router in front of it), or whether the main factors are closer to the backend FTP server. |
HI @Castaglia Below all logs. From frontend, proxy, backend proftpd_frontend_debug.txt Thank you |
Hmm. Nothing in the provided logs is showing any signs of errors. Are you still seeing the error reported by your FTPS client (which app is that)? What's interesting is that these sessions appear to end after 2-3 data transfers (via |
Hi i still see the error, i have restarted the router before the VPN proxy server. But nothing helps. |
Can you run the command-line |
Hi @Castaglia i am now experiencing this issue, i have compiled ProFTPd:
with the latest mod_proxy. The backend FTP servers are: ProFTPd: 1.3.5 and also 1.3.9rc1.
Any help is more then welcome.
Thank you
The text was updated successfully, but these errors were encountered: