Why doesn't my site display properly?
-
When I access my site, all I see is a list of pages without any formatting. No buttons, no images, no layout, just a list of words along the left hand side of the screen. This problem occurs on multiple browsers (Firefox, Safari, Chrome) and multiple computers at various IP addresses.
The blog I need help with is: (visible only to logged in users)
-
Howdy,
To confirm, we’re looking at http://newmanlockhaven.org/ ?
I can’t duplicate—everything looks typical: https://cloudup.com/c8epbMQGFie
Were all of the computers on the same Internet connection/provider? Can you perform a traceroute to s0.wp.com, s1.wp.com and s2.wp.com using the instructions at Advanced Browser Troubleshooting?
Thanks!
-
Thanks for you quick response! Yes, the site in question is http://newmanlockhaven.org/
Here’s what it looks like for me:
http://postimg.org/image/4b6f4m2x9/And here’s what the WordPress.com site itself looks like for me.
http://postimg.org/image/w90ia9szz/As you can see, both are pretty screwed up.
The first traceroute is for s0.wp.com. Here it is:
Traceroute has started…traceroute to cs82.wac.edgecastcdn.net (72.21.91.111), 64 hops max, 72 byte packets
1 10.0.0.1 (10.0.0.1) 1.410 ms 0.756 ms 0.636 ms
2 * * *
3 te-1-2-ur01.lockhaven.pa.pitt.comcast.net (68.85.45.77) 14.354 ms 11.111 ms 11.148 ms
4 te-1-3-ur01.jerseyshore.pa.pitt.comcast.net (68.85.40.57) 10.471 ms 14.024 ms 11.183 ms
5 te-1-3-ur01.williamsport.pa.pitt.comcast.net (68.85.40.53) 10.771 ms 14.095 ms 11.059 ms
6 te-1-1-ur02.williamsport.pa.pitt.comcast.net (68.85.40.222) 12.676 ms 11.757 ms 11.906 ms
7 te-1-1-ur01.muncy.pa.pitt.comcast.net (68.85.40.226) 12.709 ms 11.789 ms 11.909 ms
8 te-0-4-0-3-ar03.lancaster.pa.pitt.comcast.net (68.85.52.113) 16.061 ms 16.745 ms 15.812 ms
9 69.139.168.13 (69.139.168.13) 26.680 ms 26.161 ms 27.563 ms
10 he-4-4-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.94.161) 30.431 ms 32.187 ms 31.637 ms
11 be-15-pe04.ashburn.va.ibone.comcast.net (68.86.84.222) 30.077 ms 29.512 ms 28.715 ms
12 50-242-148-166-static.hfc.comcastbusiness.net (50.242.148.166) 27.857 ms 29.452 ms 28.435 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * * -
The site was tried on two computers, but in different locations and different routers. Probably the same provider (mine is Comcast), because both computers were in the same small town. Though, I can’t be sure of the provider for the second computer.
-
Here’s the next one (s1.wp.com).
Traceroute has started…
traceroute to cs82.wac.edgecastcdn.net (72.21.91.111), 64 hops max, 72 byte packets
1 10.0.0.1 (10.0.0.1) 1.348 ms 1.337 ms 0.799 ms
2 * * *
3 te-1-2-ur01.lockhaven.pa.pitt.comcast.net (68.85.45.77) 13.325 ms 14.199 ms 11.612 ms
4 te-1-3-ur01.jerseyshore.pa.pitt.comcast.net (68.85.40.57) 10.314 ms 26.128 ms 11.420 ms
5 te-1-3-ur01.williamsport.pa.pitt.comcast.net (68.85.40.53) 10.302 ms 11.642 ms 11.642 ms
6 te-1-1-ur02.williamsport.pa.pitt.comcast.net (68.85.40.222) 12.711 ms 10.886 ms 11.919 ms
7 te-1-1-ur01.muncy.pa.pitt.comcast.net (68.85.40.226) 12.246 ms 12.366 ms 11.075 ms
8 te-0-4-0-3-ar03.lancaster.pa.pitt.comcast.net (68.85.52.113) 19.360 ms 19.132 ms 15.860 ms
9 69.139.168.13 (69.139.168.13) 25.453 ms 24.333 ms 23.603 ms
10 he-4-4-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.94.161) 30.422 ms 33.484 ms 31.982 ms
11 be-15-pe04.ashburn.va.ibone.comcast.net (68.86.84.222) 29.684 ms 31.449 ms 28.608 ms
12 50-242-148-166-static.hfc.comcastbusiness.net (50.242.148.166) 28.679 ms 29.249 ms 28.502 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * * -
And here’s s2.wp.com:
Traceroute has started…traceroute to cs82.wac.edgecastcdn.net (72.21.91.111), 64 hops max, 72 byte packets
1 10.0.0.1 (10.0.0.1) 1.376 ms 0.755 ms 0.652 ms
2 * * *
3 te-1-2-ur01.lockhaven.pa.pitt.comcast.net (68.85.45.77) 14.504 ms 13.131 ms 10.372 ms
4 te-1-3-ur01.jerseyshore.pa.pitt.comcast.net (68.85.40.57) 12.063 ms 14.175 ms 11.905 ms
5 te-1-3-ur01.williamsport.pa.pitt.comcast.net (68.85.40.53) 12.490 ms 10.978 ms 14.305 ms
6 te-1-1-ur02.williamsport.pa.pitt.comcast.net (68.85.40.222) 12.964 ms 10.070 ms 25.167 ms
7 te-1-1-ur01.muncy.pa.pitt.comcast.net (68.85.40.226) 12.012 ms 11.098 ms 12.011 ms
8 te-0-4-0-3-ar03.lancaster.pa.pitt.comcast.net (68.85.52.113) 16.359 ms 19.538 ms 15.857 ms
9 69.139.168.13 (69.139.168.13) 27.329 ms 27.831 ms 24.133 ms
10 he-4-4-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.94.161) 33.051 ms 31.622 ms 31.604 ms
11 be-15-pe04.ashburn.va.ibone.comcast.net (68.86.84.222) 29.612 ms 28.286 ms 29.126 ms
12 50-242-148-166-static.hfc.comcastbusiness.net (50.242.148.166) 28.366 ms 27.933 ms 29.228 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * * -
Well, I looked at some online discussions of this problem, and it seems that all I had to do was to reset my wireless router. Not sure why this was only a problem for WordPress, but the problem is now solved.
I guess I should look into getting another router?
Thanks,
Chris -
Hi Chris,
Hope you had a great weekend. I must first share with you a laugh I had—the service you shared the screenshots with added ads underneath it that I wouldn’t expect from a Newman center. Taken back for a second!
At this point, I wouldn’t suggest outlaying any cash for a new router—I worked at the Newman Center at UT-Austin for about five years before working on web geekery full-time, so the last thing I’d ask of y’all is to spend money when you don’t need to.
It’s possible that a DNS record or something to that effect was corrupted and stored in the cache on your router. It likely would have resolved itself in time, but resetting the router pushed that along.
If it happens consistently—whether it is WordPress or other sites as well—then I would contact Comcast (while it is still occurring) to ensure it is nothing upstream on their end and, assuming they say all is good, consider adding a router to the budget.
If you have any other questions or need anything else, please let me know! Hopefully things are relatively quiet with the students away!
Cheers!
-
Mr. Kraft,
Another Newman person, what a coincidence! Too bad we don’t have some kind of secret handshake or password to offer each other!
Thanks for all your help. The ads were hilarious weren’t they? I also thought about the incongruity as I sent the screenshots!
I will contact Comcast. Thanks for the advice. This router has been giving me other problems (like network timeouts when there’s more than one computer using it at a time), so maybe it’s to blame. Either way I’ll get to the bottom of it.
The students are all home for Christmas break, so it’s pretty quiet around here.
A peaceful and blessed Christmas!
Chris
-
Chris,
You don’t know the handshake? ;-)
If you have any other questions or need anything else, please do let me know.
Peace!
- The topic ‘Why doesn't my site display properly?’ is closed to new replies.
WordPress.com Forums 