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: digitalnomadsage.com
I ran this command: sudo certbot --nginx
It produced this output:
My web server is (include version): NGINX
The operating system my web server runs on is (include version): Ubuntu on VULTR 16.04(?)
My hosting provider, if applicable, is: VULTR
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): I think it’s certbot-auto – version.
My problem is unique because I migrated from Bluehost to VULTR…so my website retained the Bluehost SSL certificate somehow. I’m using Cloudflare so VULTR to cloudflare is insecure/nonexistent bluehost SSL. Cloudflare to internet is Cloudflare SSL.
Certbot says my DNS is not working but my site is up and running fine. So I know DNS works. It won’t accept www.digitalnomadsage.com Any ideas? Thanks!