• When using SSL for our zone, and setting the “hostname replace” field to the SSL hostname provided by MaxCDN, the test button fails: “Error: No registered CNAMEs match mydomain-com-mydomain.netdna-ssl.com.”. This entry does not, and cannot, exist in the list of CNAME’s on MaxCDN. I believe this check needs to be modified so that it takes SSL into consideration.

    On another note, the test button generates PHP warnings, resulting in the XHR request to not fire properly in the JS callback:

    Warning:  Illegal string offset 'local_path' in wp-content/plugins/w3-total-cache/lib/W3/Cdn/Mirror/Netdna.php on line 102
    Warning:  Illegal string offset 'remote_path' in wp-content/plugins/w3-total-cache/lib/W3/Cdn/Mirror/Netdna.php on line 103

    https://www.ads-software.com/plugins/w3-total-cache/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Rob W

    (@robertark)

    I brought this up to MaxCDN, and they report:

    Sanja Obrenovic: It is actually visual bug on our end. As soon as it is fixed , most probably error from w3tc will disappear
    Sanja Obrenovic: however, it is already reported on our end and team is working on this

    Any news on this? Still getting the same error with W3TC.

    • This reply was modified 8 years, 2 months ago by wpseek.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘MaxCDN SSL CNAME Error – Invalid’ is closed to new replies.