TJ Saunders

Can you provide all the logs that you can, for both successful _and_ failing directory listings? I'm hoping to see what might be different between the success and failure cases...

Thanks for those. Nothing standing out _just_ yet. So, to get more data, would you mind adding more to your `Trace` directive? Specifically: ``` Trace proxy:30 \ command:20 \ proxy.conn:30...

Thanks for those; they do help. In the not-working case, we see the "425 MLSD: Invalid argument" error response -- which can only come from [here](https://github.com/Castaglia/proftpd-mod_proxy/blob/master/mod_proxy.c#L2177), based on the rest...

@driici If I cannot reproduce the issue locally, then I cannot easily address/fix this. Barring that, I need _something_ that reliably shows this error, in order to fix it.

@driici I'm hoping that https://github.com/Castaglia/proftpd-mod_proxy/commit/ebcf82c9f3e5668e2b0218712bba64ec3287d6be can also help to address this; can you try the latest `mod_proxy` code in your environment, and see if the issue has been addressed?

@aljasPOD thanks for digging into this! This reminds me of some logging changes I recently did for Issue #213, namely to try to add logging hints in cases where `ProxySourceAddress`...

Interestingly, I _do_ see that `mod_proxy` attempts to handle such IPv6/IPv4 cases [here](https://github.com/Castaglia/proftpd-mod_proxy/blob/master/lib/proxy/conn.c#L700) -- but that's when establishing the backend control connection; when making the backend _data_ connection (as for...

@driici Would you be able to test the latest `mod_proxy` code, to see if your issue still occurs? Thanks!

@driici Actually, in looking back through your logs with fresh eyes, I think the issue you encountered is _different_ than that of @aljasPOD. The recent commits should make the behavior...

I've confirmed that `mod_proxy` does indeed properly reject `PORT`, `EPRT` commands that tell the server to use an IP address that is different than the client's IP address for the...