Elis have something wrong again, the original images didnt load at all

Fixed...25min of downtime and people complain ;(

oh sorry, I just came online.........so I dont really know

I've been curious for awhile, so I may as well ask, since it seems to have changed a long time ago.

As of right now, are there any maximum simultaneous downloads or connection limits on any of the servers?

If so, what are they?

Also, in the past, the site had an auto-banning mechanism for hammering which was in place. Is that long gone, have the limitations been relaxed, or is it now just completely silent?

admin2 said:
Fixed...25min of downtime and people complain ;(

Wouldn't it be worse if it were down for hours and no one cared? ;-)

Cyberbeing said:
I've been curious for awhile, so I may as well ask, since it seems to have changed a long time ago.

As of right now, are there any maximum simultaneous downloads or connection limits on any of the servers?

If so, what are they?

Also, in the past, the site had an auto-banning mechanism for hammering which was in place. Is that long gone, have the limitations been relaxed, or is it now just completely silent?

20 connections max per server, 10 download connections per server, anymore gets thrown in to a queue.

You'll get autobanned if you keep hitting any application urls, but you will not get banned for hitting any image urls

3 for the main images...

Sorry , but if anyone have the same problem with me?
the last 2 day, I usually get the message "403 Forbidden"
while viewing the image on elis.

I'm new here, so I dont know if I do something wrong or not, please tell me ^^

ryuuroden: are you blocking referrers?

admin2 said:
are you blocking referrers?

Out of curiosity I just tested it and Moe works just fine with referrers blocked. I'm not seeing any 403 Forbidden errors.

It seems even direct linking to original images from off site works even with referrers enabled >_<;;

You might considering fixing that unless you want people to be able to suck up bandwidth from offsite.

Remote linking is blocked on elis and ranka, it was just broken on sheryl.

petopeto said:
Remote linking is blocked on elis and ranka, it was just broken on sheryl.

I think it is broken on elis and ranka as well because it seems to be working over here.

Off-site linking doesn't work for any site for /image links (but it does for /sample).

petopeto said:
Off-site linking doesn't work for any site for /image links (but it does for /sample).

I see what was happening now.

Off-site linking doesn't work 'normally'. With 'normally' being the key word. Normally, direct linking to a /image link would auto-redirect you to the /sample.

I forgot I had abnormal adjustments applied to the site I tested off of, which in turn allowed me to direct link /image links. My mistake.

Why you are allowing such a simple workaround, I have no idea. Granted less than 1% likely even use it, so it's probably not a major issue. Even so, a small change could be made to make the workaround a bit more difficult.

(being vague on purpose so people who don't already know, don't purposefully begin exploiting it)

I notice that if I view some image, and then stop for 5-10 second before continues, then it's okie
but if i open the image rapidly , so the "403-forbiden" will appeare soon ^^!
How about the band rule of our site?

just curious
at what time (GMT+1 or whatever) is moes traffic the lowest ?

MDGeist said:
just curious
at what time (GMT+1 or whatever) is moes traffic the lowest ?

http://mrtg.imouto.org/

I'm not sure if this has been posted before, but you can greatly increase the rendering speed of moe by enabling http.pipelining.

reiserFS said:
I'm not sure if this has been posted before, but you can greatly increase the rendering speed of moe by enabling http.pipelining.

There should be restrictions in place to stop multiple connections to the server?

Radioactive said:
There should be restrictions in place to stop multiple connections to the server?

The limit of 20 connections per server isn't really relevant to HTTP Pipelining.

HTTP Pipelining doesn't make more connections, but rather more requests per connection. In other words, it actually reduces the load to the server by making fewer, more efficient connections, with the added benefit of reducing page load times for the user. Its use should be encouraged, as long as Moe properly supports it.

Interesting. I thought this was bad for the server?

I guess I might be mixing it up with another FF tweak.

Looks like Elis isn't very happy at the moment.

Radioactive said:
Looks like Elis isn't very happy at the moment.

Ignore me. Probably the usual mirroring issue.

The reason ranka could be a bit slow could be spoilerme...

elis was down for 6 hours earlier, was able to get back online while driving at 85 miles per hour on the freeway to work :p

admin2 said:
elis was down for 6 hours earlier, was able to get back online while driving at 85 miles per hour on the freeway to work :p

Deathrace 2000

Hit 88mph and you'll notice something interesting ^^

Feito said:
Hit 88mph and you'll notice something interesting ^^

Blue flashing lights, and sirens?

Speed of the new server?

Improved or got worse?

I am talking about 76.73.1.91 for reference...

germany :

KDE (big cable provider here)
~100-200k
rather shitty...

france :

OVH (100mbit root)
~150-250 with peaks to 550k
rather meh...

So europe wise i guess it sucks ;)
(kde ranka => ~ 1-2mb/s , ovh ranka => lol 6-10mb nighttimes )