Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

FTPS upload error
#1

I'm trying to switch over our all our FTP connection to FTPS for better security. The FTP is being handled by FileZilla server using a cert file created from within FileZilla. I can connect to the FTPS site via FileZilla client and other FTPS compatible clients. They do give messages about the certificate being "unknown" or "non trusted", however the connection can still be made successfully. 

SIW is giving the following error:

[Image: filezilla.png]
Using the following command to run/upload the report (tried with both siw32.exe and siw64.exe):
  • siw64.exe /log="test.html" /upload=ftps://[user]:[password]@[ftps_site]

Here is the FileZilla Server log for the attempted connection:
  • (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> Connected on port 990, sending welcome message...

    (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> 220 FileZilla Server 0.9.60 beta
    (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> TLS connection established
    (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> USER aem
    (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> 331 Password required for aem
    (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> PASS ******
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 230 Logged on
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> PBSZ 0
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 200 PBSZ=0
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> PROT P
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 200 Protection level set to P
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> PWD
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 257 "/" is current directory.
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> EPSV
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 229 Entering Extended Passive Mode (|||5046|)
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> TYPE I
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 200 Type set to I
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> STOR test.html
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 150 Opening data channel for file upload to server of "/test.html"
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 450 TLS session of data connection has not resumed or the session does not match the control connection
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> could not send reply, disconnected.


Any thoughts?
Reply
#2

(04-13-2021 07:10 PM)[email protected] Wrote:  I'm trying to switch over our all our FTP connection to FTPS for better security. The FTP is being handled by FileZilla server using a cert file created from within FileZilla. I can connect to the FTPS site via FileZilla client and other FTPS compatible clients. They do give messages about the certificate being "unknown" or "non trusted", however the connection can still be made successfully. 

SIW is giving the following error:

[Image: filezilla.png]
Using the following command to run/upload the report (tried with both siw32.exe and siw64.exe):
  • siw64.exe /log="test.html" /upload=ftps://[user]:[password]@[ftps_site]

Here is the FileZilla Server log for the attempted connection:
  • (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> Connected on port 990, sending welcome message...

    (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> 220 FileZilla Server 0.9.60 beta
    (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> TLS connection established
    (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> USER aem
    (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> 331 Password required for aem
    (000170)4/13/2021 16:06:08 PM - (not logged in) (192.168.1.128)> PASS ******
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 230 Logged on
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> PBSZ 0
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 200 PBSZ=0
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> PROT P
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 200 Protection level set to P
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> PWD
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 257 "/" is current directory.
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> EPSV
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 229 Entering Extended Passive Mode (|||5046|)
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> TYPE I
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 200 Type set to I
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> STOR test.html
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 150 Opening data channel for file upload to server of "/test.html"
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> 450 TLS session of data connection has not resumed or the session does not match the control connection
    (000170)4/13/2021 16:06:08 PM - aem (192.168.1.128)> could not send reply, disconnected.


Any thoughts?
  • Issue #1: The report file name should have an absolute path.
  • Issue #2: If you want to use FTPS for better security, please use a proper certificate.
    I guess that SIW doesn't support FTPS with "unknown" or "non trusted" certificates.
Reply




Users browsing this thread: 2 Guest(s)