WordPress HTTPS (SSL)
[WordPress HTTPS] PIWIK analytics code causes Opera to fail loading SSL page (2 posts)

  1. webass
    Posted 2 years ago #

    I got WordPress HTTPS installed for securing the admin panel and one page on the front of the website named mydomain.com.
    In chrome I have got no issues at all, and in IE 9 my client also said, everything would be fine.

    But now I tested on Opera.
    I go to the front of the page, and then it says UNSECURE. The report Opera gives is about the PIWIK site (piw.myotherdomain.com), that is running PIWIK and the PIWIK code from there, that I added to the head of mydomain.com, to track this site.
    Opera says piw.myPIWIKdomain.com would not fit the domain in certificate of mydomain.com.

    Then I went into WordPress HTTPS and tried with URL mapping the following:
    http://myPIWIKdomain.com -> https://myPIWIKdomain.com

    THEN the warning disappeared.

    But Opera still sends the link https://www.mydomain.com/secured-page back to http://www.mydomain.com/secured-page and when I click in the address bar icon, it says site is unsecure.

    The next thing I tried with URL mapping is:
    http://myPIWIKdomain.com -> https://www.mydomain.com/secured-page but this also doesnt help....

    Is there really a problem with the PIWIK code not being on a secured domain, because the code that is called from the unsecured URL for tracking on the secured mydomain.com???

    Or is simply Opera too stupid to understand a single secured page on a site where other pages are not secured??

    I am a bit puzzled, especially because on Chrome I got no problem at all.
    On IE 10 it says that there are missing certificates on the site, but it at least shows the https:// in the address bar...

    What about this all?

    I am using a free certificate by StartSSL...
    Thanks in advance fro any help.



  2. webass
    Posted 2 years ago #

    Although this is a quick dirty solution I would now go on and move the PIWIK installation to a sub directory of mydomain.com, away from myPIWIKdomain.com
    like mydomain.com/piwik
    because StartSSL certificates cover anything beneath the domain (but not sub-domains, for which a wildcard-cert would be needed)
    I think, through this action, I would handle the problem in EVERY case, cause then I could have PIWIK run under SSL also, with the same certificate.

    But ... that wouldnt explain the (IMHO) curious behaviour

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • WordPress HTTPS (SSL)
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic