Part of the web site is not secure after certificate

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
I ran this command: followed instructions to install
It produced this output:
My web server is (include version): apache2
The operating system my web server runs on is (include version): ubuntu
My hosting provider, if applicable, is: aws
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

Hi Friends, I have just followed the instructions and applied certificate. Immediately after that half of my web page became unavailable. especially pictures and css.

Can someone please help how to revert everything back or solve it?


Hi @senanito85,

You probably have a mixed-content problem due to hard-coded HTTP resource links on your site. You can diagnose this with a scanner like, or with your web browser’s developer tools.

1 Like

Yes, right at the top of your page, you have, for example

        <link href="" rel="stylesheet" type="text/css" media="all" />
        <link href='' rel='stylesheet' type='text/css'>
        <link href="" rel="stylesheet" type="text/css" />
         <!--- <script type="text/javascript" src=""></script> -->
        <script type="text/javascript" src=""></script>
        <link rel="stylesheet" type="text/css" href="" />
        <script type="text/javascript" src=""></script>
        <!-- FancyBox -->
        <!-- CSS -->
        <link rel="stylesheet" href="">
        <link rel="stylesheet" href="">
        <link rel="stylesheet" href="">
        <!-- FancyBox -->

All of these links should either use HTTPS or no protocol scheme at all, and they should use your domain name instead of your IP address.

For example, instead of

you could simply reference


That would cause the browser to load it from the same web server, using the same protocol (in this case, also via HTTPS).

Any of the first few results at

should also be helpful in understanding and fixing the problem.

1 Like

Thank You so much Schoen! This is really helpful!

Hi @senanito85

you have created an incomplete certificate.

You have two dns entries - non-www and www. But your certificate ( )
expires in 90 days - 1 entry

has only one domain name.

Result: Your non-www has the correct certificate (and mixed content), but your www version throws a warning:

Domainname Http-Status redirect Sec. G 301 0.360 A 200 0.577 H 200 2.123 I 200 1.886 N
Certificate error: RemoteCertificateNameMismatch

So create one certificate with two domain names and use that.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.