You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
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.
Hi Greg,
Yes - the connection still times out and the traceroute result is still the same as above.
Greg-DB
Dropbox Staff
Dropbox StaffThanks! We're looking into this, but we haven't been able to find a network issue for that network route.
To try to narrow this down:
- Are there multiple users of your app, and if so, are multiple users affected, or just yourself?
- Which API endpoints in particular are you using, and which are affected?
- Is this affecting all of the attempts to connect to content.dropboxapi.com, or only some of them? If it's only some of them, about what percent are affected?
- Is there anything on your network connection, e.g., a proxy, firewall, anti-virus, etc. what may be interfering with HTTPS connections to content.dropboxapi.com?
- Can you share the information on https://dropbox-debug.com from an affected machine?
We are the only users of the app.
Specifically the call to the "files/get_metadata" times out, however all attempts to connect to content.dropboxapi.com time out.
I do not know of anything on the network which would be interfering with the connection, and do not know of anything that changed around the time the problem started occurring. The server's host (Digital Pacific) has not reported that they are aware of any network issues, though I have submitted a ticket to double check.
As the app is running on a server without a web browser, is there any other way to get the debug information provided by dropbox-debug.com?
- Greg-DB
Calls 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?
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
