I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.
Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.
Apparently, some ISPs are blocking *.blogspot.com, or maybe have network configuration or infrastructure problems. You can access Blogger.com or you can access Blogspot.com, but you can't access nitecruzr.blogspot.com, or bloggerstatusforreal.blogspot.com.
You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.
Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):
And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post:
Remember to remove the inserted line breaks, when pasting either of the two above URLs.
(Note): Reading your blog, using an anonymising proxy server, is generally a free service provided by the proxies. Most proxies, though, aren't non-profit. They will charge a small fee for you to use forms and scripts, and other elements which are involved in writing to blogs. If your ability to maintain your blog, in addition to read it, is blocked, using an anonymising proxy server may cost you.
Update (19:30, October 23): Is this sorry situation repeating itself?
Update (6:00, June 21): Akhil informs us that the blogs are working.
Update (12:00, June 20): The Indian government is claiming that the block was an administrative error. The original govenment document (claimed scanned copy provided) very specifically defined individual websites to be blocked.
Update (18:00, June 19): Mac The Fork suggests Bloggers read about ongoing activities, then contact the Indian team CERT-IN, to discuss the situation.
Update (17:00, June 19): Jason of Blogger Support has issued one of their usual detailed analysis of the situation.
Update (15:00, July 15): The Google Feed Reader (and probably other feed readers) appear to access the feeds without having to access the blog itself. Enter the Atom feed URL, and you may be able to view the blog text. You won't see photos or fancy graphics, or scripts. Your sidebar won't be visible either. Just the post content.
Question: What the heck are you talking about? Blogger.com is not blocked, but myblog.blogspot.com is?
Yep, that's true. Open a command window, and enter "ping blogger.com". Look at the return.
Here's the important part
The IP address used by blogger.com is 66.102.15.100.
Now, do the same for your blog.
See the different IP address? That's why you can access Blogger (and post to your blog), but you can't access therealbloggerstatus.blogspot.com (and see what the heck is the problem). And that's why some folks get
Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.
Apparently, some ISPs are blocking *.blogspot.com, or maybe have network configuration or infrastructure problems. You can access Blogger.com or you can access Blogspot.com, but you can't access nitecruzr.blogspot.com, or bloggerstatusforreal.blogspot.com.
You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.
Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):
http://www.pkblogs.com/bloggerstatusforreal.blogspot.com/
2006/07/help-i-cant-see-my-blog.html
And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post:
http://bloggerstatusforreal.wordpress.com/
2006/07/15/help-i-cant-see-my-blog/
Remember to remove the inserted line breaks, when pasting either of the two above URLs.
(Note): Reading your blog, using an anonymising proxy server, is generally a free service provided by the proxies. Most proxies, though, aren't non-profit. They will charge a small fee for you to use forms and scripts, and other elements which are involved in writing to blogs. If your ability to maintain your blog, in addition to read it, is blocked, using an anonymising proxy server may cost you.
Update (19:30, October 23): Is this sorry situation repeating itself?
- I am Chinese... Open 10/25 Closed 10/26
- Problems with my URL Open 10/23 18:40
- Nothing Displayed Open 10/23 18:10 Confirmed OP is in Pakistan 10/24
Update (6:00, June 21): Akhil informs us that the blogs are working.
Update (12:00, June 20): The Indian government is claiming that the block was an administrative error. The original govenment document (claimed scanned copy provided) very specifically defined individual websites to be blocked.
- Plea to Manmohan Singh to lift blog ban
- Net gains: Blogspot to be back soon
- India blog block an 'error'
- DoT seeks explanation from ISPs for blocking sites
Update (18:00, June 19): Mac The Fork suggests Bloggers read about ongoing activities, then contact the Indian team CERT-IN, to discuss the situation.
Update (17:00, June 19): Jason of Blogger Support has issued one of their usual detailed analysis of the situation.
Update (15:00, July 15): The Google Feed Reader (and probably other feed readers) appear to access the feeds without having to access the blog itself. Enter the Atom feed URL, and you may be able to view the blog text. You won't see photos or fancy graphics, or scripts. Your sidebar won't be visible either. Just the post content.
Question: What the heck are you talking about? Blogger.com is not blocked, but myblog.blogspot.com is?
Yep, that's true. Open a command window, and enter "ping blogger.com". Look at the return.
C:\>ping blogger.com
Pinging blogger.com [66.102.15.100] with 32 bytes of data:
Reply from 66.102.15.100: bytes=32 time=20ms TTL=248
Reply from 66.102.15.100: bytes=32 time=16ms TTL=248
Reply from 66.102.15.100: bytes=32 time=17ms TTL=248
Reply from 66.102.15.100: bytes=32 time=16ms TTL=248
Ping statistics for 66.102.15.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 20ms, Average = 17ms
Here's the important part
Pinging blogger.com [66.102.15.100]
The IP address used by blogger.com is 66.102.15.100.
Now, do the same for your blog.
C:\>ping bloggerstatusforreal.blogspot.com
Pinging blogspot.blogger.com [66.102.15.101] with 32 bytes of data:
See the different IP address? That's why you can access Blogger (and post to your blog), but you can't access therealbloggerstatus.blogspot.com (and see what the heck is the problem). And that's why some folks get
502 Bad Gateway
Comments
I am the owner of http://freeproxylist.org web site and I want to make some kind of blog on it so after I will post some interesting article regarding how to use public proxy servers or how to keep user's privacy, they could ask questions and get answers.
The problem is that nowadays many users use blogs or forums to spam... or even more with vBulletin or phpBB they could get full access (forums have so much vulnerabilities) and upload some Trojans.
So what article you can suggest me to read before installing any blog on my web site?
Thanks in advance
And if you want a forum, look at a Google Group forum, which is text only.