Jump to content

andrewatfornax

Administrators
  • Content Count

    1,905
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. That definitely sounds like a good starting point, then. The plugins/etc directory should not be empty in the existing installation that you are attempting to upgrade from. You may need to go back to the existing installation, and resolve the issue with the plugins there (there are details on how to do that in the troubleshooting documentation on our site) before attempting the upgrade again. The upgrade process expects your existing installation's plugins to be present, and copies them over from there as part of the upgrade process. (We do this because you may have 3rd party plugins installed that Revive Adserver otherwise wouldn't know about; if we didn't copy them over, all those 3rd party plugins would be missing after ever upgrade.) Then you might have the same problem, or you might not, because you don't really give us any details about your problem other than "me too". You might be better off starting a new thread that provides some details about exactly what you did to get the issue you have, and provide some details about what you have tried/what you see in the logs.
  2. HTTP 503 errors are returned by the web server, under which PHP (and then Revive Adserver) runs. If you are getting HTTP 503 errors, you will need to investigate your web server logs, and use the web server documentation to track down why the web server is returning this, and resolve that issue. This is potentially (but not definitely) due to a performance issue with running the Revive Adserver code, but it's something you will need to confirm at the webserver - unfortunately, it's very unlikely to be due to a Revive Adserver code issue.
  3. I meant more that the directory includes "%clientname%" in it. That looks like it's supposed to be a variable that hasn't been replaced correctly. Is that really the literal name of the directory?
  4. Okay, unfortunately, neither do we, nor can we. 5xx errors are due to your server/webserver. They have nothing to do with Revive Adserver.
  5. That's clearly a log file spanning multiple days - only the parts that appear when you perform the action that isn't working are of any interest. Please edit the above post to remove all the data, and only leave what's relevant to the issue.
  6. Strange. No ad blockers installed? Details on checking the log file for errors here: https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken#ReviveAdserverBroken-Step8:CheckyourLogFiles
  7. Just noticed in the log files in the original post that there are lines like this: Failed to find package definition file /home/%clientname%/public_html/openx-421/plugins/etc/openXBannerTypes.xml They don't look right - is that really the correct path to the location of Revive Adserver 4.2.1?
  8. https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken
  9. "Nothing showed up". Can you please be more clear, with a screenshot? Did you get a blank screen? Did you get an error message? Did you tail the log files to see if anything appeared during this process?
  10. See our troubleshooting guide! https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken#ReviveAdserverBroken-HTTP500ErrorCode
  11. At the time of my reply, no, this is still on the todo list.
  12. Hi @stapel_eliz, This is intended functionality of Revive Adserver - advertiser accounts are there to allow advertisers to see what campaigns/banners they have, and view the statistics of their delivery, etc. Their account is not intended to have the ability to see details of zones etc. that relate to the independent website account(s) to which the banners have been linked.
  13. https://www.reviveconsultant.com/articles/what-to-do-when-you-suspect-your-openx-source-system-has-been-hacked/ may be of assistance here.
  14. Have you walked through our troubleshooting guides in the documentation?
  15. We have detailed information on how to diagnose this in our documentation.
  16. 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.
  17. 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?
  18. 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!
  19. 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...
  20. 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.
  21. 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...
  22. 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.
  23. 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?
  24. 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.
  25. 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!
×
×
  • Create New...