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.
I ran this command: ```
sudo certbot --nginx certonly
It produced this output: failed to obtain ip address
My web server is (include version): ngnix version 1.14.0 (Ubuntu)
The operating system my web server runs on is (include version): Ubuntu 18.04.5 LTS
My hosting provider, if applicable, is: My machine
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): 0.31.0
In your DNS zone, it looks like weroc.co does not have an A (address) record nor is there a CNAME (canonical name) record from weroc.co to www.weroc.co (which does have an A record). I recommend that you add an A record for weroc.co that points to 199.48.95.138.
Also, your version of certbot is really outdated (0.31.0 vs 1.7.0)
Obviously I’m terrible at these records, just haven’t had to do one on my own. It looks like I have both A records, but not sure what to add to cname.
I tried changing the “www” to www.weroc.co but it reverts back to the “www”. If you could walk me through this in a bit more detail I’d appreciate it.
Obviously I’m terrible at these records, just haven’t had to do one on my own. It looks like I have both A records, but not sure what to add to cname.
I tried changing the “www” to www.weroc.co but it reverts back to the “www”. If you could walk me through this in a bit more detail I’d appreciate it.
Most people don’t know it, but actual hostnames have a full stop at the end for the “root” label. But in almost 99.999999999 % of all mentioned hostnames, the full stop at the end is left out, because it is rather superfluous. However, when working with DNS zonefiles, such as you’re doing now in your DNS configuration panel, these little tiny details play an important part! That’s because your zonefile sees “Host Records” without the trailing dot as a record relative to your DNS zone origin, which is weroc.co..
If you want to enter an absolute host record, you’ll need to add the trailing dot to it. Some (most?) DNS zone editor panels also accept a @ character as a shortcut for the “origin” of the DNS zone, in casu weroc.co..
So my advice to you is to try one (or both if the first one doesn’t work) of the following:
change the "Host Record “weroc.co” to “weroc.co.” (notice the tiny change);
change the "Host Record “weroc.co” to “@”.
You don't need to add any CNAME records. I was just pointing out that weroc.co was not mapped to an IP address.
That is to prevent you from making the mistake that @Osiris has explained. Unfortunately it does not prevent you from only putting weroc.co, which is where you fell. As @Osiris mentioned, it is good practice to simply enter @ when you only want to refer to the base domain name.
Don’t add any CNAME records. You only need the A record I originally mentioned. A CNAME record creates an alias from what’s on the left to what’s on the right. With the A record in place you don’t need the CNAME.
Well, for some reason not clear to me the weroc.co. still doesn't work, so now your CNAME www subdomain is pointing to a non-functional DNS record and is therefore also non-functional.
I'm also still seeing the weroc.co.weroc.co. hostname resolving perfectly.. Perhaps the Bluehost DNS configuration panel is quite non-standard..
Can you post a screenshot of your current DNS configuration panel?
