golang-nuts › acme, letsencrypt and different HTTPS ports

<p>I have an EC2 vm where I want to run two go https servers on different ports.</p> <p>I am using letsencrypt for the certificates and the code is like:</p> <pre><code>server1.go: log.Fatal(http.Serve(autocert.NewListener(&#34;api1.example.com&#34;), http.DefaultServeMux)) server2.go: log.Fatal(http.Serve(autocert.NewListener(&#34;api2.example.com&#34;), http.DefaultServeMux)) </code></pre> <p>I want api1 to listen on port 443 and want api2 to listed on port 8080. Is it possible to achieve this via autocert at all ? If not, are there any other hacks to get multiple ports exposed from the same machine using letsencrypt ? I am deploying server1.go manually (via a systemd script) and server2 via a docker container, if it matters.</p> <p>Any help ? Thanks.</p> <hr/>**评论：**<br/><br/>i_regret_most_of_it: <pre><p>Are you sure you want them to be on different ports?</p> <p>You can just host both on :443:</p> <pre><code>autocert.NewListener(&#34;api1.example.com&#34;, &#34;api2.example.com&#34;) </code></pre> <p>and deal with the different hostnames in your handlers.</p> <p>But the post on go-nuts is right - autocert won&#39;t help you if need to work outside of the limitations of the http-01 challenge.</p></pre>psankar: <pre><p>Those two different processes with different release timelines. I just simplified for brevity. Thanks :)</p></pre>