Results 1 to 22 of 22
  1. #1

    Godaddy = Failure

    Probably nothing new. Seriously, they're horrible and everyone here probably knows it. But... I'm ticked, so I'll add something extra to show how genius they are.

    The problem is I can't seem to reach my website on godaddy. It appears as if the server is down. Both via the browser and ftp it fails.

    Anyway, I could write a review but no need... I'll let the e-mail I sent them and their responses do the talking.



    Okay, thanks for the information... I'm still humored that needing my pin is
    actual security considering it's listed on your website after I login. My
    password is way better security because it's never visible anywhere...
    anyway... based on the information you gave me here's what I have found out..

    The first instance of me not being able to reach the website was around noon
    EST yesterday. Earlier that morning I was on the website and had logged in
    via FTP. After noon the website was no longer reachable. This is a test from
    one computer.

    Around 6PM on a different network, the website was reachable from 3
    different computers, including the one it wasn't reachable from earlier that
    day. About 30 minutes later the website became unreachable again. Attempts
    to reach it from all 3 machines failed.

    This morning, I considered your response email and assuming the webserver is
    up like you stated, I decided to try another network. The website was up on
    that network. However, it is still down on the other two networks. It seems
    that the website works for a limited time on each network before something
    happens to keep the network from reaching the webserver.

    Attempts at pinging the webserver all fail.

    Doing a tracert to 2leet.com times out at the following:


    Code:
    1 4 ms 9 ms 3 ms 192.168.4.1
    2 30 ms 21 ms 32 ms 96.130.100.1
    3 15 ms 17 ms 10 ms ge-1-4-ur01.gray.tn.knox.comcast.net[68.85.207.
    161]
    4 15 ms 16 ms 15 ms te-8-1-ur02.gray.tn.knox.comcast.net[68.85.206.
    38]
    5 21 ms 17 ms 20 ms te-9-4-ur02.greeneville.tn.knox.comcast.net[68.
    85.206.33]
    6 24 ms 22 ms 13 ms te-9-4-ur01.bullsgap.tn.knox.comcast.net[68..85.
    206.85]
    7 16 ms 15 ms 13 ms te-8-4-ar01.bluelight.tn.knox.comcast.net[68.85
    ..206.81]
    8 60 ms 68 ms 69 ms
    te-0-8-0-4-crs01.b0atlanta.ga.atlanta.comcast.ne
    t [68.85.232.97]
    9 44 ms 41 ms 55 ms
    pos-1-3-0-0-cr01.atlanta.ga.ibone.comcast.net [6
    8.86.90.125]
    10 62 ms 66 ms 60 ms te-4-3.car1.Atlanta2.Level3.net[4.71.252.25]
    11 44 ms 52 ms 38 ms ae-63-51.ebr3.Atlanta2.Level3.net[4.68.103.30]
     
    12 63 ms 72 ms 71 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21]
    13 73 ms 67 ms 69 ms ae-71-78.ebr1.Dallas1.Level3.net[4.69.146.74]
    14 111 ms 95 ms 95 ms ae-8-8.car1.Phoenix1.Level3.net[4.69.133.29]
    15 95 ms 101 ms 99 ms ae-11-11.car2.Phoenix1.Level3.net[4.69.133.34]
     
    16 99 ms 99 ms 98 ms THE-GO-DADD.car2.Phoenix1.Level3.net[4.53.106.2
    ]
    17 * * * Request timed out.
    18 99 ms 97 ms 98 ms ip-208-109-112-142.ip.secureserver.net[208.109.
    112.142]
    19 103 ms 98 ms 99 ms ip-208-109-113-242.ip.secureserver.net[208.109.
    113.242]
    20 98 ms 103 ms 98 ms ip-208-109-113-241.ip.secureserver.net[208.109.
    113.241]
    21 123 ms 101 ms 98 ms ip-216-69-188-102.ip.secureserver.net[216.69.18
    8.102]
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29
    Immediately after hitting THE-GO-DADD we have an issue occur. It must be on
    your end. Also, I've ran the tracert mutliple times at the time outs occur
    at the same place.

    Thank you,


    And their wonderful, highly intellectual response:

    We have reviewed your account and server and it is functioning properly and responding quickly. The issue appears to be with the scripting on the site. You will need to optimize the code for efficiency to ensure it loads as fast as possible. (If your site uses databases, check those as well. Make sure all database connections are closed at the end of query.) For information on how to do so please refer to your preferred search engine or forum. I apologize for any inconvenience this may cause.

    Please let us know if we can assist you in any other way.

    Hmmm....
    {sarcasm} Can you guys point me in the right direction to how I can optimize code to login via FTP instead of getting "Could not connect to server", "Connection timed out"? {/sarcasm}

    You'd seriously think the tracert would have been sufficient information... apparently not.

    I'll keep you updated if they say more incredibly intelligent things that the world needs to hear to make themselves brighter individuals.

  2. #2
    Join Date
    Oct 2007
    Posts
    4,332
    Well based on the information that you have provided, I believe that your IP address is blocked by their server's firewall, possibly due to too many connections to the server at a specific time frame.

    Have you tried checking whether your website is loading fine through a proxy or through DownForEveryOneOrJustMe.com and Host-Tracker.com?
    [ James Lee - Cloud & Web Hosting Specialist 10+ Years WHT Veteran]

    [ Magento Performance Consultation by Magento Master ]

  3. #3
    JLHC, I agree with you.
    The problem is, Godaddy isn't smart enough to see it.

    Yes it works fine through a proxy.

    Also as far as connections go, no, only one computer with one connection caused it on one network, doing nothing that hasn't been done a million times before on godaddy. On the other network I had three connections but come on. LOL, if that's a problem...
    Last edited by Par; 11-04-2009 at 12:51 PM.

  4. #4
    Join Date
    Jul 2009
    Posts
    639
    Try esculating the issue to a better level tech or just move to a better host.
    bihira.com | 10+ Years of Web Hosting Experience!
    Shared Hosting | Reseller Hosting | 30 Day Money Back Guarantee
    cPanel | CloudLinux | R1Soft | Softaculous
    Find us on facebook and follow us on twitter @bihira

  5. #5
    Bihira, I may have to move to another host.

    While I don't care for my behavior, I got extremely aggravated with them earlier. I sent them this information and spent two more emails trying to get the woman to actually forward it on to a higher level tech. She kept trying to tell me it was my firewall and my code. So my posts and comments to godaddy today have been out of pure frustration. Inexcusably today, I've been a complete jerk.

    Anyway, I called them and I got to give them some credit here. The two techs I talked to were absolutely wonderful. Great to talk with, tried to help in every way possible and were extremely polite.

    That being said, they couldn't find the problem, and the advanced techs couldn't find the problem.

    You guys want to hear the details? It's quite a fascinating issue.

    On three different networks on two different isps I cannot access my website via ftp or http.


    Get this, on all three networks I could access my website via http and ftp. My inability to access the network seems to happen only after connecting via ftp and letting it timeout.

    That's pure speculation I can't prove this but it has happened on 3 different networks and only after I've connected via ftp and let it time out.

    Does this make any sense? Godaddy have told me they can't figure out the issue and can't solve the problem, that there is nothing they can do.

    Again I think my trace route clearly shows the issue is on there end...

  6. #6
    Join Date
    Dec 2007
    Location
    Indiana, USA
    Posts
    19,196
    It doesn't really surprise me that a company with a high customer:employee ratio like GoDaddy would rely entirely on canned responses.

    If you want friendly "We're looking into this for you now." and "We have found the issue to be X and doing Y will resolve it, would you like us to do that now?" types of tickets you're going to need to go with a smaller company...

    Even HostGator provides better support tickets by comparison.
    Michael Denney - MDDHosting.com - Proudly hosting more than 37,700 websites since 2007.
    Ultra-Fast Cloud Shared and Pay-By-Use Reseller Hosting Powered by LiteSpeed!
    cPanel • Free SSL • 100% Uptime SLA • 24/7 Support
    Class-leading support that responds in minutes, not days.

  7. #7
    Join Date
    Feb 2005
    Location
    Australia
    Posts
    5,849
    Quote Originally Posted by Par View Post
    Get this, on all three networks I could access my website via http and ftp. My inability to access the network seems to happen only after connecting via ftp and letting it timeout.

    That's pure speculation I can't prove this but it has happened on 3 different networks and only after I've connected via ftp and let it time out.

    Does this make any sense? Godaddy have told me they can't figure out the issue and can't solve the problem, that there is nothing they can do.

    Again I think my trace route clearly shows the issue is on there end...
    Have you recently changed your ftp client or settings? This would all fit with your ftp client opening too many connections, causing an automated system at their end to see it as an attack and block your IP.
    Chris

    "Some problems are so complex that you have to be highly intelligent and well informed just to be undecided about them." - Laurence J. Peter

  8. #8
    Join Date
    Feb 2006
    Location
    San Francisco, California
    Posts
    469
    Quote Originally Posted by foobic View Post
    Have you recently changed your ftp client or settings? This would all fit with your ftp client opening too many connections, causing an automated system at their end to see it as an attack and block your IP.

    +1

    Check if your FTP client is doing multiple threads for uploading via multiple connections at the same time.
    Larry Bly
    Sandbox IT Solutions, LLC.
    www.SandboxITSolutions.com
    Dedicated Servers - Web Hosting - Consulting Services

  9. #9
    Agreed guys. This issue I truly believe lies with the ftp. However, I connected via ftp on the third network and let it set for a couple minutes then disconnected. No problem I was still able to connect. The second time I connected via ftp I let it timeout. In order words, let their server say you've been connected and doing nothing for too long. Disconnect.

    Well, once this occurs I can no longer connect. Am I saying this is the issue? No. I'd have to do a few more tests. But it seems absolutely reasonable. I'm using the same ftp I've used many times. I have 3 godaddy hosting accounts. I have not changed the settings. It just seems to be happening now. I'm afraid to attempt causing an error with either of the other accounts as they are way more important than the one I am currently having issues with.


    That being said... let me show you the e-mails I've had with Godaddy so you can get an example of their email customer customer support.


    Godaddy emails in dark red

    My emails in dark blue

    Dear Jonathan Parsons,


    Thank you for responding. You have provided information to support that this is an intermittent issue. Unfortuantely, we cannot currently duplicate teh issue. To better review the matter please provide a list of the exact dates and times you have observed the site to be down.

    Alternatively, you can contact us by telephone at the time the site is down so that we may review the error.

    Please let us know if we can help you in any other way.

    Sincerely,
    Kathleen M.
    Online Support Representative


    Kathleen,

    The site isn't down, of that I am now sure. It's definitely up and working. The problem is coming from individual networks or ip addresses. I can use a proxy server, for example proxify.com and reach 2leet.com. I could go across the street to Panera bread and type in 2leet.com and the website will load (more than likely). The site being down appeared to be the problem on my original support request. Since then, I've done some testing and the website is up when I jump to different networks. However, some of these networks after a few minutes will no longer reach 2leet.com either. It's as if godaddy is blocking the ips for a random reason. I am not saying that is the problem, but it is a possibility.

    Now, 2leet.com as of the first time it became inaccessible from one of my networks as not been accessible from the network since. This is over 24 hours now, about noon EST yesterday. On another network around 6:30 EST 2leet.com became inaccessible and has not been accessible since. There were no changes to 2leet.com other than a simple css update and an image change when the first network became inaccessible. Nothing was different about the site than it had been for the last 3 months. This error is not due to a change I made, nor does it make sense that it would be.

    Again, this is definitely not due to a FIREWALL on my end. The tracert is VITAL INFORMATION and proves it's not my network that's causing the problem. Please do not overlook it, it is the key to fixing this problem. It tells any technician working on this problem where the error begins. I'll attach the tracert to the bottom of this e-mail again.

    It is not due to poor code, the site is ran off of wordpress, trust me, if it's poor code, then half of godaddy should be crashing. Likewise poor code will NOT prevent me from connecting via FTP. My IP cannot connect to 2leet.com, why? I have no idea, all I can do is tell you where it is getting held up, and it is getting held up at GoDaddy(somewhere after 208.109.112.142) where I have no ability to fix the issue. Your webserver may not be down, but something in the infrastructure isn't functioning properly and is causing networking blocking.

    I'm not a network admin by any means. I do; however, have a lot of experience with web administration and a decent amount of knowledge with cisco networking... If I was making an educated guess I'd say one of the routers/servers in the godaddy network is blocking IPs for some reason. Honestly I have two other sites on godaddy, both of which are working perfectly and run the exact same wordpress backend as 2leet.com.

    This exact error has happened to at least another person with another godaddy website. This details his problem:
    http://www.dslreports.com/forum/r232...y-site?j1=Back


    Thank you again,


    - Hide quoted text -
    1 4 ms 9 ms 3 ms 192.168.4.1
    2 30 ms 21 ms 32 ms 96.130.100.1
    3 15 ms 17 ms 10 ms ge-1-4-ur01.gray.tn.knox.comcast.net[68.85.207.
    161]
    4 15 ms 16 ms 15 ms te-8-1-ur02.gray.tn.knox.comcast.net[68.85.206.
    38]
    5 21 ms 17 ms 20 ms te-9-4-ur02.greeneville.tn.knox.comcast.net[68.
    85.206.33]
    6 24 ms 22 ms 13 ms te-9-4-ur01.bullsgap.tn.knox.comcast.net[68..85.
    206.85]
    7 16 ms 15 ms 13 ms te-8-4-ar01.bluelight.tn.knox.comcast.net[68.85
    ..206.81]
    8 60 ms 68 ms 69 ms
    te-0-8-0-4-crs01.b0atlanta.ga.atlanta.comcast.ne
    t [68.85.232.97]
    9 44 ms 41 ms 55 ms
    pos-1-3-0-0-cr01.atlanta.ga.ibone.comcast.net [6
    8.86.90.125]
    10 62 ms 66 ms 60 ms
    te-4-3.car1.Atlanta2.Level3.net[4.71.252.25]
    11 44 ms 52 ms 38 ms
    ae-63-51.ebr3.Atlanta2.Level3.net[4.68.103.30]

    12 63 ms 72 ms 71 ms
    ae-7.ebr3.Dallas1.Level3.net[4.69.134..21]
    13 73 ms 67 ms 69 ms
    ae-71-78.ebr1.Dallas1.Level3.net[4.69.146.74]
    14 111 ms 95 ms 95 ms
    ae-8-8.car1.Phoenix1.Level3.net[4.69.133.29]
    15 95 ms 101 ms 99 ms
    ae-11-11.car2.Phoenix1.Level3.net[4.69.133.34]

    16 99 ms 99 ms 98 ms
    THE-GO-DADD.car2.Phoenix1.Level3.net[4.53.106.2
    ]
    17 * * * Request timed out.
    18 99 ms 97 ms 98 ms ip-208-109-112-142.ip.secureserver.net[208.109.
    112.142]
    19 103 ms 98 ms 99 ms ip-208-109-113-242.ip.secureserver.net[208.109.
    113.242]
    20 98 ms 103 ms 98 ms ip-208-109-113-241.ip.secureserver.net[208.109.
    113.241]
    21 123 ms 101 ms 98 ms ip-216-69-188-102.ip.secureserver.net[216.69.18
    8.102]
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29


    Dear Jonathan Parsons,

    The trace route you have provided does not indicate that you are unable to connect to our servers, or servers are set to not respond to tracert requests, and therefore will show a timeout whether one occurred or not. To determine whether or not you are able to connect to the server we will need to see the full trace route results. Since this is only happening intermittently we will need you to contact our support while the issue is occurring. You may call us at (480) 505-8877. Our service departments and telephone lines are open 24 hours a day, 365 days a year to accommodate your needs anytime.

    Please let us know if we can help you in any other way.

    Sincerely,
    Jeremy P
    Online Support Technician



    I'm sorry but you are wrong.

    Asgamer.com which is also a website I have on godaddy does not timeout at the end. the traceroute completes.

    Microsoft Windows [Version 6.0.6000]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    > tracert asgamer.com

    Tracing route to asgamer.com [72.167.232.191]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 192.168.0.1
    2 11 ms 17 ms 32 ms 24-158-136-1.dhcp.kgpt.tn.charter.com [24.158.13
    6.1]
    3 39 ms 33 ms 25 ms 96-34-68-89.static.unas.sc.charter.com [96.34.68
    .89]
    4 9 ms 14 ms 9 ms 96-34-71-104.static.kgpt.tn.charter.com [96.34.7
    1.104]
    5 34 ms 40 ms 96 ms 96-34-71-129.static.kgpt.tn.charter.com [96.34.7
    1.129]
    6 58 ms 19 ms 30 ms bbr02spbgsc-tge-0-1-0-0.spbg.sc.charter.com [96.
    34.2.54]
    7 66 ms 40 ms 51 ms dca-edge-18.inet.qwest.net [63.148.64.145]
    8 98 ms 129 ms 92 ms scd-edge-01.inet.qwest.net [67.14.19.234]
    9 96 ms 97 ms 91 ms 63.227.225.70
    10 94 ms 96 ms 98 ms ip-208-109-113-149.ip.secureserver.net [208.109.
    113.149]
    11 95 ms 119 ms 92 ms ip-208-109-113-162.ip.secureserver.net [208.109.
    113.162]
    12 113 ms 129 ms 118 ms ip-216-69-188-74.ip.secureserver.net [216.69.188
    .74]
    13 95 ms 94 ms 138 ms ip-208-109-112-197.ip.secureserver.net [208.109.
    112.197]
    14 * * * Request timed out.
    15 100 ms 117 ms 94 ms ip-208-109-112-198.ip.secureserver.net [208.109.
    112.198]
    16 91 ms 114 ms 92 ms ip-208-109-113-242.ip.secureserver.net [208.109.
    113.242]
    17 118 ms 130 ms 92 ms ip-208-109-113-241.ip.secureserver.net [208.109.
    113.241]
    18 102 ms 96 ms 115 ms ip-216-69-188-102.ip.secureserver.net [216.69.18
    8.102]
    19 95 ms 95 ms 97 ms p3nlh061.shr.prod.phx3.secureserver.net [72.167.
    232.191]

    Trace complete.

    Can you explain why asgamer works and 2leet doesn't?


    Dear Jonathan Parsons,

    Thank you for your included trace from your ASGAMER.COM site. Unfortunately, we have not yet received the full trace from your 2LEET.COM site. We understand that you have included the bulk of the trace, however you have not yet included the trace in its entirety for us to review and properly support this issue.

    It appears that you are running your trace through Windows. You will notice your trace starts with:

    Microsoft Windows [Version 6.0.6000]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    > tracert asgamer.com

    Tracing route to asgamer.com [72.167.232.191]
    over a maximum of 30 hops:


    Please include the header portion of your trace for 2LEET.COM. Additionally, you will notice here that a trace route runs over a maximum of 30 hops unless it connects successfully earlier than that. Your trace route for 2LEET.COM ends at hop 29 and does not complete showing the error at the end. Your trace for ASGAMER.COM ends with 'Trace complete.' Please provide your trace in its entirety. We apologize for this request being redundant and we wish to assist in locating where the issue is and locate a resolution, however without the full error information, we cannot do so.

    Please let us know if we can assist you in any other way.


    Best Regards,

    Trevor P.
    Online Support Team



    Fair enough, I'm sorry what I sent you for 2leet.com is not a "COMPLETE" tracert. However, I want to be very clear with you guys. Your e-mail based technical support is far below satisfactory. I'm extremely disappointed in your ability to take the information I am giving and use it, better yet, I'm appalled by how you seemingly ignore it.

    First of all,

    GODADDY: "or servers are set to not respond to tracert requests, and therefore will show a timeout whether one occurred or not. "

    Seriously? Are you even being honest here or feeding me some lie? I've used tracert on 2leet, asgamer, and reneemccall.com. All of which I know are hosted by godaddy. Guess what, 2leet timesout after 216.69.188.102 and asgamer and reneemccall.com do not. Your servers do respond to tracert requests. What purpose was acting like they don't? I don't know what more you need I send you two tracerts and there is an OBVIOUS and HUGE difference between the two. Yet, you still can't tell if I can't reach your servers? The tracert for 2leet that is incomplete was entirely sufficient information. Considering I explained it repeats. Likewise, I've talked with your techs via phone and know 216.69.188.102 is a last hop before reaching the server. The multiple times the tracert timesout that I sent is all the information you need. However, since you want a "FULL" tracert, I'll give you a good one with 120 hops. Your welcome, you can see it time out 100 times.

    GODADDY: "Since this is only happening intermittently we will need you to contact our support while the issue is occurring."

    Wow. I don't know the number of times I've stated this is consistent but I know I have it at least once, quite clearly.

    "Now, 2leet.com as of the first time it became inaccessible from one of my networks as not been accessible from the network since. This is over 24 hours now, about noon EST yesterday. On another network around 6:30 EST 2leet.com became inaccessible and has not been accessible since. There were no changes to 2leet.com other than a simple css update and an image change when the first network became inaccessible. Nothing was different about the site than it had been for the last 3 months. This error is not due to a change I made, nor does it make sense that it would be."

    That's from a couple e-mails back. How in the world can you send me an e-mail that says this is intermittently when I have quite specifically told you it has "NOT BEEN ACCESSIBLE FROM THE NETWORK SINCE". I am extremely aggravated with your inability to actually read my e-mails. At first I thought I wasn't being clear so I decided to apologize for being brass. Now I'm sure you simply do not read. Honestly, I don't know why I'm typing all this, simply with a hope that a good technician will kindly read what I am sending. Please read the above italicized paragraph that I sent to you previously, it was obviously not read then, so I kindly ask that you read it now.


    DO NOT IGNORE THE FOLLOWING, PLEASE READ.

    Lastly, I'll give you some information to help you troubleshoot this problem. I gave this to a very helpful technician via phone last night, but I'll repeat so it's recorded by e-mail as well. Sadly I'm going to explain what I clearly explained above in italics from a couple emails back again in different words.

    As of yesterday's emails I had lost connection on two networks. Let me make this clear, I CANNOT REACH 2LEET.COM FROM EITHER OF THOSE TWO DIFFERENT NETWORKS AND HAVE NOT BEEN ABLE TO FOR OVER A DAY NOW ON BOTH. THIS IS NOT INTERMITTENTLY, IT IS CONSISTENTLY.

    Let me establish another point. I LOST CONNECTION ON A THIRD NETWORK LAST NIGHT.

    Now by lost connection, let me explain. I once could access 2leet.com on all three of these networks no problem. The first network stopped loading 2leet.com around noon 11/03. the second around 6:30PM 11/03. the third around 8:00PM 11/04. I understand debugging and these times are extremely useful debugging information. Why? Look at your logs and my ftp access. You'll notice I logged in via ftp around all these times. You'll probably notice I ftp'd around 8:00AM as well. So what's the difference. Here's what I know. Each time that I've completely lost connection on each of the three different networks it's occurred after your server has closed my ftp connection. You have some timeout on the ftp, it seems when that occurs something else happens and that IP gets locked out. It can no longer access the webserver. I'd consider looking at what kind of updates you've made recently and finding the bug.

    Btw, my ftp client is filezilla. Yes I know how to use it, yes I could connect to 2leet.com via ftp BEFORE THE NETWORK WAS BLOCKED. Currently I cannot access 2leet.com via the web browser or ftp on three networks. I repeat, I cannot access 2leet.com via ftp or web on three different networks and have not been able to since each network first lost connection as explained above... twice. Also attempts to connect via other ftp clients fail. I cannot connect via ftp or the web. Please don't try to explain to me how to ftp... I know how, it is not the problem. I was ftping fine before I lost all connection to 2leet.com

    And last, http://www.yougetsignal.com/tools/we...on-web-server/
    Finding a list of all the websites on the same ip as 2leet.com it times out on these as well. I cannot access that web server period. It is blocking me out.

    Here's your behemoth tracert:

    Microsoft Windows [Version 6.0.6000]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    >tracert -h 120 2leet.com

    Tracing route to 2leet.com [97.74.144.146]
    over a maximum of 120 hops:

    1 3 ms 2 ms 3 ms 192.168.4.1
    2 10 ms 16 ms * 96.130.100.1
    3 11 ms 9 ms 9 ms ge-1-4-ur01.gray.tn.knox.comcast.net [68.85.207.
    161]
    4 19 ms 10 ms 11 ms te-8-1-ur02.gray.tn.knox.comcast.net [68.85.206.
    38]
    5 12 ms 12 ms 17 ms te-9-4-ur02.greeneville.tn.knox.comcast.net [68.
    85.206.33]
    6 13 ms 12 ms 11 ms te-9-4-ur01.bullsgap.tn.knox.comcast.net [68.85.
    206.85]
    7 13 ms 12 ms 12 ms te-8-4-ar01.bluelight.tn.knox.comcast.net [68.85
    .206.81]
    8 39 ms 39 ms 51 ms te-0-8-0-4-crs01.b0atlanta.ga.atlanta.comcast.ne
    t [68.85.232.97]
    9 38 ms 39 ms 38 ms pos-1-3-0-0-cr01.atlanta.ga.ibone.comcast.net [6
    8.86.90.125]
    10 59 ms 40 ms 39 ms te-4-3.car1.Atlanta2.Level3.net [4.71.252.25]
    11 61 ms 42 ms 38 ms ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]

    12 72 ms 71 ms 71 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21]
    13 106 ms 68 ms 71 ms ae-71-78.ebr1.Dallas1.Level3.net [4.69.146.74]
    14 171 ms 212 ms 204 ms ae-8-8.car1.Phoenix1.Level3.net [4.69.133.29]
    15 94 ms 93 ms * ae-11-11.car2.Phoenix1.Level3.net [4.69.133.34]

    16 96 ms 98 ms 98 ms THE-GO-DADD.car2.Phoenix1.Level3.net [4.53.106.2
    ]
    17 * * * Request timed out.
    18 97 ms 97 ms 98 ms ip-208-109-112-142.ip.secureserver.net [208.109.
    112.142]
    19 98 ms 100 ms 96 ms ip-208-109-113-242.ip.secureserver.net [208.109.
    113.242]
    20 97 ms 97 ms 97 ms ip-208-109-113-241.ip.secureserver.net [208.109.
    113.241]
    21 98 ms 98 ms 97 ms ip-216-69-188-102.ip.secureserver.net [216.69.18
    8.102]
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.
    31 * * * Request timed out.
    32 * * * Request timed out.
    33 * * * Request timed out.
    34 * * * Request timed out.
    35 * * * Request timed out.
    36 * * * Request timed out.
    37 * * * Request timed out.
    38 * * * Request timed out.
    39 * * * Request timed out.
    40 * * * Request timed out.
    41 * * * Request timed out.
    42 * * * Request timed out.
    43 * * * Request timed out.
    44 * * * Request timed out.
    45 * * * Request timed out.
    46 * * * Request timed out.
    47 * * * Request timed out.
    48 * * * Request timed out.
    49 * * * Request timed out.
    50 * * * Request timed out.
    51 * * * Request timed out.
    52 * * * Request timed out.
    53 * * * Request timed out.
    54 * * * Request timed out.
    55 * * * Request timed out.
    56 * * * Request timed out.
    57 * * * Request timed out.
    58 * * * Request timed out.
    59 * * * Request timed out.
    60 * * * Request timed out.
    61 * * * Request timed out.
    62 * * * Request timed out.
    63 * * * Request timed out.
    64 * * * Request timed out.
    65 * * * Request timed out.
    66 * * * Request timed out.
    67 * * * Request timed out.
    68 * * * Request timed out.
    69 * * * Request timed out.
    70 * * * Request timed out.
    71 * * * Request timed out.
    72 * * * Request timed out.
    73 * * * Request timed out.
    74 * * * Request timed out.
    75 * * * Request timed out.
    76 * * * Request timed out.
    77 * * * Request timed out.
    78 * * * Request timed out.
    79 * * * Request timed out.
    80 * * * Request timed out.
    81 * * * Request timed out.
    82 * * * Request timed out.
    83 * * * Request timed out.
    84 * * * Request timed out.
    85 * * * Request timed out.
    86 * * * Request timed out.
    87 * * * Request timed out.
    88 * * * Request timed out.
    89 * * * Request timed out.
    90 * * * Request timed out.
    91 * * * Request timed out.
    92 * * * Request timed out.
    93 * * * Request timed out.
    94 * * * Request timed out.
    95 * * * Request timed out.
    96 * * * Request timed out.
    97 * * * Request timed out.
    98 * * * Request timed out.
    99 * * * Request timed out.
    100 * * * Request timed out.
    101 * * * Request timed out.
    102 * * * Request timed out.
    103 * * * Request timed out.
    104 * * * Request timed out.
    105 * * * Request timed out.
    106 * * * Request timed out.
    107 * * * Request timed out.
    108 * * * Request timed out.
    109 * * * Request timed out.
    110 * * * Request timed out.
    111 * * * Request timed out.
    112 * * * Request timed out.
    113 * * * Request timed out.
    114 * * * Request timed out.
    115 * * * Request timed out.
    116 * * * Request timed out.
    117 * * * Request timed out.
    118 * * * Request timed out.
    119 * * * Request timed out.
    120 * * * Request timed out.

    Trace complete.



    I know that's A LOT. But if someone want's to see how godaddy web support works. Here's a perfect example.

  10. #10
    Join Date
    Dec 2002
    Location
    India
    Posts
    1,433
    The support should know when to escalate an issue to a higher level or higher expertise person and these kinds of problems will not occur.
    Chris, Developer/Programmer,
    https://www.chrisranjana.com/
    Php laravel developers, Node Python developers,
    AWS Certified | Python developers | Nodejs Developers | Devops

  11. #11
    LOL, @chrisranjana the irony is this.

    I called last night and talked to them for over an hour and had advanced techs look into it. They said everything was fine and working correctly.

    The phone tech supports were extremely nice and helpful. However, so far it was completely useless. I'm very thankful for kind and understanding customer support but it doesn't fix the problem and this is somewhat out of hand. The site has been down on my network for 2 days now and godaddy's current response is nothing is wrong.
    Last edited by Par; 11-05-2009 at 11:44 AM. Reason: increased elaboration

  12. #12
    i have a host with godaddy and the connection is too bad

  13. #13
    Join Date
    Jun 2009
    Location
    UK: Oxford
    Posts
    1,259
    This clearly shows then they are not up to scratch.

    Even though they own their own network, it doesnt seem to be working.

    Maybe a hardware / software upgrade on a massive scale might in need for Godaddy.

    I know its pretty easy for me to say it, but i dont see how they can carry on with all these bad comments about their network and connection issues that keep getting raised.

    Obviously, something is wrong and they need to sort it out. If they are updating their software faster then they are updating the hardware, then there is 1 problem, and vis-versa.
    Garbott Ltd - Exceptional web development, hosting & consultancy services

  14. #14
    Join Date
    Oct 2007
    Location
    Reading, UK
    Posts
    602
    This is so bad is is almost funny, this is the problem with huge hosting companies
    Toby
    Xeo Solutions - Discovering Innovation
    Managed Service Provider & Cloud Hosting | Launching Late August 2019

  15. #15
    Join Date
    Oct 2007
    Posts
    4,332
    Your problem clearly seem to be your IP address being blocked by their server's firewall. Have you provided your IP address to them and request that they unblock your IP?
    [ James Lee - Cloud & Web Hosting Specialist 10+ Years WHT Veteran]

    [ Magento Performance Consultation by Magento Master ]

  16. #16
    @JLHC, yep. You can see it in the email I posted above.

    "I'm not a network admin by any means. I do; however, have a lot of experience with web administration and a decent amount of knowledge with cisco networking... If I was making an educated guess I'd say one of the routers/servers in the godaddy network is blocking IPs for some reason. Honestly I have two other sites on godaddy, both of which are working perfectly and run the exact same wordpress backend as 2leet.com."

    Haha, the biggest irony here is they have no problem telling me I need to check my firewall.

  17. #17
    Join Date
    Sep 2009
    Posts
    375
    Nothing new.. I agree to that.lol I have been hearing a lot of bad reviews from customer totally not satisfied with their service and support as well. And I believe it would keep going on unless they try to make improvements.

  18. #18
    someone once told me:

    never host with a registrar
    and never register a domain with a web host.

    i think its definitely not worth the trouble.
    how much have you lost in downtime?

  19. #19
    The problem may be fixed. GoDaddy forwarded it on to advanced technical support and an hour or so later I got a response thanking me for helping with the FTP issue and that it has been fixed.

    I'm assuming it was blocking IPs as I and some of you suggested. I just sent them my home network IP so I can get it unblocked.

    Anyway, if GoDaddy would have let me talk to advanced tech from the beginning I think we would have solved this extremely quickly. As of now, if it is solved it's been about 54 hours from the first incident.

  20. #20
    Join Date
    May 2008
    Posts
    48
    Par,

    Since they already fix it, but in the future, it does look like there server firewall did block you. I've just never heard of FTP timeout blocking network ips like this.

    Chris

  21. #21
    Join Date
    Oct 2007
    Location
    Reading, UK
    Posts
    602
    I've seen this happen before on our servers where a user is making loads of connections to FTP / another service and cPanel's bruteforce / DOS protect kicks in and bans them for 15min... cPHulk can be a real pain in the a*se to be honest.
    Toby
    Xeo Solutions - Discovering Innovation
    Managed Service Provider & Cloud Hosting | Launching Late August 2019

  22. #22
    Join Date
    May 2009
    Location
    United Kingdom
    Posts
    1,695
    Another bad review of GoDaddy.

    I would certainly recommend moving host. Have you looked at HostGator? I’m 100% sure they will provide the best support.
    Zomex ~ Templates & services for web hosting resellers since 2009!
    #1 Web Hosting Templates for WHMCS Templates | WordPress | HTML | Blesta | Clientexec
    █ Professional WHMCS Services | Installation | Configuration | Integration | Upgrades

Similar Threads

  1. Failure"Domain lookup failure"
    By ghasembaghi in forum Web Hosting
    Replies: 8
    Last Post: 05-30-2009, 03:48 PM
  2. GoDaddy sucks, at least for me [I hate Godaddy]
    By Barti1987 in forum Domain Names
    Replies: 19
    Last Post: 04-24-2009, 03:14 PM
  3. Replies: 19
    Last Post: 08-13-2007, 12:16 AM
  4. Replies: 4
    Last Post: 03-21-2006, 06:48 PM
  5. Expiring at Godaddy = backorder at Godaddy?
    By roughrider in forum Domain Names
    Replies: 8
    Last Post: 02-17-2005, 01:28 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •