so that works… and I can get directory listings and parse them… so ok … doing it the clunky way … but all is good until I try downloading an avi file from the p1s … I use the following command to try and download and timelapse video:
lftp -d -u bblp,35868996 -e "set ssl:verify-certificate no; cd timelapse; get video_2024-11-22_20-38-08.avi; exit" ftps://192.168.86.180:990
I know the file is there and I can download it with FileZilla no problem and it’s actually a very small file (print was only like 15 layers)
but I get this:
lftp -d -u bblp,35868996 -e "set ssl:verify-certificate no; cd timelapse; get video_2024-11-22_20-38-08.avi ; exit" ftps://192.168.86.180:990
---- Resolving host address...
---- 1 address found: 192.168.86.180
---- Connecting to 192.168.86.180 (192.168.86.180) port 990
Certificate: CN=01P00A411900960
Issued by: C=CN,O=BBL Technologies Co.\, Ltd,CN=BBL CA
Checking against: C=CN,O=BBL Technologies Co.\, Ltd,CN=BBL CA
Trusted
Certificate: C=CN,O=BBL Technologies Co.\, Ltd,CN=BBL CA
Issued by: C=CN,O=BBL Technologies Co.\, Ltd,CN=BBL CA
WARNING: Certificate verification: Not trusted (89:0B:58:86:BA:82:37:47:C4:44:D6:48:1F:C6:D2:21:A6:48:D6:26)
WARNING: Certificate verification: certificate common name doesn't match requested host name ‘192.168.86.180’ (CC:CA:97:D8:78:8A:14:11:F2:90:2D:8F:9D:FB:22:6C:AA:3A:6B:0D)
<--- 220 BBL-P003 FTP Server
---> FEAT
<--- 502 no-features
---> USER bblp
<--- 331
---> PASS 35868996
<--- 230
---> PWD
<--- 257 /
---> PBSZ 0
<--- 200
---- CWD path to be sent is `~/timelapse'
---> CWD timelapse
<--- 250
cd ok, cwd=~/timelapse
---> PROT C
<--- 200
---> TYPE I
<--- 200
---> SIZE video_2024-11-22_20-38-08.avi
<--- 213 297448
---> MDTM video_2024-11-22_20-38-08.avi
<--- 213 20241122210854
---> PASV
<--- 227 (192,168,86,180,7,232)
---- Connecting data socket to (192.168.86.180) port 2024
---- Data connection established
---> RETR video_2024-11-22_20-38-08.avi
<--- 150
---- Got EOF on data connection
---- Closing data socket
**** Peer closed connection
---- Closing control socket
---- Connecting to 192.168.86.180 (192.168.86.180) port 990
Certificate: CN=01P00A411900960
Issued by: C=CN,O=BBL Technologies Co.\, Ltd,CN=BBL CA
Checking against: C=CN,O=BBL Technologies Co.\, Ltd,CN=BBL CA
Trusted
Certificate: C=CN,O=BBL Technologies Co.\, Ltd,CN=BBL CA
Issued by: C=CN,O=BBL Technologies Co.\, Ltd,CN=BBL CA
WARNING: Certificate verification: Not trusted (89:0B:58:86:BA:82:37:47:C4:44:D6:48:1F:C6:D2:21:A6:48:D6:26)
WARNING: Certificate verification: certificate common name doesn't match requested host name ‘192.168.86.180’ (CC:CA:97:D8:78:8A:14:11:F2:90:2D:8F:9D:FB:22:6C:AA:3A:6B:0D)
<--- 220 BBL-P003 FTP Server
---> FEAT
<--- 502 no-features
---> USER bblp
<--- 331
---> PASS 35868996
<--- 230
---> PWD
<--- 257 /
---> PBSZ 0
<--- 200
---- CWD path to be sent is `~/timelapse'
---> CWD timelapse
<--- 250
---> PROT C
<--- 200
---> TYPE I
<--- 200
---> PASV
<--- 227 (192,168,86,180,7,232)
---- Connecting data socket to (192.168.86.180) port 2024
---- Data connection established
---> RETR video_2024-11-22_20-38-08.avi
<--- 150
Interrupt
---> ABOR
---- Closing aborted data socket
---- Closing control socket
over and over again … it tries to start the download … it doesn’t create the file locally and times out about about 10 seconds and reconnects… I’m scratching my head now.