Fatal error: Uncaught exception 'Dropbox\Exception_NetworkIO' with message 'Error executing HTTP request: error:14094410:SSL routines:SSL3_READ_BYTES:

Do you have an API app that is failing with this error message? Support for SSLv3 on the Dropbox API was disabled some time ago. (Developer were notified in advance by email.) You should use TLS for secure connections to the Dropbox API instead.

I have the excat same error:

Uncaught Dropbox\Exception_NetworkIO: Error executing HTTP request: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure

On Line 54 in /dropbox-sdk/Dropbox/Curl.php

I make a request from an SSL encrypted site. This error is thrown when I follow the PHP SDK Tutorial to the letter.
My app is a single user app, just for this one website and no other. So a "hardcoded" solution would be fine.

Can anyone help, or point me to resources / documentation on how to get this working again.

If you're using the official PHP SDK, you should be able to just update to the latest version, which uses TLS:

https://www.dropbox.com/developers/core/sdks/php

Thanks Greg,

I downloaded the newest version manually (for some reasons my composer did not update the sdk to 1.1.4)
Now I'm getting the following Error:

[User Error] Uncaught Exception: The Dropbox SDK uses 64-bit integers, but it looks like we're running on a version of PHP that doesn't support 64-bit integers (PHP_INT_MAX=2147483647)

Is there any way around this? Or do I have to contact my hosting service?

Due to the size of certain numbers used by the SDK, it requires a 64-bit build of PHP in order to run properly, so the right solution is to upgrade your PHP installation to a 64-bit build. There isn't really any other workaround, besides disabling this check, but that of course isn't recommended.

Thanks Greg for your reply.
Unfortunately I cant upgrade my server.

If I disable the 64bit check, whats the worst that could happen? Dataloss would be terrible.
I really just need the meta listing of the files.

Thanks in advance

Unfortunately I can't really make any guarantee one way or another, though if you're not interacting with content, e.g., not uploading or downloading files, I would expect there'd be no opportunity for data loss. For metadata, your app might see incorrect file sizes.

At which filesize would this be? There are many files, but none will be bigger than 150MB. And even if the size are displayed incorrectly, thats fine. My priority is to check that the files are there and what name they have.

Thank you :)

Based on the PHP_INT_MAX value above, it would probably be files >2GB, but again I can't make any promises, so do so at your own risk.