Hi All,
I hope you can help me with this because it drives me crazy.
When I check if the server is working propely in ftptest.net it doesn't show any errors. I can also see on the administration server that it is well connected.
Test log
Warning: Selected port (5790) is not the default port (21) of the selected protocol.
Status: Resolving address of 119.12.232.169
Status: Connecting to 119.12.232.169
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message...
Reply: 220-FileZilla Server 1.8.2
Reply: 220-Please visit https://filezilla-project.org/
Reply: 220 Welcome to Control Surveys Server
Command: CLNT https://ftptest.net on behalf of 119.12.232.169
Reply: 200 Don't care.
Command: AUTH TLS
Reply: 234 Using authentication type TLS.
Status: Performing TLS handshake...
Status: TLS handshake successful, verifying certificate...
Status: Received 1 certificates from server.
Status: cert[0]: subject='CN=filezilla-server self signed certificate' issuer='CN=filezilla-server self signed certificate'
Command: USER Allyces
Reply: 331 Please, specify the password.
Command: PASS *******
Reply: 230 Login successful.
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*;perm*;
Reply: MLSD
Reply: AUTH SSL
Reply: AUTH TLS
Reply: PROT
Reply: PBSZ
Reply: UTF8
Reply: TVFS
Reply: EPSV
Reply: EPRT
Reply: MFMT
Reply: 211 End
Command: PBSZ 0
Reply: 200 PBSZ=0
Command: PROT P
Reply: 200 Protection level set to P
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 (119,12,232,169,10,68)
Command: MLSD
Status: Data connection established, performing TLS handshake...
Status: TLS handshake successful, verifying certificate...
Status: Received 1 certificates from server.
Status: cert[0]: subject='CN=filezilla-server self signed certificate' issuer='CN=filezilla-server self signed certificate'
Status: TLS session of transfer connection has been resumed.
Reply: 150 Starting data transfer.
Reply: 226 Operation successful
Status: Success
Results
Your server is working and assorted routers/firewalls have been correctly configured for explicit FTP over TLS as performed by this test. However there have been warnings about compatibility issues, not all users will be able to use your server.
For maximum compatibility, consider resolving these warnings.
However when I use the same credentials in Filezilla Client it doesn't connect at all. This is the message I see.
Status: Connecting to 119.12.232.169:5790...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...
Status: Connecting to 119.12.232.169:5790...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Can someone help me with this, please? I don't know why this happen.
Thanks.
With ftptest.net works but Filezilla client doesn't
Moderator: Project members
Re: With ftptest.net works but Filezilla client doesn't
Could a firewall be blocking you?
-
- 500 Command not understood
- Posts: 4
- Joined: 2024-05-03 12:52
- First name: Carolina
- Last name: Reyes
Re: With ftptest.net works but Filezilla client doesn't
Hi,
Setup are right I already unblocked them. Also the test said everything is fine with the firewall. I don't understand what it is going on.
Regards,
Setup are right I already unblocked them. Also the test said everything is fine with the firewall. I don't understand what it is going on.
Regards,
Re: With ftptest.net works but Filezilla client doesn't
Which test? ftptest.net tests the FTP Server ONLY. It cannot test the client and, in fact, rules it out. Thus, a successful test using that site means the server is good, and the problem is at the client side.
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
-
- 500 Command not understood
- Posts: 4
- Joined: 2024-05-03 12:52
- First name: Carolina
- Last name: Reyes
Re: With ftptest.net works but Filezilla client doesn't
Hi,
Thanks for your answer. I know I am testing if the server is working right. However the fact that I am using the clients credentials to test it make me think that it is not the client issue.
It looks like the website server with clients credentials have access to the files on my computer. As you can see the log below. I hope you can help.
Warning: Selected port (5790) is not the default port (21) of the selected protocol.
Status: Resolving address of 119.12.232.169
Status: Connecting to 119.12.232.169
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message...
Reply: 220-FileZilla Server 1.8.2
Reply: 220-Please visit https://filezilla-project.org/
Reply: 220 Welcome to Control Surveys Server
Command: CLNT https://ftptest.net on behalf of 119.12.232.169
Reply: 200 Don't care.
Command: AUTH TLS
Reply: 234 Using authentication type TLS.
Status: Performing TLS handshake...
Status: TLS handshake successful, verifying certificate...
Status: Received 1 certificates from server.
Status: cert[0]: subject='CN=filezilla-server self signed certificate' issuer='CN=filezilla-server self signed certificate'
Command: USER Allyces
Reply: 331 Please, specify the password.
Command: PASS *******
Reply: 230 Login successful.
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*;perm*;
Reply: MLSD
Reply: AUTH SSL
Reply: AUTH TLS
Reply: PROT
Reply: PBSZ
Reply: UTF8
Reply: TVFS
Reply: EPSV
Reply: EPRT
Reply: MFMT
Reply: 211 End
Command: PBSZ 0
Reply: 200 PBSZ=0
Command: PROT P
Reply: 200 Protection level set to P
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 (119,12,232,169,9,197)
Command: MLSD
Status: Data connection established, performing TLS handshake...
Status: TLS handshake successful, verifying certificate...
Status: Received 1 certificates from server.
Status: cert[0]: subject='CN=filezilla-server self signed certificate' issuer='CN=filezilla-server self signed certificate'
Status: TLS session of transfer connection has been resumed.
Reply: 150 Starting data transfer.
Listing: type=file;size=3906563;modify=20240506125517.544;perms=awr; 05a51315-0cd0-42d1-8849-065a66f22fab.pdf
Reply: 226 Operation successful
Status: Success
Thanks for your answer. I know I am testing if the server is working right. However the fact that I am using the clients credentials to test it make me think that it is not the client issue.
It looks like the website server with clients credentials have access to the files on my computer. As you can see the log below. I hope you can help.
Warning: Selected port (5790) is not the default port (21) of the selected protocol.
Status: Resolving address of 119.12.232.169
Status: Connecting to 119.12.232.169
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message...
Reply: 220-FileZilla Server 1.8.2
Reply: 220-Please visit https://filezilla-project.org/
Reply: 220 Welcome to Control Surveys Server
Command: CLNT https://ftptest.net on behalf of 119.12.232.169
Reply: 200 Don't care.
Command: AUTH TLS
Reply: 234 Using authentication type TLS.
Status: Performing TLS handshake...
Status: TLS handshake successful, verifying certificate...
Status: Received 1 certificates from server.
Status: cert[0]: subject='CN=filezilla-server self signed certificate' issuer='CN=filezilla-server self signed certificate'
Command: USER Allyces
Reply: 331 Please, specify the password.
Command: PASS *******
Reply: 230 Login successful.
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*;perm*;
Reply: MLSD
Reply: AUTH SSL
Reply: AUTH TLS
Reply: PROT
Reply: PBSZ
Reply: UTF8
Reply: TVFS
Reply: EPSV
Reply: EPRT
Reply: MFMT
Reply: 211 End
Command: PBSZ 0
Reply: 200 PBSZ=0
Command: PROT P
Reply: 200 Protection level set to P
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 (119,12,232,169,9,197)
Command: MLSD
Status: Data connection established, performing TLS handshake...
Status: TLS handshake successful, verifying certificate...
Status: Received 1 certificates from server.
Status: cert[0]: subject='CN=filezilla-server self signed certificate' issuer='CN=filezilla-server self signed certificate'
Status: TLS session of transfer connection has been resumed.
Reply: 150 Starting data transfer.
Listing: type=file;size=3906563;modify=20240506125517.544;perms=awr; 05a51315-0cd0-42d1-8849-065a66f22fab.pdf
Reply: 226 Operation successful
Status: Success
Re: With ftptest.net works but Filezilla client doesn't
There is no such thing as "client credentials". Only one type of credentials exist (the ones for accessing the FTP server account), and the client can optionally save them as they are requested by the server as part of the login process. Credential saving in the client is for convenience only.
The test is successful, the server works. It's running on a non-standard port, however, which can be a problem with some bad firewalls that expect FTP traffic only on the default port.
A 100% client side issue, something is blocking FileZilla from making a connection to the destination socket (119.12.232.169:5790).
Note: If the FTP server is running on your own computer, or a computer in your LAN, you need to tell that from the start as it changes things. With a local server, you cannot use the public IP address to access it from a client that's also in the same LAN. In this case, you MUST use the private IP address of the server only, as the public one does not exist within the LAN borders (it exists only on the outside-facing side of your NAT router).
Try with the private IP or the NETBIOS name (Workgroup name) of the local server, then.
The test is successful, the server works. It's running on a non-standard port, however, which can be a problem with some bad firewalls that expect FTP traffic only on the default port.
A 100% client side issue, something is blocking FileZilla from making a connection to the destination socket (119.12.232.169:5790).
What items you see in listings are the ones your FTP account has access to. That would be files from wherever the server is running.It looks like the website server with clients credentials have access to the files on my computer.
Note: If the FTP server is running on your own computer, or a computer in your LAN, you need to tell that from the start as it changes things. With a local server, you cannot use the public IP address to access it from a client that's also in the same LAN. In this case, you MUST use the private IP address of the server only, as the public one does not exist within the LAN borders (it exists only on the outside-facing side of your NAT router).
Try with the private IP or the NETBIOS name (Workgroup name) of the local server, then.
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
-
- 500 Command not understood
- Posts: 4
- Joined: 2024-05-03 12:52
- First name: Carolina
- Last name: Reyes
Re: With ftptest.net works but Filezilla client doesn't
Hi Boco,
Thanks for your answer. I was testing as a client on my own computer becuase I used to do it like that before I changed my internet company. It used to work.
After your note I tried in another computer outside my network and it works. Thanks very much.
Regards,
Thanks for your answer. I was testing as a client on my own computer becuase I used to do it like that before I changed my internet company. It used to work.
After your note I tried in another computer outside my network and it works. Thanks very much.
Regards,