Home/ Questions/Q 7744875
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T09:52:24+00:00

I’m loading Disqus on a page loaded via HTTPS with the following code, as

  • 0

I’m loading Disqus on a page loaded via HTTPS with the following code, as suggested in this answer.

  <div id="disqus_thread"></div>
  <script type="text/javascript">
      var disqus_shortname = 'our-shortname';
      (function() {
          var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
          dsq.src = 'https://' + disqus_shortname + '.disqus.com/embed.js?https';
          (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
      })();
  </script>

Note that I’ve changed the request of embed.js to be https rather than http, and I’ve added ?https to the end of the request too, which I believe is supposed to force HTTPS.

The initial request goes via HTTPS as planned, but it makes a secondary request via HTTP, which Chrome is hating (I get the red cross over padlock icon).

From the Chrome console:

The page at https://our-website.com/blog-post-name ran insecure content from http://juggler.services.disqus.com/event.js?thread=635675380&forum=our-shortname...[long query string]

Is this the correct method to get Disqus to use ssl on all requests, or have I missed a step?

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This looks to be an issue within Disqus itself. We had Disqus working fine via SSL with the same approach in a couple of Drupal sites, but both recently had Disqus begin causing SSL warnings in both IE and Chrome as you’ve described.

    I did a bit of digging, and I see that the DISQUS.useSSL function that’s defined in embed.js and called in thread.js updates a few URLS (specifically [“disqus_url”,”realtime_url”,”uploads_url”]) in the Disqus json settings object by replacing http in their URL with https if https is found in the settings. The juggler_url doesn’t get the same treatment, and so it’s not updated to load via SSL. I’m not sure what juggler’s purpose is, but it appears that that URL (http://juggler.services.disqus.com/) won’t load via SSL in any case, so even if it’s url was changed to https, it still wouldn’t work.

    So perhaps Disqus has made a recent change, since we had this working previously? We’re taking this up with them, since this doesn’t appear to be a config issue on our end…

    UPDATE:

    Apaprently Disqus launched a new service that does not support SSL. This is what’s generating the extra scripts that get loaded insecurely, thus triggering the security warning. Disqus disabled this new service (which they didn’t tell us the name of) for our specific account, and now SSL is once again working as expected. So, the solution is to just ask them to make your account SSL compliant, and that should take care of it.

    • 0