Jump to content

Matteo Beccati

Administrators
  • Content Count

    261
  • Joined

  • Last visited

Everything posted by Matteo Beccati

  1. During the installation, you should have seen something like: Installing Revive Adserver Plugin: Banner Types PluginOK while the installer was installing all the bundled plugins, e.g.
  2. Then there is something very wrong with your setup or hosting, or apache security modules. One of the last steps of the installer does also install the plugins.
  3. Perhaps the standard plugins are disabled or not installed.
  4. Did you just change that? Your logs where explicitly mentioning OA_Maintenance_Auto. Also 5 minutes operation interval is an extremely bad idea. Try setting it back to 60 minutes and schedule 1 cron job at minute 0. PS @andrewatfornax I really think we should remove the option.
  5. If you have messages stating that maintenance is complete, there is nothing you should be worrying about. You're using automatic maintenance and concurrent requests will try to trigger it: one will succeed and the others will rigthfully fail. I'd suggest disabling auto-maintenance and setting up scheduled maintenance via cron.
  6. My suggestion would be to try and restart MySQL. I do remember having seen once or twice such lock being stuck and not released.
  7. To everyone else that I haven't already contacted, if you are interested to help pls PM me. I'll send you my IP and SSH key to see if I can find any more clues.
  8. Research is still ongoing: we are in touch with a few affected users, but until now we haven't received enough evidence to understand how the malicious plugin or the php files in the images folder are being planted.
  9. Hi @scott001, I'm sorry - we must have missed this. We've had similar reports, but until now no one was able to provide any useful information on how the malware or compromised plugin files were injected in the first place. Do you have any older logs that could help?
  10. @Snaggy yes, absolutely. An/or you can find a pristine file in etc/plugins/openXBannerTypes.zip. The zipfile can be used together with the "Import" button in the plugin screen to overwrite the existing files.
  11. @tvvpmi Yes, please clean up your plugins/bannerTypeText/oxText/genericText.delivery.php file, which has most likely been compromised at some point. Unfortunately the logs sent by @sunech didn't cover the time when that happened.
  12. Thanks for your help. Would any of you allow me to have a closer look, in order to see if I can spot anything else that's unusual and possibly gather more information?
  13. data-revive-id is a hash calculated using the delivery and deliverySSL config values. @Adi The old one had "www" in the path while the new one doesn't, that's why you're getting a different id.
  14. It's a known incompatibility with the utf8mb4 charset: https://github.com/revive-adserver/revive-adserver/issues/740
  15. @olabre See my original reply. Testing upgrades from 2.0.11-pr1 is now part of the release process. Tags should also be compatible, as long as you are not using functionalities that have been removed.
  16. @OMG I believe you just need to make sure that This banner can be safely displayed inside an iframe (e.g. is not expandable) is checked in the banner-edit screen.
  17. As I said earlier, only "clickTag" is supported. Revive AdServer only supports a single destination URL.
  18. Revive only supports the main clickTag. They should also be using the JS variable thereafter, not an <a href
  19. I'm sorry, magic macros aren't supported in HTML5 banners. You should stick to the default, which is using clickTAGs. You should kindly ask your client to comply.
  20. Hi @tkat https://support.google.com/dcm/partner/answer/3145300?hl=en Look for Simple ClickTag insertion.
  21. @andrewatfornax maybe the plugin requires the revive-id field used in the async tags? @melamoccicata If so, just generate an asynchronous invocation code and copy the revive-id html attiribute value.
  22. @Maro Sorry, I can't possibly know how your servers are configured. Wordpress is not involved in that though.
  23. Your Apache or nginx is most likely configured to set the wildcard header, as Revive uses the Origin domain for async calls.
×
×
  • Create New...