Error message when accessing my own blog

April 27, 2004 2:08 AM

I can't look at my own weblog. I'm using Mozilla, and I get a message that says:

The file / cannot be found. Please check the location and try again.

I've tried to access it through the very few people who've linked me, and I get the same message. I've tried typing in, and I get the same message. What's going on?

Other blogspot sites do not seem to have this problem. I can access friends' sites with nothing going wrong.

Why is my computer calling my URL "/"?

posted by interrobang to computers & internet (15 comments total)

If you are talking about rassenfrass.blogspot.com, I can access it fine from here.

(IE6, W2K)

You might want to get rid of that Nedstat counter, it's been causing lots of trouble with loading websites lately.
posted by sebas at 2:17 AM on April 27, 2004

(The "view blog in new window" button on blogger doesn't work for me either, by the way. I absolutely have no intention of drawing attention to my shitty blog, but can anyone look at it, or is it just off-limits?)
posted by interrobang at 2:17 AM on April 27, 2004

sebas, that's it, but nedstat I can look at just fine. Is that the problem? Would that cause that weird "can't access / " message?
posted by interrobang at 2:19 AM on April 27, 2004

I can see it in Mozilla and IE6, interrobang. I don't know if caused your problem, but I agree with sebas - you ought to put the nedstat script as the very last thing that loads on the page (like under the "wiscoblogs"), that way if there's any trouble with nedstat, it shouldn't keep the rest of the page from loading.
posted by taz at 2:23 AM on April 27, 2004

taz and sebas, I've had the same template for the blog for a couple of years, and it's mainly because it took me so long to figure out how to get the comments in the right place.

The nedstat stuff has never given me any trouble before, so I don't understand why it's doing this now. I know that the nedstat stuff is in the wrong place - on my friends' sites, it's somehow at the bottom - and the wiscoblogs-thing is partially not there - but I'm not an HTML guy anyway.

Why am I getting this weird response from my browser that tells me that my URL is "/"? What the fuck does that mean?

(And, thanks.)
posted by interrobang at 2:29 AM on April 27, 2004

I do not know what that error message is you get. Did you try to access it using http://rassenfrass.blogspot.com/index.html as well?

The nedstat counter never caused me any problems before either, however on a few websites I visit the Javascript that comes with it has been really slow since last week. It causes the website to load in IE, however not display all of it. I read somewhere the company behind nedstat is in a bit of financial trouble, so it might be worth looking for another counter anyway.

I noticed on your site that first the nedstat counter is visible, and only after a few seconds the rest of the site comes up. Now this does not seem to be related to your cannot find "/" error, so it might be a red herring.
posted by sebas at 2:37 AM on April 27, 2004

Using that http://rassenfrass.blogspot.com/index.html makes it work, sebas. Maybe I should spend some time tomorrow re-working the template, as much as I can.

The nedstat thing has always appeared before everything else (just because I know nothing about how to handle this stuff), but it's never given me this problem before.

I guess I'll try to deal with this tomorrow. Thanks.
posted by interrobang at 2:45 AM on April 27, 2004

I've noticed some really weird errors with firefox / blogspot as well. (Blogs appear as flashing / underlined / orange nonsense) Clearing down the cache usually fixes it, so I'd try that first. I've got a feeling the error is caused by some kind of internationalisation or CSS error, but since the cache cleardown I've not been able to reproduce the error.
posted by seanyboy at 4:17 AM on April 27, 2004

I use BlogSpot and Firefox and I occasionally get that error. I've never been able to pin it down to anything in particular, but I suspect seanyboy may be on to something with the caching. I've seen it recommended that if you're on a reasonably fast net connection, that you should set your cache fairly small on the assumption that downloading it is faster than the hash table look up and disk read necessary to get it from disk.
posted by tommasz at 5:34 AM on April 27, 2004

interrobang, you need to take that whole section that begins with <!-- Begin Nedstat Basic Code and ends with End Nedstat Basic code --> and move it to the very bottom of the page, under the wiscoblog thing.

Also if you look at that wiscoblog code, you'll see that there's one spot where it has two less-than signs together (the section that looks like this: prev"><</a> ); if you change this so that it only has one < there (like this: prev"></a> ), it should work. (Just remember that every bit of code begins with a < and ends with a >. If you are missing one, or have one too many, it gets messed up.
posted by taz at 5:43 AM on April 27, 2004

This is a long-standing Mozilla bug. Basically, what would probably help would be to clear your cache, and do this, from the bug chatter: You don't have to clear the cache to get rid of the behavior. It works on my machine (Moz 1.6, Win XP) if you go to Edit -> Preferences -> Advanced -> Cache and change the "Compare the page in cache to the one on the network" to "Every
time I view this page"

Also, it should probably be 'prev>&lt;</a>' for the wiscoblogs code, if you want a < to show up.
posted by zsazsa at 5:55 AM on April 27, 2004

I get this error with several versions of mozilla on Fark sometimes and the cache setting zsazsa referenced seems to work.
posted by spartacusroosevelt at 6:48 AM on April 27, 2004

I've had this problem with Firefox on many different sites, usually when I don't let a page finish loading before hitting the 'back' button. Clearing the cache fixes it right up.
posted by dual_action at 7:27 AM on April 27, 2004

i used to get the same error running ie6. i would be unable to view *any* blogspot addresses at all, as well as occasionally google and finally mefi. so i swapped to mozilla and all is good.

i still have no idea at all what stopped them all from working, but as tommasz said, try different caching options and clear out the relevant cookies. this did help me with google, anyway.
posted by triv at 12:45 PM on April 27, 2004

Well, the problem seems to have gone away, but thanks, everyone.
posted by interrobang at 2:16 PM on April 27, 2004