scott001 Posted June 12, 2020 Report Share Posted June 12, 2020 I brought this up once before, and I still cannot solve this issue. I would like to change the setting for "Delivery Engine URL (SSL)" to a subdomain, for example ads.mydomain.com. But when I do this the ads do not show. It only works using www.mydomain.com. This is strange because I can change the "Image Store URL (SSL)" setting to ads.mydomain.com, and it works fine. I can also use this path in my site's template, and it works fine: <script async src="https://ads.mydomain.com/adserv/www/delivery/asyncjs.php"></script> There is nothing in my .htaccess or site security policy that won't allow this to work. Any ideas? Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted June 14, 2020 Report Share Posted June 14, 2020 Hi @scott001, So, when you change the URL in the configuration file, and it "doesn't work", what do you mean? What do you see? What does stepping through the troubleshooting guide turn up? Quote Link to comment Share on other sites More sharing options...
scott001 Posted June 16, 2020 Author Report Share Posted June 16, 2020 (edited) When I change the Delivery Engine URL (SSL) to the subdomain ads.mydomain.com the banners stop displaying. I can only get this setting working when it is www.mydomain.com. Normally this would make me think that the subdomain isn't set up properly, but it is, as I use it to server other content on the site (for example Google Analytics). I also mentioned that I am using the subdomain to server the asyncjs.php script in the site template, and I am using it as the Image Store URL (SSL) setting. So, the subdomain is set up, working, and there is nothing in my .htaccess, site security policy, or anywhere else on the server side that seems to be causing this issue. I will take another look at the troubleshooting guide, but I did look at it last time I brought this issue up, and saw nothing that would explain this. Edited June 16, 2020 by scott001 Quote Link to comment Share on other sites More sharing options...
scott001 Posted June 19, 2020 Author Report Share Posted June 19, 2020 Perhaps I am misunderstanding what Delivery Engine URL means. Is this the web site where the ads are served? It isn't clear, but knowing this might be helpful? Quote Link to comment Share on other sites More sharing options...
scott001 Posted June 23, 2020 Author Report Share Posted June 23, 2020 So I can get the iFrame tags working as described above, but not the async tags. Do you know why the async would not work for a subdomain, while the iFrame tag would? Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted June 23, 2020 Report Share Posted June 23, 2020 On 6/19/2020 at 9:49 AM, scott001 said: Perhaps I am misunderstanding what Delivery Engine URL means. Is this the web site where the ads are served? No - it's the URL from which Revive Adserver will deliver the ads. If you change this, you need to have your web server configured to allow the Revive Adserver delivery directory to operate from that URL. Quote Link to comment Share on other sites More sharing options...
scott001 Posted June 23, 2020 Author Report Share Posted June 23, 2020 So, the important test I did was that it works fine using Iframe tags, but will not work at all using the async tags. Do you know why that would be? Again, I've tried everything, and to me it seems to be some sort of coding issue with the async tags. Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted June 24, 2020 Report Share Posted June 24, 2020 No, I don't know why it wouldn't work based on the information above. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.