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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: www.cookinggoals.com
I ran this command: apt install python-certbot-nginx
(https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-18-04)
It produced this output:Not Secure
My web server is (include version): Ubuntu 18.04.3 (LTS) x64 - Nginx
The operating system my web server runs on is (include version): Ubuntu
My hosting provider, if applicable, is:Digitalocean
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):I have root access
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.31.0
Hi @tolgacan
that's only a mixed content problem - see https://check-your-website.server-daten.de/?q=cookinggoals.com#html-content
Your certificate is correct:
CN=cookinggoals.com
05.06.2020
03.09.2020
expires in 89 days cookinggoals.com, www.cookinggoals.com - 2 entries
but you have wrong links:
http://www.cookinggoals.com/wp-content/uploads/2020/06/logo27290.png
Change these to https.
Thank you sir
But this is an image. We don’t choose http or https when uploading an image. It seems weird.I have uploaded my logo before I installed ssl.
That’s more a Wordpress problem if you switch from http to https.
It’s not a certificate problem.
Hi again Juergen
I have solved homepage problem. It shows secure connection.
But have a look at my post result.
https://www.whynopadlock.com/results/b17346c0-24b6-4ce7-a842-08840c92dd7c
Recheck your domain - with both tools - check-your-website and whynopadlock.
There is no automated recheck.