Jump to content

joe_1592835

Approved members
  • Posts

    3
  • Joined

  • Last visited

About joe_1592835

joe_1592835's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. We just had the exact same problem pop up. Fifteen of our ad zones had a script included that loaded a coinminer.f JavaScript. These were all added into the table xxx_zones in the prepend column. To remove the coinminer.js script go into your database and pull up any xxx_zones where prepend or append is not null. You should see the script there and can delete it. More importantly I need to figure out how it got there. I just began looking into this, I will let you know what else I find. This came up right after we upgraded to revive version 4.1.1. That might just be a coincidence. I'll post what I find. I also disabled the prepend/append columns in the xxx_zones table since I do not use these. By "disabled" I mean I just changed their column type from text to char(1). This way nothing can be entered into those columns. Again though, most importantly I need to figure out how they got there in the first place since it means there is a hole somewhere.
  2. We have no stats for the days that the stats weren't working. So since I fixed the stats by upgrading Revive Ad Server last night, we have stats again for last night and today, but yesterday and the days before yesterday still show no stats at all. Does anyone know if it's possible to get the stats back for the days the stats were broken? Glad to see the updates coming in on Revive. Thanks for all your work!
  3. UPDATE: This actually appears to be a problem with our MOD_SECURITY module for Apache erroring out because the reponse body is too large. So this is most likely not a Revive Ad Server issue. I upgraded to fix the stats problem also. After upgrading to 3.0.4 I get an Apache 500 error when trying to use the stats tab on mywebsite.com/ads/www/admin/stats.php It doesn't seem to want to give me any error message to work off of. The debug log doesn't mention anything and there is no PHP error. The last line on stats.php $oStatsController->output(); triggers the 505 error.
×
×
  • Create New...