Subdomain a record

[lukecurtis]

Hey guys, so i’ve run cert bot for my domain, but i get the below error, it runs on a separate server and isn’t the A Record for the DNS listing, is this even possible to do?

My domain is: dev.bmoty.com

I ran this command: sudo certbot --nginx

It produced this output:
Failed authorization procedure. dev.bmoty.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Timeout

IMPORTANT NOTES:

• The following errors were reported by the server:

  Domain: dev.bmoty.com
  Type: connection
  Detail: Timeout
  The following errors were reported by the server:

  Domain: dev.bmoty.com
  Type: connection
  Detail: Timeout

  To fix these errors, please make sure that your domain name was
  entered correctly and the DNS A record(s) for that domain
  contain(s) the right IP address. Additionally, please check that
  your computer has a publicly routable IP address and that no
  firewalls are preventing the server from communicating with the
  client. If you’re using the webroot plugin, you should also verify
  that you are serving files from the webroot path you provided.

My web server is (include version): NGINX 1.10.0

The operating system my web server runs on is (include version): Ubuntu 16.04

My hosting provider, if applicable, is: N/A

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

[pfg]

It’s possible, but not with the nginx plugin you’re using. Demonstrating domain ownership involves a step like putting a file under a certain path on the domain (which Let’s Encrypt can then request) or creating a special DNS record. Certbot does this for you if you’re running it on the “real” server behind an IP address, but things are not quite as easy if you’re running the client on a different server.

Certbot has a “manual” plugin which allows you to perform these steps, well, manually - i.e., you could upload the verification files to the actual server behind the IP through whatever means and then request validation. You can find the documentation here. If you have programmatic access to the server or your DNS, you could even look into automating this steps using the --manual-auth-hook flag.