500 Internal Server Error?
Every PM I try to send or question I try to answer is met with a “500 Internal Server Error”. This has been happening for about 30 minutes now, is anyone else experiencing this?
edit: i should make it clear that I am able to send PM’s and post, but each time I get this erroneous message for some reason.
Observing members:
0
Composing members:
0
19 Answers
Lemme try answer this….....
Its a server overload, just too many people using Fluther at once. We must upgrade!
I don’t get the error message, but tonight, a lot of stuff won’t load and just stalls there when I click on something. Waiting long enough, I’d get the message too. It isn’t too uncommon, it’s happened here before, a few times.
I just stop the page and click again, that usually does teh trix.
I experienced that. I reloaded, was able to send the message. The person has already responded.
I’m not having any trouble with this, though I was having trouble earlier with something unrelated.
You might want to try clearing your cache and restarting your browser, though it definitely could be a server issue.
There was just another Spam explosion @FutureMemory. I don’t know if that could be contributing to your issue or not.
12:36Am CST I got a 500 error, too. & again 3 mins later…site is slow, too. Cache is clear and no other sites are slow for me
I just got a bunch by the shitload!
Yep, and now my GA’s aren’t always “sticking”.
It’s around 1:45 AM EST and a few mins. ago I did both a reset and a restart on my iPhone (the equivalent of clearing the cache and then some) and the site still hangs interminably with the occasional “server stopped responding”.
So, something is screwball with Fluther tonight.
Let’s face it, the mobile site is a rather stripped down version of the full Fluther, so should be loading speediest of all. Definitely kerwacky tonite.
kerwacky My favorite techie term ;)
This has happened to me on and off for months – I just never bothered to post about it until tonight. Same for anyone else?
Alright, I think I have this figured out. Turns out that the problem I was having earlier actually took the site down for minutes at a time. Since I was messing with it to see if it was a consistent problem, and so was Ben, trying to fix it, it was happening several times throughout the night. The good news is, he did fix it! Hopefully, that was the whole cause.
Response moderated (Spam)
Answer this question