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.
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.
Hi joe_walker,
Everything you have reported point to some problem in network configuration of your machine. If you want to use IPv6 then all devices seating on the route between content.dropboxapi.com and your machine should be configured properly to use the protocol. Even one misconfiguration is enough to reach such a result. Try "traceroute6 content.dropboxapi.com" to figure out where exactly is the problem. If the error message is reported immediately, you are working on misconfigured machine (or if DHCP is used then corresponding router(s) could be problematic). While resolving the issue you can use the Greg-DB's workaround (force use of IPv4). :wink: From your initial post could be concluded that will work for you (it's in fact IPv4 trace).
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
