• Resolved shanthini

    (@shanthini)


    Hi,

    We have configured CDN using total cache plugin. In developer console we are getting error as below. We are using chrome

    Mixed Content: The page at 'https://www.efacilityvms.com/' was loaded over HTTPS, but requested an insecure font 'http://cdnefacilityvmscom.r.worldssl.net/wp-content/themes/sofbox/assets/fonts/ionicons.ttf?v=2.0.0'. This request has been blocked; the content must be served over HTTPS.
    
    Even though we use the absolute url as 'https://cdnefacilityvmscom.r.worldssl.net/wp-content/themes/sofbox/assets/fonts/ionicons.eot?v=2.0.0' we are getting this error.

    Is this issue related to theme’s files. Could you please suggest.

    Thanks

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @shanthini

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    Can you please share which CDN provider you are using and what is the CDN Type: selected in Performance>General settings?
    Thanks!

    Thread Starter shanthini

    (@shanthini)

    Hi,

    Please find below the details that we setup in admin side

    SSL support: auto
    CDN url: cdnefacilityvmscom.r.worldssl.net

    We purchased CDN url from accuweb hosting. Link: https://www.accuwebhosting.com/

    But except the above reported url this is working as expected for rest of the URLs

    Thank you

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @shanthini

    Thank you for the information.
    It appears that some settings on your CDN are not correct since the files are served from the origin over HTTPS.
    W3 Total Cache only uploads the file to CDN and helps to integrate the CDN via W3 Total Cache and in your case as a Generic mirror.
    Please make sure to follow these instructions and make sure to check your provider CDN settings.
    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Incorrect CDN url’ is closed to new replies.