On Sunday, 11 June 2017 03:57:38 UTC+2, bradfitz wrote:
>
> Perhaps the autocert package should special case localhost and just serve
> a self-signed cert in that case. That'd be useful for testing and
> consistency.
>
> I filed https://github.com/golang/go/issues/20640 to think about that.
>
> M
Perhaps the autocert package should special case localhost and just serve a
self-signed cert in that case. That'd be useful for testing and consistency.
I filed https://github.com/golang/go/issues/20640 to think about that.
On Tue, Jun 6, 2017 at 10:22 AM, 'Axel Wagner' via golang-nuts <
golang-
No worries :) Glad to help increase security on the web by adding another
Site with good TLS :)
On Fri, Jun 9, 2017 at 10:06 AM, Sankar P
wrote:
> Thank you so much Axel Wagner. I was able to get everything working, once
> I added the A record. Everything worked so magically together correctly :
Thank you so much Axel Wagner. I was able to get everything working, once I
added the A record. Everything worked so magically together correctly :)
2017-06-07 23:33 GMT+05:30 Axel Wagner :
> On Wed, Jun 7, 2017 at 7:22 PM, Sankar P
> wrote:
>
>>
>> 2017-06-06 22:52 GMT+05:30 Axel Wagner :
>>
>>
On Wed, Jun 7, 2017 at 7:22 PM, Sankar P wrote:
>
> 2017-06-06 22:52 GMT+05:30 Axel Wagner :
>
>> tl;dr: You need a) a publicly routed IP address (either IPv4 or IPv6 is
>> fine), b) a publicly resolvable domain that points to that IP address and
>> c) actually point your client (browser) to that
On Tuesday, June 6, 2017 at 6:22:28 PM UTC+1, Axel Wagner wrote:
>
> tl;dr: You need a) a publicly routed IP address (either IPv4 or IPv6 is
> fine), b) a publicly resolvable domain that points to that IP address and
> c) actually point your client (browser) to that domain.
>
>
>
I've not done
2017-06-06 22:52 GMT+05:30 Axel Wagner :
> tl;dr: You need a) a publicly routed IP address (either IPv4 or IPv6 is
> fine), b) a publicly resolvable domain that points to that IP address and
> c) actually point your client (browser) to that domain.
a) I created an AWS VM with a public-ip address
What it boils down to is that your server tries to get a certificate for
whatever name is in the URL. But Let’s Encrypt won’t issue a certificate for
localhost, for various reasons—not the least of which is that a certificate for
localhost makes as much sense as having a photo ID that says “Me”
tl;dr: You need a) a publicly routed IP address (either IPv4 or IPv6 is
fine), b) a publicly resolvable domain that points to that IP address and
c) actually point your client (browser) to that domain.
Long explanation:
The HTTP client will use SNI to tell the server the domain it needs a cert
fo
