Category: SSL & HTTPS

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

If you have Really Simple SSL Pro installed, you might get the warning that your site contains a reference to an external resource that cannot load over SSL. If you see a domain looking like this one: “http://i0.wp.com”, you have a JetPack plugin, Photon, installed. Deactivate it, and this issue should be resolved. If this file is from a service you are using, it’s best to contact them and ask if the service can be provided over SSL as well, as