Changes to the problem

Requests to Ecobee getting Timeout

In order to preserve the promise of transparency and open communication, the change log records changes to topics made by both customers and employees. Anyone can dispute a change by clicking the "Dispute" link and entering additional details.


  • May 13, 2016 18:53
    Jari
    Change in reply by Jari to Thanks Pedro. I was hoping this might be related to a special case for MSIE where the socket keep alive and shutdown behaviour has been altered. However, that doesn't seem to be the case here. Fortunately, I've managed to reproduce the problem and have a hunch as to what may be causing it. I might need a few more days to come up with a solution..
  • May 13, 2016 18:53
    Jari
    Change in reply by Jari to Thanks Pedro. I was hoping this might be related to a special case for MSIE where the socket keep alive and shutdown behaviour has been altered. However, that doesn't seem to be the case here. Fortunately, I've managed to reproduce and the problem and have a hunch as to what may be causing it. I might need a few more days to come up with a solution..
  • April 13, 2016 20:32
    Jari
    Change in reply by Jari to Hi Pedro,<br /><br />I can confirm that I don't see your IP or netblock in any block lists on our side.<br /><br />It looks like you ran a 'tracepath' which does PMTU discovery instead of a 'traceroute'. Can you run 'traceroute' instead? Also, can you confirm if you're able to ping api.ecobee.com or not? You should be able to ping us, if not then there may be a network connectivity issue between us. Finally, you may want to try 'traceroute' with TCP SYN's, do a 'traceroute -T -p 443 api.ecobee.com'. It would also be helpful if you can include tcpdump output while running the ping and traceroute commands.<br /><br />Alternatively, if your traceroute doesn't support the '-T' option then you may want to look at tcptraceroute.<br /><br />Also, is the problem intermittent? I show that you last connected to us on the 11th at approx. 18:00 UTC-4. Is that when the problem began for you? Does the problem occur from any other hosts or networks that you are using?<br /><br />Thanks,<br /><br />Jari.

See all changes made to topics in this company