Jump to content


Approved members
  • Content Count

  • Joined

  • Last visited

Everything posted by scott001

  1. Ok, it might take me a week or so, but I'll get it together...
  2. yes, but is it possible for me to flush out most of the subscribers beforehand?
  3. Can you please tell me exactly what you added and where? That would be a huge help...thank you!
  4. Please ignore the post I made...got my forum's confused! I still haven't attempted an upgrade due to the database issue. Is there any news?
  5. I am still stuck on v4.2.1 and nobody at Revive seems to notice this thread...
  6. 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.
  7. 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.
  8. After upgrading recently I am now getting Can't Reach Site errors when running the process bounces in the ACP. This never happened before. Any ideas? Also, I still cannot upgrade and haven't gotten an answer here: https://forum.revive-adserver.com/topic/5526-issue-with-upgrade-to-50/
  9. Still no solution? Nobody can upgrade?
  10. I still have not tried to upgrade again. If you have made no changes to the 5.0 release, the same thing will happen, and I won't be able to upgrade. Were there any changes made to the software since I had this issue?
  11. I spent a day trying again to get a sub-domain working. I was able to get it working using the iFrame and Java tags, including the single page call Java tags, however, now matter what I did, I could not get the async tags working using the sub domain (which is my goal here). Is there any reason anyone can think of that would explain why all of the other tags are working for this, but not the async tags?
  12. PS - I did follow your upgrade process perfectly, copied over the new files, etc. I've been running this for over 10 years now, so know how to upgrade. I think you have a bug in your updater this time. I reverted my copy back to 4.2.1.
  13. I just upgraded to 5.0, ran the upgrade wizard, all seemed to go fine, but was expecting after it ran that when I went to my acp I would be prompted to update my database...I was not. When I go now to the Product Updates area I see: You are currently using Revive Adserver v5.0.0 (warning: database is stamped as v4.2.1) running on Apache, PHP 7.3.10 and MySQL 5.5.5-10.3.18-MariaDB. So was my database supposed to upgrade with 5.0? Now that it didn't happen, how can I upgrade it?
  14. Thank you for taking a shot at this, but it is configured correctly, as I am using it to serve images from another app that I run, which is my Invision Power Board forum.
  15. I've been trying to switch my installation of revive adserver (I'm v4.2.1 ) to serve ads to my site via a subdomain, instead of the main domain, but am having no luck. My main installation is at: www.mydomain.com/adserv and my current config has this for delivery: [webpath] admin="www.mydomain.com/adserv/www/admin" delivery="www.mydomain.com/adserv/www/delivery" deliverySSL="www.mydomain.com/adserv/www/delivery" images="www.mydomain.com/adserv/www/images" imagesSSL="www.mydomain.com/adserv/www/images" I use async tags, and I have updated the paths everywhere, including in cached and copies of config that are created, to be: [webpath] admin="www.mydomain.com/adserv/www/admin" delivery="ads.mydomain.com/adserv/www/delivery" deliverySSL="ads.mydomain.com/adserv/www/delivery" images="ads.mydomain.com/adserv/www/images" imagesSSL="ads.mydomain.com/adserv/www/images" I wanted to leave my admin access to be untouched, so I left that path the same. I change the async ad tag to the new location: <script async src="https://ads.mydomain.com/adserv/www/delivery/asyncjs.php" rel="preload" as="text/php"></script> and again, I used grep to find all instances of the paths, including: var/www.mydomain.com.conf.php var/cache/localhost_admin_container.php var/cache/mydomain.com_admin_container.php.meta var/cache/www.mydomain.com_admin_container.php var/cache/localhost_admin_container.php.meta var/cache/www.mydomain.com_admin_container.php.meta But I can't get the ads to display. Any ideas? Oh, and for a long time I can't get my debug error log working...it just puts in a strange character and is blank.
  16. I am still hoping for a solution to my insecure cookie issue. Revive is the only app on my domain that has this issue. All other apps have secure cookies.
  17. Is there a setting to make my cookies secure, as currently they are not secure: The following Cookies are not secure, you should add the Secure instruction in the Set-Cookie HTTP header: www.celiac.com/adserv/www/delivery/lg.php?banner[...]celiacs%2F&cb=f3814766b9 set-cookie: spcsrf=58357e9856fb6e2fa93de7f9cdfc37e6; Expires=Thu, 02-May-19 23:52:50 GMT; Path=/; HttpOnly; SameSite=Strict set-cookie: UTGv2=D-h4c33fdc6d399b6de8496e40aa580775b642; Expires=Fri, 01-May-20 21:52:50 GMT; Path=/ https://www.celiac.com/adserv/www/delivery/asyncjs.php set-cookie: spcsrf=6520eb79b20bf2806ff4d56baf063477; Expires=Thu, 02-May-19 23:52:48 GMT; Path=/; HttpOnly; SameSite=Strict set-cookie: UTGv2=D-h42c4ac14766f5128084800ade37ed3e0344; Expires=Fri, 01-May-20 21:52:48 GMT; Path=/
  18. I don't have my domain in the conf cookie setting...does this matter? If I add it should I include www? [openads] installed=1 requireSSL=1 sslPort=443 language=en [max] requireSSL=1 sslPort=443 [database] type=mysqli host=localhost port=3306 [cookie] permCookieSeconds=31536000 maxCookieSize=2048 domain= viewerIdDomain=
  19. I am still getting these warnings. The adserver's cookies are not secure https: The Secure directive By adding the Secure instruction in the Set-Cookie HTTP header, the server informs the browser that it is allowed to transmit the cookie over secure connection only. Read this blog post to learn more. Caution: Ensure that the HTTP to HTTPS redirect is activated on your website. Otherwise, the Secure cookie may not be sent on HTTP request. The following Cookies are not secure, you should add the Secure instruction in the Set-Cookie HTTP header: EXAMPLES: set-cookie: spcsrf=a7926253af246ee7f09f04062fcde42d; Expires=Thu, 25-Apr-19 19:03:00 GMT; Path=/; HttpOnly; SameSite=Strict set-cookie: UTGv2=D-h4f4bae1c99aeac150608db7df7d860a3547; Expires=Fri, 24-Apr-20 17:03:00 GMT; Path=/ set-cookie: OAID=a32d8dd64ecb4a95ef3092870b2080ea; expires=Fri, 24-Apr-2020 17:03:00 GMT; Max-Age=31536000; path=/ set-cookie: _OXLIA[2202]=pqj0p0-326; expires=Sat, 25-May-2019 17:03:00 GMT; Max-Age=2592000; path=/ Anyone know how to fix this? The answer probably lies in this file: lib/pear/HTTP/Request.php
  20. The only way to reproduce is to view the email that is sent out when a campaign is expiring. In my case the email from address is now malformed...not sure why, but it started after a recent upgrade. Again, all other system emails seem fine.
  21. I'm not sure how...every other email sent from my adserver system is normal, and follows the settings in the configuration file. The only email that has this issue is the impending ad expiration notice. I suspect there is a bug. PS - I am using sendmail and not php to send the emails.
  22. So the only further info I have is that it is possible that a 3rd party network that I was serving ads from served malware that somehow allowed them to inject those files. The strange thing was that they were indeed dated to the exact time and date as the rest of the installation files. I do always upgrade from Revive, and follow the link in admin to the upgrade file download. One think I wanted to point out, which could be a vulnerability, and I've pointed this out before, there are copies of the php config files in /var/cache which contain the password data. If you try to protect these files by chmoding them 644 you will get warning that your permissions are set incorrectly, and your ad stats may not be properly counted. The only way to stop the error, and the recommended permissions when running an installation where those directories are set to higher permissions, is to chmod them to 666. I am not sure this is secure enough. In any case, I did track the malware ads as coming from the 3rd party network, but I also discovered some injected hidden link to an Italian shopping site that was put into all pages of my site. Once I removed the two files mentioned that I found in the images directory the hidden links in my site ended. So I suspect that the malware ads that were served were somehow able to pull in the 2 files to the image directory. There needs to be an .htaccess file in that directory that stops php files from executing.
  23. Since I upgraded to v3.4.0 the system email "Impending campaign expiration" is now sending from my server name domain, and from "s". For example: From: "s" <s@scott.serverdomain.com> I've checked the config file and do not see anything that could cause this, and have no idea where the "s" is coming from. The email should be from "noreply@sitedomain.com"
  24. One of the Ad Networks that I used to serve ads from is called District M. Through them, unfortunately, I was also serving ads that contained horrible pop up malware...the type of ad pop up that you can't close or use the back button on--Usually claiming that you won a prize or that your device is infected and you simply need to download their "fix" to resolve it. I am wondering if it is possible that this type of malware could have also been the source of the 2 backdoor files? Could this malware also have utilized a Revive Adserver exploit to get the two files onto my site? I am surprised that more Revive folks have not responded here, as I do believe that there should be more concern about whatever exploit is being used to infect Revive installations. I've been using this software for over 10 years since it was called PHPAdsNew, and have never had such issues before.
  • Create New...