Getting intermittent ERR_CONNECTION_TIMED_OUT message RRS feed

  • Question

  • User1312450783 posted


    I have had several asp.net applications up and running on GoDaddy for over 10 years. About 10 days ago (11/19) I starting getting (for the first time), this message:  

    "This site can't be reached. xxx.mydomain.com took too long to respond. ERR_CONNECTION_TIMED_OUT"

    This is happening randomly across all of my subdomains - (ones that I have made any changes to in years).  Once I receive that error, I have to completely restart my browser for any of the pages to load again - and sometimes that doesn't even work.  Once I am back in to my application, it usually works fine for several minutes - then I start receiving that message again.

    Of course, I have contacted GoDaddy and they said that I would have to purchase a new hosted site with them that is a later version.  I asked if their current version wasn't being supported (as I hadn't received any notice of this) and they said it was still supported but that most likely the reason for these errors was that I was on an older version. 

    Has anyone experienced this issue? Any ideas of how I can work around this?  I don't think I will be getting much assistance from GoDaddy, unfortunately.

    Friday, November 29, 2019 7:58 PM

All replies

  • User409696431 posted

    Clearly if you changed nothing, and it started happening, it's nothing you can fix.  It is a GoDaddy problem, so they are your only source of information about what might be causing it and there is no "getting around" a server load/response problem when you don't control the server.   Something is overloading the server, and GoDaddy doesn't seem to be interested in finding out what, but instead is set on upselling you.   Frankly, you get what you pay for, and GoDaddy is cheap.  I have no idea if moving to a new plan on GoDaddy will help, although if it is a newer and/or more expensive plan they may have more resources assigned to it.  Or find a different host.

    Saturday, November 30, 2019 4:12 AM
  • User61956409 posted

    Hi lpieczynski,

    This is happening randomly across all of my subdomains - (ones that I have made any changes to in years).

    I have contacted GoDaddy and they said that I would have to purchase a new hosted site with them that is a later version.

    According to your description, the issue seems be caused by GoDaddy hosting service/server, not your ASP.NET application (our forums discuss on ASP.NET related questions), so please contact GoDaddy supporter or post the issue in GoDaddy community forums. Thanks for your understanding.


    With Regards,

    Fei Han

    Monday, December 2, 2019 1:57 AM
  • User1057802005 posted

    I am experiencing a similar problem although the message I receive is err_connection_refused. I've come to a workaround that consists in a .NET application whose function (at regular intervals) is to copy overighting the DLL in the IIS bin folder and, then, in a webbrowser control request my site's home page first and secondly the /mobile/mobile.aspx page. This is because err_connection_refused only happens in mobile webbrowsers requesting that page and afterwards as a consequence of this all the site stops working.
    Since this workaround is in place the site has been working well several hours. I'll let you know if there is any change.

    Sometimes, requesting from the phone webbrowser, the page still fails but when the interval elapses (so the copy is done), the page and the site recovers.

    My domain is https://xrjunque.nom.es

    Monday, December 2, 2019 9:11 AM
  • User409696431 posted

    The post that started this question refereneced sites that hadn't changed in years, and the error message is different.  I would not assume your issue is the same at all.  A time out is a very different error from a refusal.

    Monday, December 2, 2019 3:09 PM
  • User1057802005 posted

    Thanks KathyW for your comment. Anyway, I am happy to see that my.godaddy.com/community that was down several hours ago, now seems to be OK. Something must have changed.

    Monday, December 2, 2019 3:54 PM