Jump to content

Search the Community

Showing results for tags 'SSL'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Using and Managing Revive Adserver
    • Documentation
    • Using Revive Adserver
    • Managing Revive Adserver
    • Bugs
  • Advanced Topics
    • Performance, Scalability, and Reliability
    • For Developers
  • Revive Adserver Community
    • Revive Adserver Project News and Announcements
    • Feature Requests
    • Plugins
    • Requests for Consulting
    • Off Topic

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL

Found 8 results

  1. Hello, i am trying to setup Revive Adserver on an https-only website. But what code I use I always get the ads full or partly served over http, even if i change the http parts in the code to https. Even if the javascript loads over https the img src shows http. Revive Adserver itself is installed with ssl. How can I force Revive Adserver to serve ads only via https? Which version of the code is best used for https?
  2. 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
  3. Always used the Revive to manage my ads on my sites, always worked perfectly. Until, my site started to use ssl certificate, which caused damage to revive. Therefore I delete, reinstalled, manually and even at Softaculous by cpanel. But nothing worked, until I discovered that in a given file, enabling one to work ssl cool, everything was fine, but the plugins, such as placing ads for html among other functions were not well. I wonder what to do to revive the work comprehensively on the ssl protocol. Grateful!
  4. I've asked Chitika about this 3 times now without even an acknowledgement of my query. Before I give up on them, does anyone here know how to get their ads to appear over https? We are in the process of adding letsencrypt certs to all our sites. Needless to say, Adsense is fine and when I visit the site over http the Chitika ones re-appear - it just looks at the moment like https is beyond them. They don't even appear in the Revive banner preview when I use that over https.
  5. Hi all there. I have a problem on my web. I get an error on all browsers saying context was blocked because ads are serving mixed content. The insecure url is http://myserver.org/www/delivery/fl.js In the banners, the script has a correct url: https://myserver.org/www/delivery/spcjs.php?id=1but revive adserver serves really the insecure url. All the settings (requireSSL=1) seems to be correct. I've read the documentation and a lot of messages on forum and it seems to be a revive problem. How can I solve that problem in order to avoid error messages? Is it a ssl configuration error? Thanks a lot!
  6. We've noticed that the Doubleclick plugin supplied with current Revive (3.2.2. and earlier) does not support injecting the click tag for Doubleclick banners embedded via HTTPS. A fix would be to change plugins/3rdPartyServers/ox3rdPartyServers/doubleclick.class.php in lines 51, 52 to this: $search = array("/\[timestamp\]/i", "/(http:.*?;)(.*?)/i", "/(https:.*?;)(.*?)/i"); $replace = array("{random}", "$1click0={clickurl};$2", "$1click0={clickurl};$2");
  7. I am not sure if this is a bug issue or a strange anomaly that can't be fixed with this version. We just upgraded to the latest version of Revive... once completing the upgrade we noticed that the banners are now not shown on any web page that contains an https:// connection... even though we have verified the https:// pathway requirement to the invocation code snippet. If we change the code to only require an http:// connection and show the invocation code on an http:// page, it shows and records the impression as expected. Is anyone else experiencing this strange behavior after upgrading?
  8. I have my SSL working, and the admin section of Revive displays properly in the https: however, when trying to serve ads, or when viewing the banners in the admin interface, the banners are shown in the non-ssl protocol. I can't seem to find where to set the banner delivery to be from SSL? Thanks.
×
×
  • Create New...