3 Replies Latest reply on Oct 3, 2016 5:46 AM by lindac8375

    All kinds of errors since adding my SSL Certificate: https

    Integraoligist

      In Chrome i'm in the Dev options Console and I'm getting all of these issues on my index page since adding SSL to my site and changing from http to https. This site was created completely with Muse and no coding by me... I know the majority of these are the fonts, which are from Adobe... so I'm not sure shy the font families are having issues and staying on http instead of moving to https.

      Are these big issues? Or is it fine to just leave these problems alone?

      Here is a list of the issues right from the index page:

      -----------------------------

      Mixed Content: The page at 'https://www.DOMAIN.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Bitter'. This request has been blocked; the content must be served over HTTPS.

      (index):258 Mixed Content: The page at 'https://www.DOMAIN.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Bitter'. This request has been blocked; the content must be served over HTTPS.

      (index):610 Mixed Content: The page at 'https://www.DOMAIN.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Bitter'. This request has been blocked; the content must be served over HTTPS.

      (index):1312 Mixed Content: The page at 'https://www.DOMAIN.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Bitter'. This request has been blocked; the content must be served over HTTPS.

      (index):1380 Mixed Content: The page at 'https://www.DOMAIN.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family={param_titleboxfont}'. This request has been blocked; the content must be served over HTTPS.

      (index):1569 Mixed Content: The page at 'https://www.DOMAIN.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=ABeeZee'. This request has been blocked; the content must be served over HTTPS.

      (index):1915 Mixed Content: The page at 'https://www.DOMAIN.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Bitter'. This request has been blocked; the content must be served over HTTPS.

      (index):2076 Mixed Content: The page at 'https://www.DOMAIN.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=PT%20Sans'. This request has been blocked; the content must be served over HTTPS.

      https://www.DOMAIN.com/Add%20File Failed to load resource: the server responded with a status of 404 (Not Found)

      (index):2955 Mixed Content: The page at 'https://www.DOMAIN.com/' was loaded over a secure connection, but contains a form which targets an insecure endpoint 'http://DOMAIN.us14.list-manage.com/subscribe/post?u=2a3888e564369c662e2037610&id=ff0ed2dc1 7&c=?'. This endpoint should be made available over a secure connection.

      https://www.DOMAIN.com/Add%20File Failed to load resource: the server responded with a status of 404 (Not Found)

      jquery.min.js:4 Mixed Content: The page at 'https://www.DOMAIN.com/' was loaded over a secure connection, but contains a form which targets an insecure endpoint 'http://DOMAIN.us14.list-manage.com/subscribe/post-json?u=2a3888e564369c662e2037610&id=ff0e d2dc17&c=?'. This endpoint should be made available over a secure connection.

      https://www.DOMAIN.com/Add%20File Failed to load resource: the server responded with a status of 404 (Not Found)

      https://www.DOMAIN.com/null Failed to load resource: the server responded with a status of 404 (Not Found)

       

       

      BTW I changed over to SSL because we're using MuseXpress with WooCommerce and will be selling directly on the site shortly. And no I dont want to put the actual domain on this post as I do not want this post to pop up in a search engine with looking for said domain.

      Thanks all for the help!

        • 1. Re: All kinds of errors since adding my SSL Certificate: https
          lindac8375 Level 2

          I am pretty sure this error has to do with google fonts. I just decided to not use google fonts to avoid the whole issue with https and our ecommerce site.

           

          Anyhow, fwiw, I found this fix and maybe it will work for you, but the problem is you have to make this change every time you re-upload the html.

           

          The fix for this is very simple and will work under all the common browsers.  This has been tested on IE9, Firefox 13, Safari and Chrome.

          locate this line on your HTML page (or template):

          <link href='http://fonts.googleapis.com/css?family=Dosis:400,700' rel='stylesheet' type='text/css'>

          and change it to this:

          <link href='//fonts.googleapis.com/css?family=Dosis:400,700' rel='stylesheet' type='text/css'>

          This simple change will make your browser call the Google Font page in the applicable mode (HTTP vs HTTPS).

          1 person found this helpful
          • 2. Re: All kinds of errors since adding my SSL Certificate: https
            Integraoligist Level 1

            Other then just popping up as errors when in Dev. mode... do these errors actually cause any issues?

            • 3. Re: All kinds of errors since adding my SSL Certificate: https
              lindac8375 Level 2

              Well, not technically site issues per se (as in my site worked fine as far as no visual errors).

               

              However, users were getting browser errors that my site be may unsafe and the little green https lock in the corner was not showing up.

               

              This was not good for an ecommerce site. So it's not Muse, it's how browsers see anything in the html that points to anything http vs. https.

               

              Also, in my case, I had used some images uploaded to an image hosting site that was http and not https. So several of my images had an http path. Had to find an image host that was https.