Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. https://www.reviveconsultant.com/articles/what-to-do-when-you-suspect-your-openx-source-system-has-been-hacked/ may be of assistance here.
  2. Have you walked through our troubleshooting guides in the documentation?
  3. We have detailed information on how to diagnose this in our documentation.
  4. Sorry, I have no idea. If you have replicate steps that we could use to repeat the issue, then you could raise a ticket - but I'm afraid I don't have this issue myself when setting up Revive Adserver on MySQL 8.
  5. If all the delivery options are still not there, then you'll want to check out the campaign type next - is this a remnant campaign, or something else?
  6. Sure, as soon as I figure out where the template is, I'll happily update the GitHub ticket with the details. With all due respect back, this is an open source project. Yes, we ask for donations on Patreon, and we are very, very grateful for the members of the community who are willing to support us. We really, really appreciate it. But the current revenue from Patreon means that we no longer have to pay for costs to run the project out of our own pockets, and we get a very small amount of income. It's not like we don't all have other jobs that we have to work to make a living. If we could get the community to the point where we make enough from Patreon that we could dedicate most (or all) of our time to the project, that would be fantastic! But we are a long, long way away from that point. So, we do what we can to help the community, when we can. In the mean time, the source code is open, and we encourage the community to step through the code and improve it themselves, when they can. When they cannot, then unfortunately, like any other open source project, we will gladly assist, when and as we can. Thanks!
  7. As I said above - take the Delivery Rule options out. Does it then display, after the cache timeout period? If so, then put the rules back one by one, until you figure out which rule is preventing display. My guess is that https:// should not be part of the Site - Source...
  8. After removing the Delivery Options, you will need to wait 20 minutes for the cache to update... The removal of Delivery Options won't be instant. Looking at your first link http://amtaflorida.org/mine.html I can see that Revive Adserver is working - it's not returning any server errors - it's just deciding that there's no banner to display.
  9. Yeah, it's definitely fixable - I think I've seen you've updated the ticket in GitHub about this? I plan on looking at this for the next release...
  10. I think the issue is probably that your Delivery Options rules are "wrong" - I don't think that the protocol should be in the Client - Domain rule, for example. https://documentation.revive-adserver.com/display/DOCS/Client+Delivery+Rules#ClientDeliveryRules-Client-Domain I'd try this first: https://www.revive-adserver.com/faq/troubleshooting-banner-delivery/ Basically, remove all your Delivery Options, and try displaying the banner on an otherwise empty HTML page. Then slowly add back in all your various options as you have them now until it stops working, and you've found your problem.
  11. Hey @Marc_Juneau, That's really strange, I have never seen that before. Have you tried this with the web developer tools open, to check for any errors in calls being made, or checked the web server logs for errors? I also wonder if there are issues with setting the cookies, which might cause this?
  12. There's no new version of Revive Adserver at the time of this reply (see https://www.revive-adserver.com/support/requirements/) so the issue to me looks like your PHP being configured to display warning messages in the output. Revive Adserver does its best to disable the output of warning messages, but it can't always prevent it, depending on your PHP configuration. Take a look at the PHP documentation and see if you can disable warning message output, and things should work.
  13. Yes, there is - there's an XML-RPC API for this. Unfortunately, documentation for this is still on my todo list... But the API is there!
  14. Sounds like it might be a cookie issue. What version of Revive Adserver? Have you been through the troubleshooting guide?
  15. There's no OAuth or similar support in Revive Adserver at present. I'm not familiar with any 3rd party plugins that may offer this, but that's not to say they don't exist...
  16. There's no reason why this won't "work" in the sense that the new creatives for the banners will now display. The reason it's not recommended is you now have no statistics about the different banners, that's all.
  17. I'm not aware of any way of doing this with Revive Adserver - if the user is re-directed to another location before the banner impression can be recorded, then the impression isn't recorded.
  18. Have you tried the troubleshooting guide on banners not displaying?
  19. https://documentation.revive-adserver.com/display/DOCS/Banners+Not+Delivering
  20. Not sure what you mean by "staff" - do you mean the core Revive Adserver team?
  21. There is no native support for this, no. However, depending on your system, you may be able to mount the S3 Bucket as a filesystem, and point Revive Adserver to that mount point for image storage.
  22. https://documentation.revive-adserver.com/display/DOCS/Plugins+Incorrectly+Upgraded and https://documentation.revive-adserver.com/display/DOCS/Plugins+Missing+or+Disabled should cover you here.
  23. Most correct answer, as far as I am concerned: The user that your web service runs as needs permissions to read all directories (and all of the files and sub-directories) of the entire Revive Adserver installation; and The user that your web service runs as needs permission to write to all of the specifically listed directories (and all of the files and sub-directories underneath them). There you go - that's my view on the most correct answer - and you will notice I not said anything about how you should achieve that. This is because I can think of a number of different ways to do this, depending on your operating system and/or preferences about how you manage security. So, while it's the most correct answer, it's of absolutely no help to many (most?) of our users, because they don't have the technical experience needed to set this up. That's why we suggest something rather permissive in our documentation - we don't have time to support every single new user installing the software to get a custom setup that's just right for their security needs. We assume that if you're the kind of user who is concerned about getting the security requirements just right, then you have the capability to tweak the permissions to what your needs are. HTH!
  24. Er, okay, thanks @420, have I misunderstood the comment in https://github.com/revive-adserver/revive-adserver/issues/983#issuecomment-501910702 then?
  25. Hi @2ge, Unfortunately, the newer GeoIP2 databases are not yet supported in Revive Adserver - we are hoping to release functionality for that in Revive Adserver 5.0, but we're still a little way off that yet. You'll have to stick with the legacy previous versions for now, I'm afraid.
  • Create New...