Did a health check. Getting a few errors. Understand none of them. Can’t fix it if I can’t get the question OR the answer. Don’t even know what category to place this under.
Check the site for mixed content - Does the website mix encrypted and non-encrypted content? ERROR FOUND
response_non_200
The site’s web server responded with a status code that isn’t 200 (OK).
Check if redirecting unencrypted HTTP traffic works - Does the website redirect unencrypted traffic from HTTP to HTTPS? ERROR FOUND
no_redirect_to_https
No, the website doesn’t redirect HTTP traffic to HTTP.
Check the HTTPS status - Does the site respond with a succesful HTTPS status? ERROR FOUND
fail
No, your request failed with a response status of 400 or above.
The error responses are too vague for a novice like me to get out of this mess. I’ve been here reading and pulling hair for 4 hours. Please help me.
Hi @thrivebiz, can you share the name of the domain?
Mixed content errors mean that your website is being loaded over HTTPS but some of the resources are being loaded over HTTP. To fix this you will need to edit your source code and change all resources to load over a relative path, or directly over HTTPS.
For example, if you load your images with a full URL:
<img src="http://example.com/image.jpg" />
You would want to change this to:
<img src="//example.com/image.jpg" />
By removing the http:, the browser will use whichever protocol the visitor is already using. An alternative option would be to enable the Automatic HTTPS Rewrites feature that can potentially fix these errors for you automatically. Do be aware that resources loaded by JavaScript or CSS will not be automatically rewritten and mixed content warnings will still appear.
Mixed content errors mean that your website is being loaded over HTTPS but some of the resources are being loaded over HTTP. To fix this you will need to edit your source code and change all resources to load over a relative path, or directly over HTTPS.
For example, if you load your images with a full URL:
<img src="http://example.com/image.jpg" />
You would want to change this to:
<img src="//example.com/image.jpg" />
By removing the http:, the browser will use whichever protocol the visitor is already using. An alternative option would be to enable the Automatic HTTPS Rewrites feature that can potentially fix these errors for you automatically. Do be aware that resources loaded by JavaScript or CSS will not be automatically rewritten and mixed content warnings will still appear.
| 
thrivebiz: