Problem with website on subdomain (UP Down)

emouawad said 1 year, 1 month ago:

A strange thing is happening with me.

Access to a subdomain (http://testing.hasnaservices.com/testpage.htm) sometimes it returns a reply with the html page but sometimes it is offline (reply: couldn’t connect).

Tried to clear the cache, tried accessing the URI from a proxy, nothing.
The weird part is that the interval of this problem is seconds (sometime website UP, some other time DOWN) plus it is just plain html no ASP.

Please advice on this issue, this problem is driving me nuts.

Note that the subdomain does indeed contain an ASP.net project and can be accessed through http://testing.hasnaservices.com/home.aspx

In addition, i noticed that testpage.htm seldom shows while home.aspx never does (knowing that it is bigger in size and connected to an SQL database)

bryceh said 1 year, 1 month ago:

@emouawad

I am not sure what would be causing this. I am currently able to view both URLs:

http://testing.hasnaservices.com/testpage.htm

http://testing.hasnaservices.com/home.aspx

Are you getting any sort of error messages when the site doesn’t connect? Do keep in mind that with Windows hosting, you would want to name your homepage default.aspx. Check out the article below for the list of default file names:

https://gdhelp.godaddy.com/article/60

-Bryce

emouawad said 1 year, 1 month ago:

- I am getting: Error 109 (net::ERR_ADDRESS_UNREACHABLE): Unable to reach the server.

- Tried accessing the subdomain from a proxy – same issue.

- In addition I setup a service that checks up time using TCP at http://www.uptimerobot.com

- tracert

1 92 ms 89 ms 92 ms dsldevice.lan [192.168.1.254]
2 120 ms 120 ms 24 ms 10.150.0.1
3 26 ms 25 ms 25 ms 10.0.1.6
4 25 ms 29 ms 26 ms 10.9.8.130
5 25 ms 24 ms 24 ms 212.36.211.161
6 25 ms 24 ms 23 ms 212.36.211.40
7 * * * Request timed out.
8 342 ms 347 ms 343 ms 213.242.116.25
9 454 ms 400 ms 483 ms ae-7-7.ebr1.Paris1.Level3.net [4.69.143.238]
10 386 ms 416 ms 350 ms ae-23-23.ebr2.Paris1.Level3.net [4.69.143.126]
11 468 ms 419 ms 465 ms ae-41-41.ebr2.Washington1.Level3.net [4.69.137.5
0]
12 421 ms 463 ms 420 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.1
58]
13 452 ms 441 ms 433 ms ae-91-91.ebr1.Washington1.Level3.net [4.69.134.1
41]
14 488 ms 488 ms 504 ms ae-4-4.ebr3.LosAngeles1.Level3.net [4.69.132.81]

15 563 ms 491 ms 488 ms ae-83-83.csw3.LosAngeles1.Level3.net [4.69.137.4
2]
16 492 ms 521 ms 493 ms ae-3-80.edge2.LosAngeles9.Level3.net [4.69.144.1
43]
17 488 ms 490 ms 486 ms TIME-WARNER.edge2.LosAngeles9.Level3.net [4.53.2
30.62]
18 494 ms 495 ms 499 ms phx1-ar3-xe-0-0-0-0.us.twtelecom.net [66.192.249
.230]
19 498 ms 491 ms 495 ms be38.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.69
]
20 489 ms 490 ms 536 ms be38.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.69
]
21 487 ms 487 ms 488 ms be100.125.trmd0215-01.ars.mgmt.phx3.gdg [216.69.
188.30]
22 491 ms 491 ms 491 ms ip-216-69-188-126.ip.secureserver.net [216.69.18
8.126]
23 * * * Request timed out.
24 492 ms 565 ms 494 ms p3nwhg506.shr.prod.phx3.secureserver.net [173.20
1.60.1]

Trace complete.

Any ideas??

JasonP said 1 year ago:

@emouawad

The trace is concerning, especially the first hop within our network(secureserver.net)where it completes. Is this still an issue for you?

Keep us posted,

Jason

emouawad said 1 year ago:

I have been reviewing the same issue right now and the result is still the same.

i deleted the subdomain “testing” and “asktheexperts” from hasnaservices that pointed to hasnaservices.com/asktheexperts

the website is still though on /asktheexperts

btw pinging secureserver.net points to 97.74.104.208

Is it possible that the problem is specifically on the hosting server i used (shared), because i have other websites on other servers not having this issue.

JasonP said 1 year ago:

@emouawad

As long as the subdomains were added within the Hosting Control Center, and you created A records for “testing” and “asktheexperts” that pointed to the IP address of the server, you should have had no issue. Is there an active subdomain I can test?

Jason

emouawad said 1 year ago:

Both testing.hasnaservices.com and hasnaservices.com as expected point to 173.201.60.1

I re-setup “testing” as a new subdomain.

Plus i just ran a test now, I guess it is clearer now, the problem seems to be somewhere between my ISP and Godaddy’s Servers, Is that even possible? i’ve been having problems for the last week, could they be unaware of it.

Tracing route to hasnaservices.com [173.201.60.1]
over a maximum of 30 hops:

1 95 ms 73 ms 90 ms dsldevice.lan [192.168.1.254]
2 294 ms 174 ms 274 ms 10.150.0.1
3 392 ms 368 ms 340 ms 10.0.1.6
4 287 ms 370 ms 421 ms 10.9.8.130
5 579 ms 400 ms 362 ms 212.36.211.161
6 282 ms 307 ms 355 ms 212.36.211.40
7 * * * Request timed out.
8 595 ms 708 ms 680 ms 213.242.116.25
9 629 ms 637 ms 538 ms ae-7-7.ebr1.Paris1.Level3.net [4.69.143.238]
10 578 ms 549 ms 776 ms ae-22-22.ebr2.Paris1.Level3.net [4.69.143.122]
11 713 ms 755 ms 881 ms ae-42-42.ebr2.Washington1.Level3.net [4.69.137.5
4]
12 752 ms 694 ms 694 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
13 756 ms 605 ms 639 ms ae-71-71.ebr1.Washington1.Level3.net [4.69.134.1
33]
14 766 ms 813 ms 881 ms ae-4-4.ebr3.LosAngeles1.Level3.net [4.69.132.81]

15 816 ms 738 ms 877 ms ae-63-63.csw1.LosAngeles1.Level3.net [4.69.137.3
4]
16 * 854 ms 810 ms ae-1-60.edge2.LosAngeles9.Level3.net [4.69.144.1
5]
17 869 ms 900 ms 664 ms TIME-WARNER.edge2.LosAngeles9.Level3.net [4.53.2
30.62]
18 965 ms 663 ms 905 ms phx1-ar3-xe-0-0-0-0.us.twtelecom.net [66.192.249
.230]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
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.

Trace complete.

Your help guys much appreciated, Thanks for your help.

JasonP said 1 year ago:

@emouawad

That is a perfect trace. It looks like the issue is with twtelecom.net. It could be a switch or router that is down and not connecting to our network. Another way to confirm this is by using a proxy, such as megaproxy.com. It will probably take a different route to our network.

Jason