Fosterhood tumblr loading page issues
July 30, 2013 9:15 AM   Subscribe

I like reading the blog Fosterhood, but ever since I moved last week and got new internet from TWC (not sure if it has anything to do with it, but that's the timing) I'm only getting this on the loading page: "Not Found The URL you requested could not be found." I can access material in archives that has been posted since the move so I think it's me and not the site. How do I fix it?

I'm using Chrome, and I also installed AdBlockPlus like two days ago but it stopped working before that. I also paused ABP and it didn't help.
posted by vegartanipla to Computers & Internet (8 answers total) 1 user marked this as a favorite
Why is that ap_index thing tacked onto it?

The whole thing works fine for me without it.
posted by Sequence at 9:18 AM on July 30, 2013

Response by poster: I don't know. That's what my computer is rerouting to when I type in or when I click her own banner.
posted by vegartanipla at 9:19 AM on July 30, 2013

Can you not just read it at the real address of I think someone has fucked up the redirect for the domain name.
posted by DarlingBri at 9:27 AM on July 30, 2013

It's not there for me. And it's not there via Anonymouse.
posted by Chocolate Pickle at 9:28 AM on July 30, 2013

Response by poster: Nope, the real address takes me straight to the ap_index thing. Chocolate Pickle's Anonymouse link sends me to:

which has the same error.
posted by vegartanipla at 9:31 AM on July 30, 2013

Best answer: Clicked DarlingBri's link above and got to the site; the reported URL in my address bar is "".

I'm using the current Firefox release on a Mac; also tried Chrome on Mac and that works fine too.

(Sorry, I know it's frustrating to get answers that just say "It works for me", but I don't see the problem. Maybe empty your cache or reset your browser?)
posted by RedOrGreen at 10:12 AM on July 30, 2013

Best answer: RedOrGreen: "Maybe empty your cache or reset your browser"

This screams browser cache issue to me. There's definitely no redirect on that site to ap_index currently:
wget -O /dev/null
--2013-07-30 13:17:15--
Resolving (,
Connecting to (||:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16238 (16K) [text/html]
Saving to: `/dev/null'

100%[============================================================================>] 16,238 --.-K/s in 0.006s
(note the lack of an HTTP redirect in the output above - no 30x status code, no GET of anything other than index.html)

Perhaps try reloading the page not from cache ?
posted by namewithoutwords at 10:22 AM on July 30, 2013

Response by poster: Ok, I'm pleading post-move tiredness and confusion for why I didn't try that before posting; I've had to clear the cache/cookies/data before when Chrome has taken issue with Gmail. Anyway, that appears to have fixed it.

Thanks, all!
posted by vegartanipla at 10:25 AM on July 30, 2013

« Older Seeking cell phone advice for non-savvy pensioner   |   What does a new temp employee do when there's... Newer »
This thread is closed to new comments.