Jump to content


Approved members
  • Content Count

  • Joined

  • Last visited

  1. Hello. We've got some issue with Revive Adserver after switching to SSL connection. Our Revive is installed on subdomain (https://ox.example.com). It's used on our main site (https://www.example.com). What have I done. 1) Generated SSL serteficates and make SSL-connection for main site and Revive. 2) Changed all the invocation codes in templates (we use Javascript Tags and Asyncronous JS tags). There, I've changed <noscript>...</noscript> part - changed http to https. 3) Changed all the settings in the config: requireSSL=1 sslPort=443 ssl=1 Setting deliverySSL and imagesSSL in [webpath] section. protocol=https 4) Clear the cache in /var/cache/. 5) Restarted nginx and apache. Now all the banners are showing on the main site (with https), admin interface is also works well. Issues: - In the Console folder of the Developer Tools there are such a warning for each banner zone: "Mixed Content: The page at 'https://www.example.com/' was loaded over HTTPS, but requested an insecure image 'http://ox.example.com/www/delivery/lg.php?bannerid=15&campaignid=1&zoneid=7&loc=https%3A%2F%2Fwww.example.com%2F&cb=g3d4d8ac72'. This content should also be served over HTTPS." - In the admin interface of banner zones, at the Invocation code tab I also see "http" in the links (Javascript Tag and iFrame Tag). <iframe id='a1878197' name='a1878197' src='http://ox.example.com/www/delivery/afr.php?zoneid=1&amp;cb=INSERT_RANDOM_NUMBER_HERE' frameborder='0' scrolling='no' width='1200' height='90'><a href='http://ox.example.com/www/delivery/ck.php?n=a1878197&amp;cb=INSERT_RANDOM_NUMBER_HERE' target='_blank'><img src='http://ox.example.com/www/delivery/avw.php?zoneid=1&amp;cb=INSERT_RANDOM_NUMBER_HERE&amp;n=a1878197' border='0' alt='' /></a></iframe> How could I fix them? Thanks for your attention. PS: I read this topic http://forum.revive-adserver.com/topic/322-serving-ads-over-https-fails/, but could not find the answer. Our Revive version - 3.2.2
  2. We had this problem with flash and gif banners. Html5 banners are not used on this domain in our case. I advice you to check the request headers to Revive and Console on problem pages. If there are security restricments - there should be more info on your problem. I think, that banners couldn't be just not showing without js- or request- errors.
  3. Hello everyone. We got the problem with site speed optimization. We have Revive installed on subdomain (ox.example.com). And when I start to check the site speed with PageSpeed Insights for the main domain example.com (https://developers.google.com/speed/pagespeed/insights/), it complaine on Revive banners - say that they are requesting without web-server deflate or gzipping. We use the Html5boilerplate .htaccess parts of config for defalation and gzip. And it works fine for the main domain (example.com). When I put this settings to different .htaccess files in Revive (on ox.example.com), I get this issue: the webinterface of Revive itself use deflate (I check it with browser console in headers), but html banners are requesting on the main domain (example.com) without it. Anyone have solved such a problem? I could send the PageSpeed Insights in direct massages, to show the problem.
  4. Did you check errors on Console or Network tabs of Chrome developer tools? We faced the same issue. After making ssl on one domain, banners stoped work because of security restriction: unsecure request to http were blocked. The fast and dirty decision: you need to make a local copy of your Revive installation on SSL domain. Example: you have a domain www.example.com with revive installation in www.example.com/revive and secure.example.com (with https) on other. You should make directory secure.example.com/revive and sync it with www.example.com/revive (with the help of rsync command, for example). Then, you need to sync your banner images folder, if it is not in www.example.com/revive. Then, you should change the name of config file and all the pionts with "www.example.com/revive" (ex., see webpath section). And the final part: you should change the domain part of revive's banner zones codes in your templates and change domains there. YOU SHOULDN'T CHANGE THE DATABASE CONFIG! The original and synced version of Revive use the same database. I know, that this is a dirty hack, but it worked in our case.
  5. Hello. You might know that new version of Google Chrome blocks flash-content. So we decided to convert them to html5. We choosed Google Swiffy to make this. But any attempts to do so failed. We tried different options in html5-settings of banners in Revive. And there were messages about the illegal tokens in console and no banner at all (the banners code were in the page source). So, are there any ability to use html5 banners converted in Google Swiffy? Maybe we should use another tool, not Swiffy, for this transformation? I've found only one topic here about this problem (seems that they had the same problem) but without any solution. http://forum.revive-adserver.com/topic/300-html5-swiffy-banner-in-iframe-how-to-make-responsive/
  6. Sorry for bumping such an old theme, but I think, that I've realised the reason of my problem. Today I've upgraded Revive to 3.0.5 and one time had the problem: new version had not seen the old one. The problem was with config file. It's name is like "www.example.com.conf.php" and I've started to upgrade in "http://example.com/revive_new". So, seemed that Adserver don't find the config file with "www".
  7. We have " - " in Impr. for some banners (gif or flash with gif) and, for example, 1600 clicks. Miracles
  8. But I started the upgrade when new database for 3.0.2 were filled with tables from old OpenX db. And now I can see all the banners and campaigns from OpenX in "upgraded" Revive admin. So, I suppose that db is upgraded now, but somehow Revive haven't found the OpenX installation.
  9. My install.log Why old OpenX are not detected? I tried to upgrade with old and new paths in [webpath] section of config. How does Revive server detect the old installations?
  10. Hello one more time. Finally, I've solved the task of upgrading of my adserver. But there were some strange behaviour: after running the upgrade wizard on step 2 of "Performing the Upgrade" section this article http://www.revive-adserver.com/support/upgrading/ I saw this message: But this is very strange, because I got 2.8.10 and I should see some upgrade steps like in article. My actions were: 1) Backups. 2) Unpack revive-adserver-3.0.2.tar.gz and rename it to "ox_new" (2.8.10 is in "ox" directory). 3) Make new db and user for it. 4) Fill new db with backup of old one (2.8.10). My tables got prefixes "ox_". 5) Copy config file from 2.8.10 to 3.0.2 Changed db information in it (user, pass, db name). In other attempt I've also changed the [webpath] section (admin, delivery, deliverySSL) because after running the upgrade I was redirected to old "ox" folder. 6) Run url with .../ox_new in the end and see the message I've write above. Without any mistakes or stranges. Is this behaviour weird or normal? In the admin panel of upgraded adserver I see all my zones and banners, but there are no new stat for about 3 hours after the upgrade? How I could detect if my new server is broken?
  11. Hello. I'm trying to upgrade adserver from Openx 2.8 to Revive 3.0.2 On this page http://www.revive-adserver.com/support/upgrading/ I've read: But when I've untared (or unzip) revive-adserver-3.0.2.zip or revive-adserver-3.0.2.tar.gz - there are no dummy conf file. In Openx it was var/default.conf.php I found similar file etc/dist.conf.php Can I use it? Are documentation wrong?
  • Create New...