For many reasons, you may have a website, a blog, or an eCommerce website that uses an SSL certificate and shows the famous error message:
this website does not supply ownership information
So, what the warning message says is that you have a website that’s supposed to use SSL on all the resources and images. However, for some reasons, your web browser is not trusting the site. In this case, what could really cause the problem is mixed HTTPS and HTTP requests.
So, instead of securing all the requests, your website may still use an HTTP connection for some resources, like images, that are hosted by third-party sites or platforms.
To solve the mixed image HTTP and HTTPS issues, you need to first know the exact location of these images. So, on Windows, for example, you can visit your page URL, then, click on Ctrl+shift+K or its equivalent on Mac to open the web console.
Then, deactivate all the CSS, JavaScript, and any security filters you find. That will show you the exact image URL after you reload the page.
Now, you have clear messages and warnings about “mixed content” on your web page. We recommend copying all these URLs and seeing them in a new file.
Then, add these URLs directly to your browser to see if that fixes the problem. So, instead of HTTP, make them https, and that’s it.
That’s just to verify the images, and it’s not a solution. But to do that, you have two options:
1. Change your request URL to HTTPS
This is what will work in the majority of cases. Big brands and trusted websites use SSL to encrypt all their website connections. So, if you’re requesting HTTP from these domains, then you can just search for all the images or resource URLs in your site source code and update them with the new HTTP. That should fix the problem.
In WordPress, you can just use a plugin that searches for and replaces what you want. On Drupal, Joomla, PrestaShop, or other platforms, you can search for and replace extensions. If you can’t find a tool, you still have the option to manually add the code to your web page. Use NotePad for Windows or TextEdit for Mac.
2. Copy the external image and save them to your server
This is the solution that you need when the requested domains don’t support SSL. So, it makes no sense to add HTTPS to a domain name that uses HTTPS.
Instead of requesting the image from an external server, you can copy it and save it on your own website.
That way, you don’t only fix the “this website does not supply ownership information” error, but you’ll also speed up your web page loading time with fewer external requests.
If you’re using WordPress, there are many plugins that do the job for you. You can search for “Import External Images” and you’ll find them.
Then, install the plugin and follow the steps. The tool will look for images that your website uses but that are hosted on another domain, so, it will copy them and import them to the exact post.
That way, the plugin updates the URL of the external URL with the new ones from your website. Next time someone visits that page, the web browser will get all the contact information from your domain name and will not need extra locations. So, no more mixed HTTP and HTTPS requests.
For other platforms, follow the same steps, search for an extension that imports the external image, and update the attachment URLs.
If you have a few posts or pages with the problem, then it’s better to import the images manually and change the URL in posts, of course. That way, you’ll avoid installing a plugin, and you’ll be able to fix the SSL problem the way you want.
