1.12.34 Basically working but getting dreaded 400 with Dropbox

Getting the dreaded 400 errors trying to upload. It gets authorized to Dropbox and creates the directory just fine. And it even uploaded one little backup file successfully. The rest it chokes on. I’m sure there’s a simple explanation for this. Here’s a bit from the most recent log:

0185.933 (0) Dropbox quota usage: used=96914.8 MB, total=1058048 MB, available=961133.2 MB
0185.953 (0) Dropbox: Attempt to upload: backup_2017-02-28-1527_Tinch_Band_d35c19090bb1-uploads3.zip to: backup_2017-02-28-1527_Tinch_Band_d35c19090bb1-uploads3.zip
0196.754 (0) Dropbox chunked upload: 2.9 % uploaded (, 10485760, 10240 KB)
0198.152 (0) Dropbox chunked upload: 5.7 % uploaded (, 20971520, 10240 KB)
0199.878 (0) Dropbox chunked upload: 8.6 % uploaded (, 31457280, 10240 KB)
.
.
.
0245.132 (0) Dropbox chunked upload: 94.6 % uploaded (, 346030080, 10240 KB)
0246.733 (0) Dropbox chunked upload: 97.4 % uploaded (, 356515840, 10240 KB)
0248.019 (0) Dropbox chunked upload: 100 % uploaded (, 365888515, 10240 KB)
0248.148 (0) Unexpected HTTP code returned from Dropbox: 400 (a:3:{s:4:”code”;s:3:”400″;s:4:”body”;s:151:”Error in call to API function “files/upload_session/finish”: HTTP header “Dropbox-API-Arg”: cursor.session_id: ‘None’ expected to be a string, got null”;s:7:”headers”;a:7:{s:6:”server”;s:5:”nginx”;s:4:”date”;s:29:”Tue, 28 Feb 2017 21:31:32 GMT”;s:12:”content-type”;s:25:”text/plain; charset=utf-8″;s:17:”transfer-encoding”;s:7:”chunked”;s:10:”connection”;s:10:”keep-alive”;s:20:”x-dropbox-request-id”;s:32:”9e8ecdd0331f3e3be8bc80a2b2d1dfdd”;s:12:”x-robots-tag”;s:31:”noindex, nofollow, noimageindex”;}})
0248.149 (0) Recording as successfully uploaded: backup_2017-02-28-1527_Tinch_Band_d35c19090bb1-uploads3.zip (faeacd218d6f7fc1ef4db446d02c4263)
0248.213 (0) Deleting local file: backup_2017-02-28-1527_Tinch_Band_d35c19090bb1-uploads3.zip: OK
0248.214 (0) Dropbox: File upload success (backup_2017-02-28-1527_Tinch_Band_d35c19090bb1-uploads3.zip): 357313 KB in 62s (5738 KB/s)

************
Notice that it acknowledges an error, then happily deletes the local file and records an upload success anyway!!!! Don’t you just LOVE it when that happens??? ??

Now THIS file actually uploaded successfully and appeared at Dropbox! The only thing I can figure is that it’s such a small file that there wasn’t time for anything to go wrong.

0248.575 (0) Dropbox: Attempt to upload: backup_2017-02-28-1527_Tinch_Band_d35c19090bb1-others.zip to: backup_2017-02-28-1527_Tinch_Band_d35c19090bb1-others.zip
0251.575 (0) Dropbox chunked upload: 100 % uploaded (AAAAAAAJPGWyKLMv5G34Kg, 145067, 10240 KB)
0252.804 (0) Recording as successfully uploaded: backup_2017-02-28-1527_Tinch_Band_d35c19090bb1-others.zip (760972dd5cc2e1787d8353d161f39942)
0252.806 (0) Deleting local file: backup_2017-02-28-1527_Tinch_Band_d35c19090bb1-others.zip: OK

**************
Server info:
Server Environment
Server Info: Apache
PHP Version: 5.6.30
PHP Post Max Size: 96 MB
PHP Time Limit: 300
PHP Max Input Vars: 1000
cURL Version: 7.19.7, NSS/3.21 Basic ECC
SUHOSIN Installed: –
MySQL Version: 5.6.35

*******
So… any advice lads??? Maybe a cURL thing? Is that something I can get my server guys to update? That version of cURL is from 2009. I have seen other mentions in this forum about “years old” versions of cURL.

Thanks,
Mark