Jump to content

andrewatfornax

Administrators
  • Content Count

    1,865
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. Maybe give us some more information please - like where are you getting the first URL from? What type of invocation code tag are you generating?
  2. Hi @truegodtv, Take a look at Exclusive Campaigns and/or Companion Positioning.
  3. Hi @JMKL, Please see the section on 500 errors on https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken
  4. Hi @JMKL, Not at all - Revive Adserver supports both inline and overlay video ads out of the box: https://documentation.revive-adserver.com/display/DOCS/Inline+Video+banners https://documentation.revive-adserver.com/display/DOCS/Overlay+Video+banners The above thread was about the video player that is embedded in the page that the user will view. Revive Adserver does not provide such a player - just the capability to deliver video banners. The player used then needs to support the display of banners, using VAST 1.0, which is what Revive Adserver uses.
  5. Hi @remy_php, I can confirm that Revive Adserver does not currently support VAST 2.0 natively, and therefore, a plugin will be required for this. However, the core Revive Adserver team will not specifically recommend any one 3rd party plugin provider over another - please speak with those providers that you feel meet your requirements, and evaluate their offering carefully as you would with any other purchasing decision. Sincerely, Andrew
  6. 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.
  7. Sorry @Korona, but I really have no idea what you are asking.
  8. Hi @Korona, Sorry, but it's not clear what you are now asking.
  9. 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.
  10. Can you please post screenshots of the two banners in the UI? Looks to me like the one that is not working does not have any link information added to the banner...
  11. 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
  12. 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....
  13. 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!
  14. 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....
  15. https://documentation.revive-adserver.com/display/DOCS/Tag+Settings
  16. https://documentation.revive-adserver.com/display/DOCS/Banners+Not+Delivering
  17. https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken
  18. 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.
  19. 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
  20. 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?
  21. 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?
×
×
  • Create New...