500 I won't open a connection to 192.168.x.x (only to 121.121.160.12)

[C-Fu]

This is the log while using filezilla in windows

Status:	Plain FTP is insecure. Please switch to FTP over TLS.
Command:	USER newuser
Response:	331 User newuser OK. Password required
Command:	PASS ***********
Response:	230 OK. Current directory is /
Command:	OPTS UTF8 ON
Response:	200 OK, UTF-8 enabled
Status:	Logged in
Status:	Retrieving directory listing...
Command:	PWD
Response:	257 "/" is your current location
Command:	TYPE I
Response:	200 TYPE is now 8-bit binary
Command:	PORT 192,168,1,19,251,92
Response:	500 I won't open a connection to 192.168.1.19 (only to 121.121.160.12)
Command:	PASV
Response:	227 Entering Passive Mode (115,134,7,89,78,61)
Command:	MLSD

And nothing happens. this worked a month ago without touching anything, as in I can get the directory listing, uploads and downloads working from local network.
No idea what that 121 IP is from.

[stilliard]

Hi @C-Fu
I'd check the PUBLICHOST for passive mode is correct as well as the ports.
192.168.1.19 looks like a local/private ip while 121.121.160.12 is an external ip so worth checking how you have it set and the ip you're connecting from.
Hope this helps.

[C-Fu]

Thanks for the quick reply!

Thing is 121 is an IP that is unknown to me, and yes I am connecting from another pc in the same network/house. It's highly unlikely for me to manually set that setting to only allow that 121 ip origin.

But this behaviour didn't appear a month ago. I don't even know how to block/limit IP in Linux (or pure ftpd for that matter). Maybe you can advice on how would I do this, so I can get to the bottom of the error?

Only change I did, as far as I know, was to change the port range from 10 ports like 50000-50010 to 50 ports, and use port trigger in my asus router. And my public ip isn't 121.

[stilliard]

Via Filezilla's Site Manager, under Transfer Settings could you try enabling Passive (rather than Active) mode?
If it was trying to use active mode before that may have been the issue.

Also for your docker container, can you confirm PUBLICHOST is the IP you're connecting to via filezilla?

Another thing is you mentioned changing the ports, these would be exposed via FTP_PASSIVE_PORTS, could you check these are correct and not blocked by any firewall.