EF under siege?

I wonder what's going on in past days. We had 1.4 finally, but since this day every time I try to enter www.Easternfront.org is mostly a failure. 503 error is occuring every time. Even hitting F5 button won't help. So what's going on? I went down to the end of forum main page and I found that mostly we have up to 100 visitor at the moment. I guess it's not so high amount. So I'm asking, just to get informed well ( I think I have right to ask :) ), what's happening? Is the server malfunction, or too many downloads at the same time? I hope I'll be able to read answer in next two days, if the present situation will carry on.

Cephalos

The auto-update feature on the launcher is tied directly with the site. Since there are massive amounts of downloads occuring the site is slow.

So it looks like the auto-updater bug is causing 503 errors?

That's not what I meant. I meant that the updater on the Launcher itself is tied to the site, not the auto-update feature, my apologies.

The servers are at 150% Compacity!!!!!!!

(Meltdown inevitable, losing life support systems)

I feel sorry for those with slow internet. lol  :'(

The devs really opened up Pandora's box when they released 1.4 and linked it to the auto update.

http://easternfront.org/forums/index.php?topic=5972.msg71675#msg71675

Thats Cope's explanation

Could Eastern Front buy a new server to stop this from happening?

pariah wrote:
Could Eastern Front buy a new server to stop this from happening?

Would take a lot more donating.

Any idea how much it would cost? I could chip in if i have to...

pariah wrote:
Any idea how much it would cost? I could chip in if i have to...

Didn't you already donate 500$? I'm sure others can chip in xD

Yeah, but that was what, 6 months ago? I could donate a few hundred more if need be.

pariah wrote:
Yeah, but that was what, 6 months ago? I could donate a few hundred more if need be.

I would prefer you buy a new rig and play EF :P.

Planning to mate, but Eastern Front is more important than my computer. ;)

We are working on a solution for future patches, should be out before 1.50 at least. We don't wanna stress something out, that it afterwards seen to not work as well as another solution. So, we'd think/talk some stuff over and get it right, then screw everything up.

I had to go to someones profile and then see what they posted to go on anything. ;D

lol, I just persist. If it displays error just press back and charge in again until the door comes down