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.
It produced this output: You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry. etc
My web server is (include version): nginx 1.25
The operating system my web server runs on is (include version): windows 11
My hosting provider, if applicable, is: pagekite
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): 2.6.0
Hello Everyone, I have recently been able to solve the problems with http/https and now the site is https everywhere including the html files but somehow it is still saying not secure. Most probably it being self signed?