<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-text-html" lang="x-western">
<p> </p>
<blockquote type="cite">
<div dir="ltr">Could you write step by step how you reach the
goal?<br>
</div>
<br>
2018-02-22 15:55 GMT+01:00 Gabriel Kaufmann <span dir="ltr"><<a
href="mailto:mailings@typoworx.com" target="_blank">mailings@typoworx.com</a>></span>:<br>
<p>I've tried to create an certbot SAN-Cert with multiple
domain-names and this worked like a charm using one cert for
all! Thanks!</p>
</blockquote>
<p>Shure :)</p>
<p>At first you should have a working Certbot of course. Setup for
this depends on your Server-Setup of course. Certbot requires
access due to "standalone-http(s)" mode of certbot or access
through apache/nginx/haproxy (works as well if setup correctly).
I'm using each of these variants.</p>
<p>Assuming you have a working setup and certbot-services can
access your certbot service (running as http/s while certbot is
running) the SAN setup is quit easy:</p>
<p> </p>
<blockquote type="cite">$> certbot -d domain1.com -d
domain2.com -d domain3.com</blockquote>
<p>if running in non-standalone mode (running apache/nginx) you
can tell Certbot where the auth-tokens are stored to for
external domain-approval:<br>
</p>
<blockquote type="cite">-w /var/www/my-web-root</blockquote>
With the syntax given above the SAN-Cert for all given domains is
stored in /etc/letsencrypt/live/domain1/<br>
<p>standalone-mode and web-root also can be configured in
/etc/letsencrypt/cli.ini<br>
(<a class="moz-txt-link-freetext"
href="https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465">https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465</a>)<br>
<br>
</p>
<pre class="moz-signature" cols="72">Best regards
Gabriel Kaufmann</pre>
</div>
</body>
</html>