FileZilla Forums

I'm getting the IP address used in passive mode from an external source, but I can't get it properly after 0.9.51.
The log shows Entering Passive Mode (0,0,0,10,*,*).
It has been successfully acquired up to 0.9.50.

First, always use the latest (0.9.60 ATM), issues will not be resolved for older versions.

How are you getting it? If you use the "Retrieve" option, the site must print the IP as literal text.
I'm not completely certain, but it might be that FileZilla Server (the code is very outdated right now) does not support HTTPS webpages as source. The default entry is plain HTTP. If your external source has switched to forced HTTPS (HSTS), and redirects http to https, it could be no longer working.

@botg: Does FZ Server support HTTPS Retrieve targets?

@boco: No. Maybe in a future version.

Hmmm
I got the IP address on my site, I did not use HTTPS, I output it in plain text.
However, it becomes 0,0,0,10.

If you visit your site in a browser (http://), does it automatically load the HTTPS version?

I couldn't find anything in the Server 0.9.50 to 0.9.51 version history that would explain that.

Is it my site?
I use only HTTP, not HTTPS.

Please try if it works when using the default entry.

It seems to succeed by default.
Hmm?
I confirmed that it failed before posting.

I'm running my site with a simple Perl script.
print "Content-type:text/plain\n\n$ENV{REMOTE_ADDR}\n";
Why does this fail?
What am I missing here?

I was able to get the IP address, but it is failing to open the data connection.
There may be a problem with the test site (https://ftptest.net/), but I'm not sure.
It's weird, even though it's all successful at 0.9.50.
If you know of any good testing sites, please let me know.

Your script is wrong. HTTP uses CRLF as separator between header lines. Furthermore, the canonical form for header lines includes a space between the colon and the value.

Last but not least, you need to set the Content-Length header to force use of the identity transfer encoding, FileZilla Server does not support the chunked transfer encoding.

HM.
Format analysis is strict.
I understand that, but why is it allowed in 0.9.50?
Did you change that in 0.9.51?