Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Connection timeouts
Hi,
From approximately 22:30 UTC on 27 Oct until present we have been getting timeouts when trying to connect to the Dropbox API:
cURL error 7: Failed to connect to content.dropboxapi.com port 44...
I have just received a reply from Digital Pacific explaining that:
"We erroneously blocked the IP due to suspicion of it being involved in a large attack on our networks, This error has now been corrected and the block reverted"
So this problem was with the host - my apologies for wasting your time. Thanks very much for your help.
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorCalls to files/get_metadata would be made to api.dropboxapi.com (not content.dropboxapi.com). There are other endpoints on api.dropboxapi.com as well though, such as files/list_folder. Are you attempting any other calls to api.dropboxapi.com, and if so, are those not failing?
Please do let me know if you hear anything from Digital Pacific.
And no, the debug page uses JavaScript to run the tests, so you'd need to use a browser (e.g., you can't just curl the page), so unless you can use your server as a proxy, or something to that effect, we'll need to investigate without that information.
Thanks Greg. Sorry, I was mistaken about the specific call it's timing out on.
Here's an example of a curl command failing on a content.dropboxapi.com endpoint:
$ curl -X POST https://content.dropboxapi.com/2/files/upload --header "Authorization: Bearer <token>" --header "Dropbox-API-Arg: {\"path\": \"/test.txt\",\"mode\": \"add\",\"autorename\": true,\"mute\": false,\"strict_conflict\": false}" --header "Content-Type: application/octet-stream" --data-binary @test
curl: (7) Failed to connect to 2620:100:6033:8::a27d:5308: Network is unreachableInterestingly, the error message here points to an IPV6 address. From that server, `ping6 ipv6.google.com` outputs `Connect: Network is unreachable`, so I wonder if the issue is that IPV6 is not enabled on that server.
Should we need IPV6 enabled to properly use the API?
- Greg-DB
I see, thanks.
It looks like that's a different error message now though. For reference, can you let me know exactly which endpoint(s) and host(s) are currently returning which error message(s) for you?
And no, IPv6 isn't required. Both v4 and v6 should work. I just tried it myself and confirmed that https://content.dropboxapi.com/2/files/upload is usable via both.
I believe that the difference in the error message is due to the message in my initial report coming from libcurl being used by a PHP application as opposed to command line curl.
Calls to both files/list_folder and file_requests/get returned the expected result. Therefore it seems api.dropboxapi.com is working fine for me.
Attempting to use the /files/upload endpoint returns the error mentioned previously:
$ curl -X POST https://content.dropboxapi.com/2/files/upload --header "Authorization: Bearer <token>" --header "Dropbox-API-Arg: {\"path\": \"/test.txt\",\"mode\": \"add\",\"autorename\": true,\"mute\": false,\"strict_conflict\": false}" --header "Content-Type: application/octet-stream" --data-binary @test curl: (7) Failed to connect to 2620:100:6033:8::a27d:5308: Network is unreachableAs does a call to /files/download:
$ curl -X POST https://content.dropboxapi.com/2/files/download --header "Authorization: Bearer <token>" --header "Dropbox-API-Arg: {\"path\": \"/test.txt\"}"
curl: (7) Failed to connect to 2620:100:6033:8::a27d:5308: Network is unreachableSo it seems that the problem is related to API calls on content.dropboxapi.com.
- Greg-DB
Thank you, that helps clarify the scope of the issue. We still haven't found anything on our side that should be causing this, but I'll check with the network team again.
By the way, to clarify your earlier note of "Should we need IPV6 enabled to properly use the API?", do you mean that the IPv6 stack is not currently enabled on your own server? The Dropbox API servers accept both, but the sample attempts you showed do indicate that your client is attempting to use IPv6. If IPv6 is not enabled on your server but your client is trying to use it for some reason, perhaps that's causing the issue. If that's the case, you may want to try the '-4' option to force curl to use IPv4, or check the verbose '-v' output of curl when accessing api.dropboxapi.com as a comparison.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
