Child Item

My Dropbox API connection stopped responding to my apps hosted on Multiple Servers

For couple of days we found that our dropbox API connection (dropbox app with folder access) stopped working with below error generated:

System.Net.Http.HttpRequestException: An error occurred while sending the request. 
---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: 
A connection attempt failed because the connected party did not properly respond after a period of time, 
or established connection failed because connected host has failed to respond 162.125.8.8:443

Our API is accessed from 2 Servers (Godaddy hosted VPS) and both of them can't access the API,

but the connection is working properly from my development machine and other Server that wasn't connected to the API before.

We've checked our server's firewall, antivirus and other network-related software and it has nothing to do with this server.

So what could be the problem?

Could dropbox block our server's access or soemthing?

Find more posts tagged with

API

Abuse

Accepted answers

Greg-DB

Thanks for following up. I'm glad to hear this is working for you again.

The Dropbox API wouldn't block access like this. If the Dropbox API rejects a call, it returns an explicit error message, not a network block.

It sound like there was a networking issue preventing your server from reaching the Dropbox API servers. This could have occurred anywhere along the network, so I can't say off hand where the issue was. If you do see this again, let us know and we'll investigate on our side.

All comments

m-mansour

The conncetion came back and is working fine now, don't know the source of error nor the reason it came back, but its working now on both servers after 5 days of connection time-out error.

Greg-DB

Thanks for following up. I'm glad to hear this is working for you again.

The Dropbox API wouldn't block access like this. If the Dropbox API rejects a call, it returns an explicit error message, not a network block.

m-mansour

Thanks for the quick reply,

I'm not sure either but will see if this happened again and will try to get more details about it (hope it doesn't happen again).