Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
alenavarro
4 years agoExplorer | Level 4
Files are no longer uploaded to Dropbox from PowerShell script
Hi everyone!
Hope you can help me out with this one:
We have a VOIP provider which stores calls for a maximum of 30 days, hence, we download them and upload the .wav files to Dropbox so we ca...
Greg-DB
Dropbox Community Moderator
4 years agoWhenever you make an API call, such as to /2/files/upload like in this code, you would either get a response from the API (such as the result or some API error), or some error from your network client if the connection failed. I understand you're not getting an error message in the output, so you may need to debug this or refer to the documentation for your platform for information on how to access the error, e.g., when using 'Invoke-RestMethod'. That's not made by Dropbox though so I can't offer help with that specifically.
Based on the description and timing though, this may be due to a recent change to our TLS configuration. Dropbox recently retired support for TLS 1.0 and 1.1. The Dropbox API servers now only support connections using TLS 1.2. You'll need to update your app/network client/environment to use TLS 1.2 in order to continue making Dropbox API calls.
- alenavarro4 years agoExplorer | Level 4
Thanks for the answer.
I was able to debug a bit, here's the error I get:
This is indeed an error with Upload-FileToDropbox function...and it looks like a WriteErrorException
Weird, as stated before, the script ran for almost two years without any changes made to it....
We tried running it on a different PC, with most of the updates for the OS (TLS), but still the same....
Any other ideas we might try? @Greg-DB
- Greg-DB4 years ago
Dropbox Community Moderator
The 'Microsoft.PowerShell.Commands.WriteErrorException' error type isn't made by Dropbox, so I can't offer too much insight on that. If a Dropbox API call fails, the Dropbox API would return a response body, but I don't see one here.
I do still expect this is related to the TLS change though, so I recommend looking into making sure your environment uses TLS 1.2. (In the case of a TLS failure, that would be a failure of the actual network connection and so would fail before the Dropbox API call occurs, meaning there wouldn't be an error message from the Dropbox API itself.)
- alenavarro4 years agoExplorer | Level 4
Well, I double checked and the PCs are running TLS 1.2
Should I just check that protocol and disable all others? I don't think that would be recommended
Also, where else can I ask about this?
I'm still insisting that the script worked for TWO YEARS and just a few days ago stopped working...
So if it isn't related to TLS, what else can it be?
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!