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:willbode.com
I ran this command: autoupdate
It produced this output: https is there but chrome is saying it is an unsecured site
My web server is (include version):google cloud
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:google cloud
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):
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:willbode.com
I ran this command:auto renewal ssl cert
It produced this output:https still shows up but I get the default apache page or unsecure page warnings
My web server is (include version): google cloud
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is: google cloud
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): bitnami
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):