Jump to content

andrewatfornax

Approved members
  • Posts

    2007
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. Hi @scalemates, Okay, that's really interesting! Could you please take a look in your debug log? There should be some output every hour when the maintenance script runs. Could you please capture just the output from the maintenance script, and post? (Possibly copy the contents of the current debug log just before scheduled maintenance, then empty the file, so that you can capture just the output from the maintenance script.) Thanks.
  2. Sorry @Korona, but I really have no idea what you are asking.
  3. Hi @Korona, Sorry, but it's not clear what you are now asking.
  4. Hi @kmanz, Glad to hear you fixed this, but for reference for anyone else, there's a step in the https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken page which covers broken/missing plugins, so following the troubleshooting guide for a "Broken Revive Adserver" does cover this! Thanks.
  5. The plugins required for the out-of-the-box Delivery Rules in Revive Adserver all included and installed by default. You don't need to add extra plugins, unless you have something specific that you want to add that's not provided by default. Please see: https://documentation.revive-adserver.com/display/DOCS/Site+Delivery+Rules https://documentation.revive-adserver.com/display/DOCS/Changes+to+Banners+and+Zones+Not+Appearing
  6. Sounds like an issue with iOS or the app - I can't see how Revive Adserver would change the size of the ad, given how it delivers the content....
  7. The usual cause of the UI not showing correctly are adblockers - see our documentation please! Otherwise, please submit a pull request in GitHub if you have discovered browser-specific UI layout issues. Thanks!
  8. A possibly more nuanced answer: No - you cannot use MySQL Slaves for read-only DB access with Revive Adserver - there is no support in the application to direct reads to slave databases, and writes to a master database. We do not recommend the use of distributed statistics any more - it's effectively unsupported. 14k ops (presumably database operations?) is not necessarily a large number - depends on the timescale. I have seen Revive Adserver running on a single MySQL and perform 2.5k ops per second. It really depends on what bottleneck you are seeing - and what other optimizations you have attempted re: performance. Maybe it's time to write a performance optimization guide....
  9. https://documentation.revive-adserver.com/display/DOCS/Tag+Settings
  10. https://documentation.revive-adserver.com/display/DOCS/Banners+Not+Delivering
  11. https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken
  12. Hi @martin_brack, Sorry, I am not 100% sure what you are asking here, however, I suspect that the following might answer your question: https://documentation.revive-adserver.com/display/DOCS/Banner+Selection+Mechanism That is - the order of selection is based on the order of the zone calls coming into Revive Adserver.
  13. Hi @scott001, @Oleg Rumjancev, @Dejan & other interested parties! Thank you very much for your posts above. Obviously, we want Revive Adserver to be as secure as it possibly can be, and reports from the community help us to do this. Firstly, it's very pleasing to hear from @scott001 that this is the first issue in over 10 years of use - I hope that helps to go to show that compromising Revive Adserver is not easy an easy thing to do! In terms of @scott001's post about the two back-door scripts having the same date/time as the rest of the release file, I would like to remind all users to always ensure they get Revive Adserver from the official website links, and to check the MD5 hashes of the files that we publish before using them. We have seen reports in the past where we suspect (but have not been able to prove) that users downloaded Revive Adserver from a non-official source, and that their systems were compromised in this way. (I am not saying that @scott001 definitely did this - I just wanted to reminder everyone to use the official source.) Having said that - we have double checked our releases, and they have not been compromised - so, the files @scott001 was seeing may have come from elsewhere. (It is possible to alter the creation date/time of files, so it's not a guarantee of when they were created.) In terms of the Revive Adserver team responding to posts such as these - unfortunately your post came during what (for all of us) was a bit of an end of year break. We, unfortunately, are not a large, well funded team, able to provide 24/7 support - this is a community forum (rather than a paid for support system), after all. (If you'd like to help us out, so that we can grow, and possibly move towards more core-team support, please see our Patreon page!). If, in future, anyone has concrete evidence of system compromise - with specific details that will help us figure out the cause - then please, do by all means raise a HackerOne issue. We are more likely to see and respond to comprehensive, detailed reports of issues there. (But please note we will not allow HackerOne issues that attempt to simply get personal support from the core team.) I do note that @Oleg Rumjancev has reported an inability to log a report in HackerOne, but as far as I can see, the system is working fine - it may be worth attempting this again, if you have specific information that could help us trace a vulnerability, please. I hope that all of this helps clarify what you can expect from the core team, and the best way to deal with and report security issues! Sincerely, Andrew
  14. I am not sure, but perhaps setting the size to "0x0" might be causing the issue - can you try setting an initial default size that's a positive integer for both dimensions - even though I understand that the banner is dynamic and may change size?
  15. https://documentation.revive-adserver.com/display/DOCS/Impressions+are+Too+Low ? Oh, wait - are you saying that you see a 10x higher number of impressions recorded in the data_bkt_m table than end up being summarised into the main statistics table?
  16. The core Revive Adserver project is completely free and open source - we do not sell any plugins "here" on any of the official Revive Adserver websites. I'm not 100% clear what you want to do - in your first post, you simply asked if you should buy some plugins for "sign-up / login / advertiser / publisher feature", and I assumed that you meant you wanted a "self-service" approach, where people could sign up and buy/sell advertising space. If that's correct, then yes, you either need to make that yourself, or obtain (buy or otherwise) a plugin from somewhere else to do this. "Self-service" is not a feature of the core, free, Revive Adserver project. HTH.
  17. Normally, the management of which URL you use to deliver a website under is something you need to manage with DNS records and/or your webserver configuration. This is mostly outside the scope of Revive Adserver.
  18. Check the webserver logs to see what it's trying to access when you get the 404 error?
  19. Check your web server logs to see where it is re-directing from, and to. That should help. Also, check your Revive Adserver config - it may be that the UI is configured to run on HTTP, and has not been updated to be HTTPS?
  20. Hi, Who do what do? Advertisers and publishers? If you mean them, then they don't do anything - Revive Adserver does not, unfortunately, offer a self-service model. It's an application for web publishers to manage their inventory - not to offer a self-service sales method.
  21. No immediate plans to develop this, no. I love the way you compare us with Google! If only we had that kind of budget! ?
  22. And just to be totally clear - if you want to talk to someone from Revive Adserver, then you will find us here. But as Ian said above, I think the "revive adserver mod website" you are talking about above is a 3rd party, and nothing to do with the core product and team.
  23. Ah, I see - I think it's stored in one of the core database tables?
×
×
  • Create New...