We have a fairly basic page that uses a json file to drive a report.
Up until 4/13, the FTPS functionality to upload the json file from our corporate server via cURL worked fine. At some point between 14:25 and 15:25 ET, this functionality broke.
Here’s the curl command:
`# curl -m 10 -v ftp://ftp.hubapi.com:3200/<PATH TO DESTINATION FILE>/ --ftp-ssl --user <USER>@<PASS> -T "<PATH TO SOURCE FILE>"`
And verbose output:
* About to connect() to ftp.hubapi.com port 3200 (#0)
* Trying 52.45.105.43... connected
* Connected to ftp.hubapi.com (52.45.105.43) port 3200 (#0)
< 220 Service ready for new user.
> AUTH SSL
< 234 Command AUTH okay; starting SSL connection.
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* subject: CN=*.hubapi.com,O="HubSpot, Inc.",L=Cambridge,ST=ma,C=US
* start date: Feb 13 00:00:00 2017 GMT
* expire date: Feb 21 12:00:00 2019 GMT
* common name: *.hubapi.com
* issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
> USER <USER>
< 331 User name okay, need password for <USER>.
> PASS <PASS>
< 230 User logged in, proceed.
> PBSZ 0
< 200 Command PBSZ okay.
> PROT P
< 200 Command PROT okay.
> PWD
< 257 "/" is current directory.
* Entry path is '/'
> CWD portals
< 250 Directory changed to /portals
> CWD <PATH>
< 250 Directory changed to <PATH1>
> CWD content
< 250 Directory changed to <PATH1>
> CWD files
< 250 Directory changed to <PATH2>
> CWD fhirstats
< 250 Directory changed to <PATH2>
> EPSV
* Connect data stream passively
< 229 Entering Passive Mode (|||3240|)
* Trying 52.45.105.43... connected
* Connecting to 52.45.105.43 (52.45.105.43) port 3240
> TYPE I
< 200 Command TYPE okay.
> STOR logo-tag.png
< 150 File status okay; about to open data connection.
* Doing the SSL/TLS handshake on the data stream
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* NSS error -5990
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:10 --:--:-- 0* Closing connection #0
* SSL connect error
curl: (35) SSL connect error
I’m not sure why the initial SSL handshake works fine but the data stream one fails. Any help would be greatly appreciated.
Same here! I encountered that some time ago already. Eventually, Hubspot restarted their FTP infrastructure to get everything working again.
BTW, I am wondering why Hubspot doesn’t support protocols like ssh, sftp, or rsync, but FTPS only, which I would call outdated and – as we see – unstable and broken.
