Old issue- Can't access my blog.
-
Any help would be appreciated. I can’t access my WordPress blog.derekchristiephotography.com
Sometimes it loads half a page, sometimes it freezes and most of the time I get a timeout message. It happened with my last ISP so I used a VPN. It worked. I’ve changed ISP and it worked without the VPN but it’s grounded to a halt again but this time the VPN doesn’t help either.
Weirdly everyone I’ve asked say they can access it. Not sure if they are getting a cached version (I’ve really no idea if that’s relevant) and that’s why it works.
I need to update this daily for my work so it’s pretty crippling. Anyone got any ideas?
Cheers
Derek.
-
Your site seems to load fine from my location. I tested it using http://tools.pingdom.com. The load time from Stockholm, Sweden was 1.86 seconds, which is faster than 74% of sites tested by Pingdom.You can connect from various locations around the world by clicking Settings, below Test Now.
I tend to think the issue may be with your workstation versus your server. Do you have other workstations you can use to access your site? It would be ideal to access your site from a computer that hasn’t been used to view your site before.
Do you always test only when you are logged into your WordPress Dashboard? If so, test before you log into see if there is a difference.
I can help you more when you answer the above questions.
Hi wslade, thanks for the reply.
I have been on the phone to GoDaddy all morning and it seems it might be an issue with a server they manage in London.
I’ve added the trace route to the bottom of this post. IP: 195.66.225.28 seems to be causing issues but as they have told me in the past there end was fine as was my ISP, I sussed it must be wordpress. I even considered setting up a Squarespace blog but would lose all that SEO as I kept getting This error or literally hunderds of posts while importing:
ā [http://blog.derekchristiephotography.com/wp-content/uploads/2015/03/Louise-Andrew-E-Session-1791.jpg] is an attachment without a parent. Removing from the import.
So then I thought it could be a corrupt file structure. It does seem to be GoDaddy related and they said they are trying to resolve it but I won’t hold my breath. Looking at what I’ve posted does that fit with your suspicions?
Last login: Sun Feb 22 11:14:43 on console
Dereks-iMac:~ dtchristie$ traceroute blog.derekchristiephotography.com
traceroute to blog.derekchristiephotography.com (146.255.36.1), 64 hops max, 52 byte packets
1 bthomehub (192.168.1.254) 2.293 ms 3.410 ms 2.486 ms
2 217.32.142.196 (217.32.142.196) 6.255 ms 10.976 ms 7.385 ms
3 217.32.142.238 (217.32.142.238) 7.042 ms 7.433 ms 7.532 ms
4 212.140.206.210 (212.140.206.210) 14.563 ms 14.839 ms 14.006 ms
5 31.55.165.93 (31.55.165.93) 14.373 ms 13.791 ms 14.512 ms
6 31.55.165.107 (31.55.165.107) 15.996 ms 15.892 ms 16.144 ms
7 acc1-10gige-9-2-0.mr.21cn-ipp.bt.net (109.159.250.100) 33.245 ms
acc1-10gige-2-3-0.mr.21cn-ipp.bt.net (109.159.250.94) 16.121 ms
acc1-10gige-0-3-0.mr.21cn-ipp.bt.net (109.159.250.82) 15.507 ms
8 core1-te0-14-0-3.ealing.ukcore.bt.net (109.159.250.5) 24.232 ms
core1-te0-14-0-1.ealing.ukcore.bt.net (109.159.250.22) 23.269 ms
109.159.255.155 (109.159.255.155) 24.480 ms
9 109.159.254.239 (109.159.254.239) 23.400 ms
62.172.102.9 (62.172.102.9) 27.497 ms
109.159.254.239 (109.159.254.239) 24.936 ms
10 195.66.225.28 (195.66.225.28) 30.241 ms 28.348 ms 28.656 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * ip-208-109-115-209.ip.secureserver.net (208.109.115.209) 33.426 ms !X
23 * ip-208-109-115-209.ip.secureserver.net (208.109.115.209) 186.346 ms !X *
24 ip-208-109-115-209.ip.secureserver.net (208.109.115.209) 34.776 ms !X * *
25 ip-208-109-115-209.ip.secureserver.net (208.109.115.209) 30.568 ms !X * 36.035 ms !X
Dereks-iMac:~ dtchristie$Sorry, disregard my previous post. Pingdom is now reporting page loads in excess of 60 seconds and many images are not showing. I can see the missing images by going to their respective URL.
I’ll be back after I do some more testing.
Hi wslade,
Thank you for your help, really really appreciated as I’ve had this issue for ages now. Thank you.
Sorry for the delay. I decided to give Godaddy time to quit working on you server. They or something else was causing every test I ran to be different than the earlier ones.
The results seem stable but some are not good. Here is the Traceroute:
Hop IP Address Host name ms Lost(%)
1 176.221.87.4 4.87.221.176.pingdom.com 1 0
2 92.43.37.126 f126.broadband2.quicknet.se 1 0
3 10.5.12.1 1 0
4 212.247.178.9 1 0
5 130.244.39.46 vst-ncore-1.bundle-ether1.tele2.net 1 0
6 130.244.71.178 kst5-core-1.bundle-ether6.tele2.net 3 0
7 130.244.205.125 kst5-peer-1.ae0-unit0.tele2.net 2 0
8 195.219.36.13 if-13-4.har1.STK-Stockholm.as6453.net 2 0
9 80.231.89.33 if-7-1-0.core2.OS1-Oslo.as6453.net 8 0
10 80.231.152.41 if-8-3-1-0.tcore2.AV2-Amsterdam.as645… 28 0
11 195.219.194.5 if-2-2.tcore1.AV2-Amsterdam.as6453.net 28 0
12 195.219.194.2 29 0This looks better than what you had earlier.
Here is the really bad part – the page load time is over 60 seconds when tested from Amsterdam where the server is located! You can find the full page load info here. Note that it shows images that do not load, just as you mentioned. The server is timing out at 60 seconds. Who know how long it would keep trying if it weren’t for the time out?
Earlier I would have said it was a server and network issue. But now I’m puzzled. The problem can be almost anywhere. Check your error_log in the WordPress root for errors occurring today. Copy and paste the errors here or use pastebin and include the link if there is a lot of text. To conserve space, just copy only today’s errors and don’t copy the same error message over one time.
Next check to determine that your subdirectory is set up correctly. Your server is returning a 302 redirect for the blog when it should be a 200 (OK). It may be looping.
In cPanel go to Domains > Subdomains > Subdomain enter blog > Document Root > enter the subdirectory for WordPress example: /test. You probably don’t want to add anything in the redirection section. Test before moving on to the next paragraph.
Next look at the DNS Zone on your server for this account. Login to WHM Root > DNS Functions > Edit DNS Zone > highlight the zone for this URL > push enter. Look for an entry in the left column for blog. If blog isn’t there, add it with this data > 14400 > IN > A > same IP as ns1. Do the same thing for http://www.blog. If you made changes push save. Adding http://www.blog won’t fix your problem but it may prevent a future one.
Post what you find.
Sorry for the delay. I decided to give Godaddy time to quit working on you server. They or something else was causing every test I ran to be different than the earlier ones.
The results seem stable but some are not good. Here is the Traceroute:
Hop IP Address Host name ms Lost(%)
1 176.221.87.4 4.87.221.176.pingdom.com 1 0
2 92.43.37.126 f126.broadband2.quicknet.se 1 0
3 10.5.12.1 1 0
4 212.247.178.9 1 0
5 130.244.39.46 vst-ncore-1.bundle-ether1.tele2.net 1 0
6 130.244.71.178 kst5-core-1.bundle-ether6.tele2.net 3 0
7 130.244.205.125 kst5-peer-1.ae0-unit0.tele2.net 2 0
8 195.219.36.13 if-13-4.har1.STK-Stockholm.as6453.net 2 0
9 80.231.89.33 if-7-1-0.core2.OS1-Oslo.as6453.net 8 0
10 80.231.152.41 if-8-3-1-0.tcore2.AV2-Amsterdam.as645… 28 0
11 195.219.194.5 if-2-2.tcore1.AV2-Amsterdam.as6453.net 28 0
12 195.219.194.2 29 0This looks better than what you had earlier.
Here is the really bad part – the page load time is over 60 seconds when tested from Amsterdam where the server is located! You can find the full page load info here. Note that it shows images that do not load, just as you mentioned. The server is timing out at 60 seconds. Who know how long it would keep trying if it weren’t for the time out?
Earlier I would have said it was a server and network issue. But now I’m puzzled. The problem can be almost anywhere. Check your error_log in the WordPress root for errors occurring today. Copy and paste the errors here or use pastebin and include the link if there is a lot of text. To conserve space, just copy only today’s errors and don’t copy the same error message over one time.
Next check to determine that your subdirectory is set up correctly. Your server is returning a 302 redirect for the blog when it should be a 200 (OK). It may be looping.
In cPanel go to Domains > Subdomains > Subdomain enter blog > Document Root > enter the subdirectory for WordPress example: /test. You probably don’t want to add anything in the redirection section. Test before moving on to the next paragraph.
Next look at the DNS Zone on your server for this account. Login to WHM Root > DNS Functions > Edit DNS Zone > highlight the zone for this URL > push enter. Look for an entry in the left column for blog. If blog isn’t there, add it with this data > 14400 > IN > A > same IP as ns1. Do the same thing for
www.blog. If you made changes push save. Addingwww.blogwon’t fix your problem but it may prevent a future one.Post what you find.
There’s nothing wrong with your blog, it comes up fine for me. Whatever is causing your problem is a connection issue, not WordPress.
Thanks wslade I’ll make a start on all that after weekend.
Samuel, good to know so a connection issue might be the problem after all if you can read it. Any chance you can check a few more posts to see if they load ok too. Some have reported it slows when they’ve clicked on two or more pages.
Thinking I might move hosting to another provider as this may help if godaddy are causing connection problems.
The images are very slow from the U.S. Midwest. How big are they? If you’re not resizing them for the web, and uploading 3 or 5 meg photos, that may be a big problem.
The whole page is only 932 kb.
Yeah, I use BlogStomp to resize all the images so page size and image size shouldn’t be an issue. I’m definitely going to change hosts though.
Haven’t you had this issue with two hosts and four different servers?
- The topic ‘Old issue- Can't access my blog.’ is closed to new replies.