• Brohoster: Proving their Excellent Services Yet Again
    3,001 replies, posted
just to play devil's advocate and get it out of the way before someone derps it out blindly, knowing the problem precisely like that isn't necessarily the most cleansing of excuses in the matter. Besides that, interesting to know, I'm sure Garry will appreciate the info. [editline]d[/editline] I guess garry appreciated it :slick:
[QUOTE=daijitsu;30674537]just to play devil's advocate and get it out of the way before someone derps it out blindly, knowing the problem precisely like that isn't necessarily the most cleansing of excuses in the matter. Besides that, interesting to know, I'm sure Garry will appreciate the info.[/QUOTE] I'm just going on what you said. A whole bunch of users appearing and then disappearing randomly while the server goes down since sockets are opened is how it works. My primary job deals with web servers. I know web servers in and out. I leave the game servers mostly to Andrew, Tyler, and Josh since that's what they do best. All I do is manage the servers for hundreds of thousands of websites across several companies. I see this stuff all the time. Moving to Litespeed on servers that attract it fixes it every time since Litespeed has basic ddos detection/prevention built in unlike Apache.
JWJ, sue Matt for slander. It's actually kind of fun to sit in a court room when you know you're right. (I've been in a court room. Idiot punched me. General prosecutor sued. Too bad he wasn't an adult at that time, might have been able to get loads e mone)
[QUOTE=CU-MattR;30674485]We were hit by the same type of attack last December by a Club Uptime competitor. It only affects those using Apache. Essentially, people open up a socket and never finish communicating with the web server, so the web server sits there waiting on a response from your browser until Apache times out on that connection. Move to Litespeed or Ngnix and you won't be vulnerable anymore. I do see that you're running an exploitable version of Apache. Once we moved to Litespeed, everything was fixed since we were no longer vulnerable AND we could handle about 20,000+ connections per second (previously just at over 3500 or so). [highlight](User was permabanned for this post ("Why are you here" - garry))[/highlight][/QUOTE] "My primary job deals with web servers. I know web servers in and out." We're using IIS. You just tested the redirection server. That's what the whole http 301 and URL Redirection thing is about. :rolleyes: We should definitely move to Litespeed based on that though.
[QUOTE=CU-MattR;30674485] [highlight](User was permabanned for this post ("Why are you here" - garry))[/highlight][/QUOTE] gf matt
Is Matt being helpful? Never mind he got banned,
[QUOTE=garry;30674614]"My primary job deals with web servers. I know web servers in and out." We're using IIS. You just tested the redirection server. That's what the whole http 301 and URL Redirection thing is about. :rolleyes: We should definitely move to Litespeed based on that though.[/QUOTE] I'll have you know banning someone is HIGHLY ILLEGAL.
[QUOTE=FlamingSpaz;30674652]I'll have you know banning someone is HIGHLY ILLEGAL.[/QUOTE] thats not even funny
Has he ever been helpful?
[QUOTE=deathmog;30674683]Has he ever been helpful?[/QUOTE] he's provided constant evidence against himself, I think that was pretty helpful.
Other than to crash into the earth and wipe out the dinosaurs? [editline]24th June 2011[/editline] oh wow automerge
[QUOTE=CU-MattR;30674485] Move to Litespeed or Ngnix and you won't be vulnerable anymore. I do see that you're running an exploitable version of Apache. Once we moved to Litespeed, everything was fixed since we were no longer vulnerable AND we could handle about 20,000+ connections per second (previously just at over 3500 or so). [highlight](User was permabanned for this post ("Why are you here" - garry))[/highlight][/QUOTE] And of course, you have no reason to use this to your advantage right?
[QUOTE=CU-MattR;30674485]We were hit by the same type of attack last December by a Club Uptime competitor. It only affects those using Apache. Essentially, people open up a socket and never finish communicating with the web server, so the web server sits there waiting on a response from your browser until Apache times out on that connection. Move to Litespeed or Ngnix and you won't be vulnerable anymore. I do see that you're running an exploitable version of Apache. Once we moved to Litespeed, everything was fixed since we were no longer vulnerable AND we could handle about 20,000+ connections per second (previously just at over 3500 or so). [highlight](User was permabanned for this post ("Why are you here" - garry))[/highlight][/QUOTE] It was good knowing you. Oh, wait, no.
Glad garry shorted that guy out, I laughed my ass off when he said we're running a vulnerable version of apache.
[QUOTE=:awesome:;30674739]Glad garry shorted that guy out, I laughed my ass[b] of when I he [/b]said we're running a vulnerable version of apache.[/QUOTE] wat
[QUOTE=:awesome:;30674739]Glad garry shorted that guy out, I laughed my [b]asses[/b] of when I he said we're running a vulnerable version of apache.[/QUOTE] wat
Ignorance can kill.
[QUOTE=CU-MattR;30674485][highlight](User was permabanned for this post ("Why are you here" - garry))[/highlight][/QUOTE] [img]http://sae.tweek.us/static/images/emoticons/emot-slick.gif[/img] [editline]24th June 2011[/editline] [quote] 02:54 ClubUptime lmao. Facepunch finally banned me 02:54 aaher2 LOL 02:55 GSV-P5 Lolz 02:55 ClubUptime I'm surprised it didn't happen days ago 02:55 GSV-P5 What reason did they give you ? 02:55 *** iRawrDinasawr is now known as Melodi- 02:55 ClubUptime "why are you here" 02:55 ClubUptime Someone posted up what the exploit was that they were hit with 02:56 ClubUptime and I told them how to close it so they wouldn't get hit again 02:56 ClubUptime and then they banned me 02:56 ClubUptime lmao 02:56 Melodi- Well. Lemme put it this way. Now we can stop worrying about it, and focus more on work. 02:56 Melodi- lmao 02:56 ClubUptime I really feel bad for them 02:56 ClubUptime They have this little board for people who get banned 02:56 Melodi- How come? 02:56 Melodi- Mhm? 02:56 ClubUptime I opened up a thread named "I apologize?" and put this in there 02:56 ClubUptime "Trying to work with you guys is useless. I'm really not the evil asshole that you all make me out to be: You're just taking the word of one person as the penultimate truth and completely brushing off everything I say without even considering it. But, that's fine. 02:56 ClubUptime Gary: If you ever decide to take the advice I posted up on closing up that exploit, you're welcome. " 02:57 Melodi- xD They aren't goin to like that. Nice. 02:57 ClubUptime Heh 02:57 ClubUptime In the end, whatever 02:57 ClubUptime No matter what I do they'll hate me because of who I am 02:57 ClubUptime I sit there and help them over and over, and they brush me off 02:57 ClubUptime So 02:57 Melodi- I'm guessing that several people here are streaming this straight to JJ's channel. [b]02:57 ClubUptime fuck them [/b] 02:57 Melodi- ^ 02:58 ClubUptime Yup 02:58 ClubUptime Probably 02:58 ClubUptime I could care less [/quote] he mad
[QUOTE=garry;30674614]"My primary job deals with web servers. I know web servers in and out." We're using IIS. You just tested the redirection server. That's what the whole http 301 and URL Redirection thing is about. :rolleyes: We should definitely move to Litespeed based on that though.[/QUOTE] One of your best posts.
Some mod please post in his RC thread: "We're using IIS dumbass."
[QUOTE=JWJ;30675088][img]http://sae.tweek.us/static/images/emoticons/emot-slick.gif[/img] [editline]24th June 2011[/editline] he mad[/QUOTE] he always mad. but watch out, saying he's mad is HIGHLY illegal and his lawyer is drafting up a cease and desist letter AS WE SPEAK.
[QUOTE=JWJ;30675088][img]http://sae.tweek.us/static/images/emoticons/emot-slick.gif[/img] [editline]24th June 2011[/editline] he mad[/QUOTE] Did he make a threat against every Facepunch user? We all should sue him v:v:v [sp]Kidding.[/sp]
[QUOTE=JWJ;30675088][img]http://sae.tweek.us/static/images/emoticons/emot-slick.gif[/img] [editline]24th June 2011[/editline] he mad[/QUOTE] 02:57 ClubUptime I sit there and help them over and over, and they brush me off lol
[QUOTE=:awesome:;30675178]02:57 ClubUptime I sit there and help them over and over, and they brush me off lol[/QUOTE] Well he was helping us. By giving us evidence... against himself.
Funny. Even I noticed that the http headers showed the redirect. If im correct, IIS runs at kernel level, meaning if IIS crashes, everything else does. Correct me if im wrong. Maybe thats what he was relying on?
[quote]02:57 ClubUptime I sit there and help them over and over, and they brush me off [/quote] DDoSing is not helping. This man needs psychological help.
[quote]02:55 ClubUptime Someone posted up what the exploit was that they were hit with [/quote] I think he honestly needs a doctor if his memory is as short term as it's been throughout this whole predicament. He explained it himself ...in the post he got banned for a fucking HOUR ago
I want a freepass to talk to him in red member forum :saddowns:
It's nice to see the entire drama of Brohoster play out before the thread autolocked. Pretty close though Or not
Did he just try to DDoS us again?
Sorry, you need to Log In to post a reply to this thread.