Category: Mixed Content

If you have Really Simple Security Pro installed, you might get the warning that some posts contain a reference to an external resource that cannot load over SSL. This mostly concerns hot-linked images. An example: if a post contains an image that is actually located on another domain: <img src=”http://www.not-your-domain.com/image.jpg”> If that domain does not have an SSL certificate, this image won’t load on SSL. This might also happen with javascript files (.js), or stylesheets (.css) Solution: click the “fix” button

If you have Really Simple Security Pro installed, you might get the warning that your site contains references to JS or CSS files on other domains which in turn contain non-secure links. For example, your site might include a .js file from a service you run on your site. If this JavaScript file, in turn, includes another file over http://, this will result in mixed content errors. To fix this, you can try to ask the file owner on that

If you have Really Simple Security Pro installed, you might get the warning that your site contains JS or CSS files which in turn contain non-secure (http) links. For example, your site probably has a stylesheet like style.css included. If this stylesheet uses a background image, that might look like this: body { background-image: url(“http://​www.domain.com/paper.gif”); } This http URL may cause mixed content issues because Really Simple Security can’t fix this dynamically, it is stored in a CSS file. You

If you have Really Simple Security Pro installed, you might get the warning that your site contains a reference to an external resource that cannot load over SSL. If this file is from a third-party service you are using, it’s best to contact the vendor and request if the service can be provided over SSL as well. If that is not possible, you can try the steps below. Please take care not to violate any intellectual property rights: always ask