"Cannot connect to host api.box.com:443" errors
We've seen increasing log messages for these "Cannot connect to host api.box.com:443" errors, and we're not really sure what the source is.
I have seen this post:
But I do not think this is the issue we're having, since most calls do successfully pass through. As we increased the speed of our api calls, these errors started to show up more. It could just be there's more chance of failure because we're making more calls.
Also we also do not use a proxy, so we shouldn't be hitting any sort of connection limit on our end.
If there's any more information I can provide, please let me know!
-
Hi ,
Is there any other data that is being sent in the error? Based on what you're saying about increasing the number of requests, I'm wondering if the underlying error is related to rate limits. If that's the case you'll see a 429 error coming back. If that's the case, you'll want to space your requests out based on the limits.
- Jon
-
Hello, thank you for your reply!
Unfortunately I don't think these are rate limits, as we are checking for a 429 status code and handling that accordingly. I think we're just seeing more of these errors with the increase in request speed because we're just making more requests in the same period of time.
Something else I've seen accompany this error is also a timeout error:
TimeoutError: [Errno 110] Connect call failed ('xxx.xxx.xx.xxx', 443).It also appears that we don't get any sort of status code for the request, it seems we are just hitting this timeout.
サインインしてコメントを残してください。
コメント
2件のコメント