2017-06-06 22:52 GMT+05:30 Axel Wagner <axel.wagner...@googlemail.com>:
> 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. I verified that the machine is accesible by ssh-ing into it. b) In my domain name provider (Gandi, if it matters), I added a web-forwarding rule to forward all incoming requests to http://api.mydomain.com to https://public-ip c) I ran a go server with that magical line: log.Fatal(http.Serve(autocert. NewListener("mydomain.com <http://example.com/>"), handler)) in that public-ip Now if I try to access http://api.mydomain.com then I am not able to reach this server, nor do I get any mail from letsencrypt about certificates. What should I be doing extra ? Thank you everyone for the responses. -- Sankar P http://psankar.blogspot.com -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
