Ace Revenue & G-Wages Back-end is Down

[muffincrumbs]

Both http://acerevenue.com/ and http://gwages.com/ are showing a 410 (Gone) error. That is is a server error and is likely being addressed as I type this. Still it is good to let everyone know when it is showing up as a non-redirect dead page and we should hear from them I think to let us know when it will be back.

Also in other news my main site http://mobilecasinoparty.com suffered from a DDoS attack so i wonder if hackers are out in force again to cause all of us problems. It is still being worked on by a third party http://www.prolexic.com/ to stop the attack. Technically it is cyber crime

 

[Online18Casino]

Looks like they are back up now... And it looks like they did a little update to the backend.. Added a few new things, I like it.

Was it your index page being attacked, or another? I was having problems with XML-RPC about a month back, as well as spammers hitting my login files... The ithemes security plugin works pretty well for my site right now.

 

[paulajardine]

It's still showing the 410 gone error for me, and so are all of their casinos. Hopefully it comes back soon.

 

[Online18Casino]

That's very strange... Maybe it has to do with dns propagation or something..? Works from both my PC and phone, I can log in and everything.

 

[muffincrumbs]

Looks like they are back up now... And it looks like they did a little update to the backend.. Added a few new things, I like it.

Was it your index page being attacked, or another? I was having problems with XML-RPC about a month back, as well as spammers hitting my login files... The ithemes security plugin works pretty well for my site right now.

Glad you saw it for a moment, but it is still down for me too. Still not sure about how the attack was done. It is slowing down now thankfully.

Ill check out ithemes

 

[AussieDave]

Hey sorry to hear about the DDoS trouble muffins!

I swear by ZBblock because it stops all the crap before WP even loads

WP loads like this:

index.php (files only contains reference to loading: wp-blog-header.php)
wp-blog-header.php (instructs to load wp-load.php, then template-loader.php)

However, the include file for ZBBlock is located on the first line of wp-load.php Hence script kiddies, bad bots, scrappers you name it are blocked before WP loads. Far better option in my opinion that relying on plugins to protect a WP site once it's completely loaded.

Basically it stops all the crap at the front gate, before it knocks at your door

ZBblock is 100% free: http://www.spambotsecurity.com/zbblock.php

Here's just a couple of entries in yesterday's zbblock log file which stopped crap:

#: 3151 @: Wed, 11 Jun 2014 04:58:27 +1000 Running: 0.4.10a3 / 75
Host: 31.41.216.104
IP: 31.41.216.104
Score: 2
Violation count: 1
Why blocked: Network known to associate with malware, source: google.com/safebrowsing/diagnostic?site=AS:42655&hl=en (ASN-BESTHOSTING-0). No access allowed from Ukraine (CUST-IP-0038/UA-20140108)

---------
#: 3148 @: Wed, 11 Jun 2014 00:12:49 +1000 Running: 0.4.10a3 / 75
Host: 165.231.27.154
IP: 165.231.27.154
Score: 1
Violation count: 2
Why blocked: No registrations, or logins, from hosts listed as hostile on Stop Forum Spam (stopforumspam.com/removal) (local block).
Query: action=register
Referer: /wp-login.php?action=register
User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.72 Safari/537.36
Reconstructed URL: /wp-login.php?action=register

 

[paulajardine]

I was just informed by Vipin that this issue is specific to the new version of firefox and that everything (casinos/back end) are working fine on other browsers. They must be working on it or have fixed it now because I just checked and can now get into the back end. I also checked a few of the casino sites and they seem to be working now as well from firefox.

 

[Online18Casino]

Well that explains a lot.. I am one of the few that still uses IE for everything

 

[AceRevenue]

I'm sorry for the late response on this thread, but yes, that was correct. It was a small bug that kicked in with anything Firefox 3.X. Since this was the first time Firefox it version 3.x, it caused the error. Everything is good to go now, and as always, if anyone has a problem they can email me or call me (day or night)!

Thanks,

Dan