Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. I am still stuck on v4.2.1 and nobody at Revive seems to notice this thread...
  3. Revive Adserver, cookies, Google Chrome v80 Revive Adserver, cookies, Google Chrome v80 Summary: With the release of version 5.0.4 of Revive Adserver on January 21, 2020, our software is now fully prepared for the upcoming changes regarding third-party cookies in Google Chrome v80. In more detail As announced by Google, Google Chrome v80 is due to be pushed to users in February 2020. This version implements what Google calls a “secure-by-default model for cookies”. Mozilla’s Firefox and Microsoft’s Edge are set to also implement this in the near future. Instead of trying to explain what this means, we would like to recommend having a look at the article posted on the Webmaster Central blog, Get Ready for New SameSite=None; Secure Cookie Settings. In case you find it hard to understand this rather technical article by Google, you could also have a look at article WTF is Chrome’s SameSite cookie update? On Digiday.com, which has a somewhat more humorous take on the matter. We released Revive Adserver v5.0.3 on January 14th, 2020, including some changes to the way we set cookies, with the aim of supporting the new directive. Unfortunately, the changes were not entirely successful, and a few days later we became aware of several issues affecting cookies. While the ad server still worked, several features that require cookies, for example frequency capping, did not. These issues have been tackled with priority. On January 21, 202, we released Revive Adserver v5.0.4, which fixes the earlier cookie issues and made some additional improvements to how Revive Adserver deals with cookies. We recommend updating to Revive Adserver v5.0.4 at your earliest convenience, so that you’re fully prepared for the release of Chrome v80 next month. Don’t want to update yourself? Alternatively, if you don’t want to spend any time on keeping the software up to date, we also have a Hosted edition that you can subscribe to. This is a Software-as-a-Service offering that uses the exact same software, and that will always be kept up to date with the most recent version. All you have to do is sign up, log in and use it. The post Revive Adserver, cookies, Google Chrome v80 appeared first on Revive Adserver. View the full article
  4. Same here. I udated version 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4 and every time: You are currently using Revive Adserver v5.0.4 (warning: database is stamped as v4.2.1) running on Apache 2.4.41, PHP 7.3.11 and MySQL 5.7.27-30.
  5. Hi, Can we show google ads from 1 google adsense account to huge number of publishers and portals through revive ad server ? If yes, how can we do it ?
  6. Last week
  7. The Revive Adserver team announces the immediate availability of Revive Adserver v5.0.4. We are pleased to announce the release of version 5.0.4 of the Revive Adserver software. This new version addresses issues with the creation and use of cookies that were discovered after the release of version 5.0.3 on January 14, 2020. It also addresses one security issue that has been discovered recently. Here is a list of changes in Revive Adserver v5.0.4: Fixed cookie based features (e.g. frequency capping) inadvertently broken in the 5.0.3 release. Full release notes for v5.0.4 can be found on our Github page. Security fix This version 5.0.4 contains a fix for one low risk vulnerability that was recently discovered and reported to us through our HackerOne security program. We recommend upgrading to the most recent 5.0.4 version of Revive Adserver as soon as possible. Download, install and upgrade Revive Adserver v5.0.4 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server(s) being used meet(s) the minimum technical requirements. Community contributions The continued development of Revive Adserver is being sponsored by community members, either financially or in the form of code contributions. We’re very grateful for the support we’ve received. If you would like to contribute to our project, please consider becoming a patron on Patreon.com. Another way to contribute to our project, is by using the Revive Adserver Hosted edition. The post Revive Adserver v5.0.4 released – includes security fix appeared first on Revive Adserver. View the full article
  8. Good evening, I lost some data because we have changed domain and everything else, and now I want retrieve the old data. I have the old db, so I created a new domain only for backup, I installed adserver, and i changed the name of table for try to retrieve those data, but nothing. I want retrieve the statistics of two editors of two months that we don't have. There is a query or other method to do this? Best regards
  9. MaxMind’s new license key for downloading GeoLite2 files Downloading and updating GeoLite2 files Revive Adserver version 5.0 comes with a new, completely rebuilt geotargeting plugin, capable of using the new GeoIP2 datafiles produced by MaxMind. Our software was developed to be capable of downloading the required GeoLite2 country datafile from MaxMind’s servers upon initial installation, or while upgrading from a version older than v5. It is also capable of keeping that datafile updated by downloading any newer files that MaxMind publish (usually on a weekly basis). We released Revive Adserver v5.0 on September 30, 2019. On December 18, 2019, MaxMind suddenly announced that they were going to implement a mandatory license model for file downloads and updates of GeoLite2 files. License keys for GeoLite2 are free of charge. Following MaxMind’s announcement, a new version 5.0.3 of the Revive Adserver software was released on January 14, 2020, which is capable of using your MaxMind GeoLite2 license key to download GeoLite2 datafiles. In this blog post, we explain how to obtain a free license key from MaxMind’s website, and how to use it in your installation of Revive Adserver v5.0.3 or higher. Step 1: sign up for a MaxMind license key As explained in the blog post by MaxMind, you can get a license key free of charge. The steps are: Sign up for a MaxMind account (no purchase required) Confirm your signup and set a password to access the MaxMind backend website Create a License key Step 2: Enter license key in geotargeting plugin settings Here is what you need to do to enter the license key you just obtained in the plugin’s settings: Go to your installed Revive Adserver v5.0.3 (or higher), and log in as a system administrator. If necessary, switch to Working as System Administrator in the top right hand corner of the screen. Now click the Plugins tab. Most likely the new MaxMind GeoIP2 Plugin is listed at the top of the list of available plugins. For this plugin, click the Details link in the same row. On the details screen, you’ll see two components. Click the Settings link in the first row. In this settings screen, you will notice a new settings field for the License Key. Paste the license key you obtained from MaxMind in step 1. Now click the Save Changes button. Step 3: Force download of GeoLite2 file (optional) If you’ve been using a prior version of the software that was capable of downloading the GeoLite2 country datafile without a license key, the software will now be able to do that again using the license key you just entered. By default, the software will check for new files during the maintenance process at midnight. If it notices that a newer file is available, it will download that and use it to replace the outdated file on your server. If you created a fresh install of Revive Adserver v5.0.3, or if you updated from a version older than v5.0, and entered your license key, it will now be capable of downloading the GeoLite2 country datafile. To force the system to do that right away, instead of having to wait until midnight, here’s how: Make sure you are still logged in as a System administrator, and that you are still Working as System Administrator. Go to the Plugins tab to open a list of the installed plugins. In the row for the MaxMind GeoIP2 Plugin you will see that the status column shows the plugin to be Enabled. Now click the Disable link at the right of the same row. The screen will refresh and the plugin’s status will have switched to Disabled. A new Enable link has come into view in same place. Click it to enable the plugin again. To avoid disrupting your ad serving, disable and enable within a few seconds. Once again the screen will refresh, but you may notice that it takes a few seconds. This is because at that very moment the plugin is proceeding to download the GeoLite2 country datafile from MaxMind’s servers. The time it takes to download it depends on the speed of your server’s connection to the internet. That’s all, your geotargeting plugin is now up to date. It will automatically keep an eye on any new versions of the GeoLite2 country file and download it once available. This will happen at most once every 24 hours, at midnight. Don’t want to get your own license key? Alternatively, if you don’t want to spend any time on configuring a server and installing the software, obtaining a MaxMind license key and setting that in the software, we also have a Hosted edition that you can subscribe to. This is a Software-as-a-Service offering that uses the exact same software, and that will always be kept up to date with the most recent version. All you have to do is sign up, log in and use it. We’ve already taken care of regular updates of the GeoIP data files for you! The post MaxMind’s new license key for downloading GeoLite2 files appeared first on Revive Adserver. View the full article
  10. HTTP 403 is a permission error. Check you webserver logs.
  11. I'd get rid of it, and install it from the official package!
  12. Maybe step 2.2 of https://documentation.revive-adserver.com/display/DOCS/No+Statistics ?
  13. How do I set the cookie SameSite for ox_install_session_id it comes back blank instead of none and returns a warning. The other cookie from the ads server returns samesite=none. Please advise. Kris
  14. Hello Revive team, I installed Revive 5.0.2 and after installation, while adding a banner I am getting a 403 Error. More details in the attached screenshot. https://drive.google.com/file/d/10kl1MMvT2wf3k0srZHNOL7eEvhbbt5eJ/view?usp=sharing https://drive.google.com/open?id=10kl1MMvT2wf3k0srZHNOL7eEvhbbt5eJ I checked all the write permissions for the following folders and they are correctly set: var var/cache var/plugins var/templates_compiled plugins www/admin/plugins www/images Could you please help me in resolving this issue? Many thanks in advance. Kind regards Sudhir
  15. Earlier
  16. Hi I run a Wordpress-site on on www.xyz.com/ and tried to install Revive at www.xzy.com/openx as proposed by the Softaculous installer. Running Revive 5.02 on Apache 2.4.41 and PHP 7.2.26 I can log into the admin interface and open the dashboard ( www.xyz./openx/www/admin/dashboard.php ) but when I press a "Save" button I'm getting a 404 page (e.g. I can edit the form at www.xyz.com/openx/www/admin/advertiser-edit.php but when I press "save" I'm getting a 404 with the same URL) Probably not a Revive problem but maybe you can give me hint where to look for a solution. Thx
  17. We still use a fairly old version v4.1.4 (Apache, PHP 5.6.30-pl0-gentoo und MySQL 5.5.62-38.14.) and since Jan 2 there a no more impressions shown. But ad clicks are still displayed. We have integrated Revive Ads on different systems and websites, but the problem of no impression-counts affects all. That's why I would rather guess, that the problem lies in the Revive configuration itself. What could that be? Thx for any help /ideas on that ...
  18. No changes related to this thread in 5.0.3: https://github.com/revive-adserver/revive-adserver/blob/v5.0.3/RELEASE_NOTES.txt
  19. We changed it to that and we're currently testing to see if it works. But I see a new version is out now. Was it fixed in the latest version?
  20. This new version is about the Samesite Cookie issue, as per changelog : Added support for the SameSite cookie directive which will soon be required by browsers in order to allow 3rd party cookies. I upgraded but I still get 4 warnings in the Chrome console when checking the websites were we display ads from our server : A cookie associated with a cross-site resource at our-adserver/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032. Is it still supposed to happen ?
  21. The Revive Adserver team announces the immediate availability of Revive Adserver v5.0.3. We are pleased to announce the release of version 5.0.3 of the Revive Adserver software. This new version has two new features, one is about the SameSite cookie policy for Google Chrome and other browsers, the other is support for registering a license key to enable download of MaxMind’s GeoIP2 files following the changes in MaxMind’s EULA. Here is a list of changes in Revive Adserver v5.0.3: Added support for the SameSite cookie directive which will soon be required by browsers in order to allow 3rd party cookies. Updated MaxMind2 database updates downloader to use a license key, according to their EULA changes. Full release notes for v5.0.3 can be found on our Github page. We encourage our users to upgrade to the new version 5.0.3 as soon as possible, so that they can benefit the most from the new functionality of Revive v5. Download, install and upgrade Revive Adserver v5.0.3 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server(s) being used meet(s) the minimum technical requirements. Community contributions The continued development of Revive Adserver is being sponsored by community members, either financially or in the form of code contributions. We’re very grateful for the support we’ve received. If you would like to contribute to our project, please consider becoming a patron on Patreon.com. Another way to contribute to our project, is by using the Revive Adserver Hosted edition. The post Revive Adserver v5.0.3 released appeared first on Revive Adserver. View the full article
  22. No, there’s currently no LTS version. Only the latest releases normally get security fixes.
  23. Still hopeful, bump. Maybe just a yes/no? Is it safe to stay on this version?
  24. It seems that nobody with a large list would every use the throttle features the way they are set up, as it will throttle every domain. Does anyone know if there is a plugin that would allow one to throttle only domains on a list? I have ~4-5 domains I need to throttle, but don't need to throttle gmail, hotmail, etc. If not, this would be a great feature to add.
  25. I still can't upgrade for the reasons listed above. It would be nice if they could look into this. I too have an old installation...I've been running it since it was PHPAdsNew, so way over 10 years.
  26. Are you on shared hosting, VPS or dedicated server? Prefer to optimize and tune your MySQL or MariaDB server. Moreover, try using Apache or even better, Nginx with some cache control headers for files, etc.
  27. Which Nginx version are you using? Use 775 rather than 777 on directories: var var/cache var/plugins var/templates_compiled plugins www/admin/plugins www/images Setup robots.txt - block search engines and bots to follow and index: User-agent: * Disallow: / Use the newest version of Nginx, PHP and Revive AdServer. Prefer to use HTTPS. Add HSTS header too. Use Gzip or Brotli, and add Cache headers (expiries, etag, cache-control for html, js, css, images ...). This can help too for security: location ~* \.(git|rb|inc|ht|bak|htaccess|sql|log|htpasswd|engine|info|install|test|po|sh|theme|pl|cgi|py|lua)$ { deny all; # log_not_found off; access_log off; } location ~ /\. { deny all; # log_not_found off; access_log off; } # XSS add_header X-Content-Type-Options nosniff; add_header X-XSS-Protection "1; mode=block"; if ($request_method !~ ^(GET|HEAD|POST)$ ) { return 444; } if ($http_user_agent ~ (Acunetix|libwww|libwww-perl|sqlmap|WinHttp.WinHttpRequest|WinHTTP|Zeus|curl|wget|scan|winhttp|HTTrack|havij|WVS) ) { return 403; } if ( $request_method ~* ^(TRACE|DELETE|TRACK)$ ) { return 403; } set $susquery 0; if ($args ~* "\.\./") { set $susquery 1; } if ($args ~* "\.(bash|git|hg|log|svn|swp|cvs)") { set $susquery 1; } if ($args ~* "etc/passwd") { set $susquery 1; } if ($args ~* "boot.ini") { set $susquery 1; } if ($args ~* "ftp:") { set $susquery 1; } if ($args ~* "http:") { set $susquery 1; } if ($args ~* "https:") { set $susquery 1; } if ($args ~* "(<|%3C).*script.*(>|%3E)") { set $susquery 1; } if ($args ~* "mosConfig_[a-zA-Z_]{1,21}(=|%3D)") { set $susquery 1; } if ($args ~* "base64_encode") { set $susquery 1; } if ($args ~* "(%24&x)") { set $susquery 1; } if ($args ~* "(127.0)") { set $susquery 1; } if ($args ~* "(globals|encode|localhost|loopback)") { set $susquery 1; } if ($args ~* "(request|insert|concat|union|declare)") { set $susquery 1; } if ($args !~ "^loggedout=true"){ set $susquery 0; } if ($args !~ "^action=jetpack-sso"){ set $susquery 0; } if ($args !~ "^action=rp"){ set $susquery 0; } if ($http_referer !~ "^http://maps.googleapis.com(.*)$"){ set $susquery 0; } if ($susquery = 1) { return 403; } location = /robots.txt { allow all; # log_not_found off; access_log off; } location ~ /nginx.conf { deny all; access_log off; # log_not_found off; } You can also use .htpasswd to protect the filder where your Revive Adserver is installed. So, if wrong user/pass, the visitor/client would get 401 error.
  1. Load more activity


×
×
  • Create New...