Jump to content

scott001

Approved members
  • Content Count

    70
  • Joined

  • Last visited

About scott001

  • Rank
    Member

Recent Profile Visitors

1,304 profile views
  1. 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/
  2. Still no solution? Nobody can upgrade?
  3. 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?
  4. 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?
  5. 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.
  6. 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?
  7. 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.
  8. 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.
  9. 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.
  10. 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=/
  11. 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=
  12. 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
  13. 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.
  14. 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.
×
×
  • Create New...