TJ Saunders

Ah, I see what's happening here -- it's the same as Issue #193. Namely, that the "address mismatch" in question is occurring between mod_proxy, and the backend server: mod_proxy resolved...

I've just merged my patch to master. If you can download and compile the latest mod_proxy, then you should be able to add `ProxyOptions AllowForeignAddress` to your `` section, and...

Hmm. I'm not sure if building the latest mod_proxy, as a shared module, would work that way. I suspect there might be some compilation differences between the package-installed ProFTPD you're...

> Even without the option, the "operation not permitted" shows up. Here are the debug and proxy log values: > > Proxy log: `2024-07-04 13:07:20,285 mod_proxy/0.9.5[602799]: error stashing proxy session...

For building mod_proxy, you may also want/need to install the ProFTPD "devel" package on Fedora 39, _e.g._ `yum install -y proftpd-devel`. (I'm currently trying to reproduce this build issue locally,...

Thanks for the logs! And I'm glad you were able to get a working build with the latest mod_proxy. I think I found the next issue -- and it's completely...

> On the good news front, replacing the xfer.c file, performing a clean make, and updating the mod_proxy.so file for ProFTPD v1.3.8b does now allow for the original remote address,...

I see. Well, the segfault/backtrace there is certainly unexpected. Would it be possible to see the full `PASV` response that the backend server is sending? In particular, I'd like to...

> Would it be possible to see the full `PASV` response that the backend server is sending? In particular, I'd like to see the address/ports it is telling the client...

Can you elaborate on what you mean by "they continue to work"? Any logs to demonstrate the behavior you're seeing, along with the config you're using?