503 Error?
 

Why am I getting 503 - Server not available - errors whenever I try to read certain threads? There are posts being made to those threads, so other posters are presumably able to read them. Am I being slowly eased out? :sciencefail:

As a point of information, the threads I can't get to include:
J'Accuse!!
Kids in Restaurants
Dio/Ken S (or whatever it's called)
Real Estate Listings
An FDIC for Health Insurance

One thing I notice happen every now and again is that I will get Litespeed errors (possibly 503 errors also) on threads I haven't looked at yet. That usually means that it's time to clear out my cache, close my browser, and go back in again. Then everything goes back to normal.

ETA: Dammit, pick a forum! :fist:

I find that it's usually enough to just log out of the board then log back in. Since logging out wipes the board cookies that's generally all it takes. Sure does screw up the "new posts" button though!

Okay, logging off and then logging back in seems to have fixed the problem.

The screen I got did have something about Litespeed on it.

And the reason I started threads in two different forums was that when I I clicked the "Post Thread" button for the first one I got the 503 Error screen, so I thought that the thread wasn't posted. So I tried starting it again in a different forum, only to have the same thing happen.

Huh, that is strange. I haven't seen any problems connecting to the server myself over the past few days, and I'm not quite sure why cookies or cache issues would cause a 503 error. Let me know if you keep seeing it, and we'll try to figure out what's going on.

It had never happened before, or since I logged off and back on. What was strange about it was that I only got the 503 error when I tried to read certain threads. Other threads would open up normally. Even stranger, the two threads I started were among them; when I saw that there had been replies to this thread I had to go to "Read all posts by SmartAleq" and select her post in order to read the thread.

Huh. That makes me think that Uth's comment about clearing the cache is probably right -- certain stored threads get corrupted, and the browser thinks the site isn't loading.

Yeah, when the problem starts I will get the error on any thread I hadn't previously looked at. So I'd figured it was some kind of connection corruption on accessing unviewed threads.

Now that I think about it, I'm pretty sure that all of the threads I was having trouble with were ones I hadn't read yet. So I guess that was the problem.