Issue Getting Connected to FTP Server

[boco]

It didn't work, only the first image is visible.

Why is the "Retrieve external IP address from:" field censored? Please note that you cannot enter your private URL here, as the IP is not obtained by resolving. In most cases, you are expected to leave the default URL in there.

If you want to enter a Hostname/URL that resolves to your IP, enter it into the "Use the following IP:" field.

[CaseCrS]

I'm using a Dynamic DNS through No-IP.com. I'm pretty sure when it was working I had the URL in the retrieve external IP address field. I just tried switching it to the Use the following IP field and it's still not working.

[boco]

The Retrieve field requires the service to literally print the IP as text to a website. The Custom IP resolves.

I'm pretty sure when it was working I had the URL in the retrieve external IP address field.

As you used Plain FTP before, the previous router might have modified the IPs on the fly so the wrong configuration didn't cause the server to fall over. Such silent modifications cause much confusion on the user's part. They simply cannot understand why their configuration was/is wrong when "it is working fine". See the section about malicious routers in Network Configuration.

[boco]

Code: Select all

16:25:47	Status:	Connecting to 24.53.xxx.xx:60059...
16:25:47	Status:	Connection established, waiting for welcome message...
16:25:47	Response:	220-FileZilla Server 0.9.60 beta
16:25:47	Response:	220-written by Tim Kosse (tim.kosse@filezilla-project.org)
16:25:47	Response:	220 Please visit https://filezilla-project.org/
16:25:47	Command:	AUTH TLS
16:25:47	Response:	502 Explicit TLS authentication not allowed
16:25:47	Command:	AUTH SSL
16:25:47	Response:	502 Explicit TLS authentication not allowed
16:25:47	Status:	Insecure server, it does not support FTP over TLS.
16:25:47	Command:	USER anonymous
16:25:47	Response:	331 Password required for anonymous
16:25:47	Command:	PASS *********************
16:25:48	Response:	530 Login or password incorrect!
16:25:48	Error:	Critical error: Could not connect to server

Although login did not succeed, I can connect to your server. But only if I use your current IP address. Your DDNS URL points to an old, outdated IP that doesn't work anymore. Does renewing the dynamic DNS addres work correctly?

[CaseCrS]

Code: Select all

16:25:47	Status:	Connecting to 24.53.xxx.xx:60059...
16:25:47	Status:	Connection established, waiting for welcome message...
16:25:47	Response:	220-FileZilla Server 0.9.60 beta
16:25:47	Response:	220-written by Tim Kosse (tim.kosse@filezilla-project.org)
16:25:47	Response:	220 Please visit https://filezilla-project.org/
16:25:47	Command:	AUTH TLS
16:25:47	Response:	502 Explicit TLS authentication not allowed
16:25:47	Command:	AUTH SSL
16:25:47	Response:	502 Explicit TLS authentication not allowed
16:25:47	Status:	Insecure server, it does not support FTP over TLS.
16:25:47	Command:	USER anonymous
16:25:47	Response:	331 Password required for anonymous
16:25:47	Command:	PASS *********************
16:25:48	Response:	530 Login or password incorrect!
16:25:48	Error:	Critical error: Could not connect to server

Although login did not succeed, I can connect to your server. But only if I use your current IP address. Your DDNS URL points to an old, outdated IP that doesn't work anymore. Does renewing the dynamic DNS addres work correctly?

Well it's supposed to update automatically, I just forced an update I'll try it again and see if it work.
Thanks!

[CaseCrS]

I figured it had to be something simple I was overlooking. Forcing the DDNS to update the IP worked. Thanks for the help!

[CaseCrS]

New issue, even though I have the users set to be able to list directories and to read the Online FTP Tester is saying to make sure that account has permissions to list directories.

Code: Select all

Warning: Plaintext FTP is insecure. You should use explicit FTP over TLS.
Warning: Selected port (60059) is not the default port (21) of the selected protocol.
Status: Connecting to 24.53.120.52
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message...
Reply: 220-FileZilla Server 0.9.60 beta
Reply: 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
Reply: 220 Please visit https://filezilla-project.org/
Command: CLNT https://ftptest.net on behalf of 24.53.120.52
Reply: 200 Don't care
Command: USER Tester
Reply: 331 Password required for tester
Command: PASS ******
Reply: 230 Logged on
Command: SYST
Reply: 215 UNIX emulated by FileZilla
Command: FEAT
Reply: 211-Features:
Reply: MDTM
Reply: REST STREAM
Reply: SIZE
Reply: MLST type*;size*;modify*;
Reply: MLSD
Reply: UTF8
Reply: CLNT
Reply: MFMT
Reply: EPSV
Reply: EPRT
Reply: 211 End
Command: PWD
Reply: 257 "/" is current directory.
Status: Current path is /
Command: TYPE I
Reply: 200 Type set to I
Command: PASV
Reply: 227 Entering Passive Mode (24,53,119,78,234,239)
Command: MLSD
Reply: 425 Can't open data connection for transfer of "/"
Error: Listing failed

[CaseCrS]

Here's the Permissions on the folder

Permissions.png (5.21 KiB) Viewed 3903 times

[CaseCrS]

Added a Port Triggering Rule in my router and that seemed to do it. Both the Online FTP Tester and the FTP client on my phone can connect to the server.
Thanks for all the help!