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. crt.sh | 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:deborahsweetin.com
I ran this command:
sudo /opt/bitnami/bncert-tool
It produced this output:
bitnami@ip-172-26-4-228:~$ ls -l /opt/bitnami/letsencrypt/certificates/
total 16
-rw-r--r-- 1 bitnami root 2901 Oct 9 08:46 www.deborahsweetin.com.crt
-rw-r--r-- 1 bitnami root 1567 Oct 9 08:46 www.deborahsweetin.com.issuer.crt
-rw-r--r-- 1 bitnami root 243 Oct 9 08:46 www.deborahsweetin.com.json
-rw-r--r-- 1 bitnami root 227 Oct 9 08:46 www.deborahsweetin.com.key
bitnami@ip-172-26-4-228:~$ ^C
My web server is (include version):
The operating system my web server runs on is (include version):
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): no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Yeah, that first message is pretty clear that the cert is valid.
Use the browser's Developers Tools and view the debug console. But, this is almost certainly the Mixed Content problems shown by "Why No Padlock" link I provided earlier
