ut99.org connection trouble

[TheDane]

Hi there,

I've been having issues connecting to ut99.org lately, it's a bit weird as the issues comes and goes? First I thought it was Network issues as I often uses my phone to connect with, but other sites works fine even when this site is "down". I read over at Hooks that it seems to be time based? DDoS attacks perhaps?

Any news?

[Torax]

I had same last week.
Instead loading forums, it showed "Error 500"

[papercoffee]

It was the same for all member ...some server issue.
Only Shade can shed light upon this.

[Feralidragon]

Yeah, there were some problems, but I don't think it was an attack, given that something similar happened before and it was related to a memory leak. It seems it's everything alright now though, but like Paper said, Shade has still to explain what happened somewhat.

[Chamberly]

I have already reported the errors and problem to Shade (a few days ago), and sometimes it just configuration issue. Nothing to do with attacks.

Cheers. Case closed.

[EvilGrins]

Today is the first time I managed to login and reply to anything in several days.

Sadly, the comments I made were not that impressive.

[Spectra]

Even I had this same problem. It was showing some internal server error.
It seems that this Community is under heavy Attack

[Radi]

For me, this site is not available almost every night. Normally during day working but in later hours not.

[EvilGrins]

Funny thing about the comment I made above, about 15 minutes later I could access ut99.org at all. Even then some threads I couldn't get into even when I was logged successfully in.

It may well be this forum is finally dying, while the game continues to go on strong.

[Dr.Flay]

Hooray !
It's taken me all week to get in.
I have visited all the front-page threads via http://www.ut99.org.nyud.net, so they will still be readable via Coral for another 12 hours if the site locks-up again.
I have also swapped my news-feed in Opera over to http://www.ut99.org.nyud.net/feed.php

*EDIT*
Well I tested using Coral when it died last night, but it cannot work because the site is still contactable, so it will just fetch the error page.
Oh the irony.
For Coral to work, the site must either be functioning properly, or totally dead.

The site is still giving errors every time I use it at any time of day.

[Chamberly]

Just give it time guys, Shade have a life and so do we all.

Internal server error is just configuration stuff or so. Nothing to do with getting attacked.

[Skillz]

Actually the Error 500 is a catch-all error, it does NOT mean it's a configuration problem nor does it mean it isn't a configuration problem. It just means the web server could not fetch the page the client requested. This COULD be from an attack such as a DDOS attack, but I highly doubt this site is the target. It could be another site on the same server however.

[ShaiHulud]

The odd thing is that it seems to happen at approximately the same time each day, and for a similar duration. Also, each time it *does* happen I'm asked to log in again when the page finally loads. I'm not sure what these symptoms point to, but there's some consistency here.

[Feralidragon]

The error 500 is simply an internal error that the server didn't know how to handle, and it could be originated from anything, but it's still something the server didn't know how to handle internally.
Anyway, it's all up to Shade to check into it. I already let him know about the issues over a week ago, so it's in his hands.
There are things being done about it, that's why the site is now somewhat stable for a good portion of the time unlike before, but that's pretty much all the info we have atm about the state of things.

From there, until Shade makes a statement about the ongoing problems and if they are either fixed or not, any assumption on the actual problem is mere speculation and should be treated as such.

[RocketJedi]

the forum is very slow. I couldn't log in yesterday. Two min ago got the 500 error trying to login. something is still very wrong. maybe database is being hammered. Or its on a shared webhost and someone is running a cron job or something.