# Error creating new authz :: Issuance for IP addresses not supported **URL:** \ **Category:** Help\ **Created:** [August 28, 2019, 2:40pm UTC](https://community.letsencrypt.org/t/error-creating-new-authz-issuance-for-ip-addresses-not-supported/100855 "2019-08-28T14:40:49Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![tskale](https://avatars.discourse-cdn.com/v4/letter/t/74df32/32.png) [@tskale](https://community.letsencrypt.org/u/tskale)\ **Post date:** [August 28, 2019, 2:40pm UTC](https://community.letsencrypt.org/t/error-creating-new-authz-issuance-for-ip-addresses-not-supported/100855/1 "2019-08-28T14:40:49Z")
My domain is: www.openmep.biz I ran this command: Using [golang.org/x/crypto/acme/autocert](http://golang.org/x/crypto/acme/autocert) library in Go server to create certificate. The servers runs as expected using https but print the following message: It produced this output: 2019/08/28 14:26:48 http: TLS handshake error from 107.178.237.16:53543: 400 urn:acme:error:malformed: Error creating new authz :: Issuance for IP addresses not supported My web server is (include version): The Go web server I have written. The operating system my web server runs on is (include version): Ubuntu 18.04 My hosting provider, if applicable, is: Google Cloud Platform 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): Bo The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you’re using Certbot): None ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [August 28, 2019, 3:18pm UTC](https://community.letsencrypt.org/t/error-creating-new-authz-issuance-for-ip-addresses-not-supported/100855/2 "2019-08-28T15:18:35Z")
Hi @tskale > [@tskale](#): > > My domain is: www.openmep.biz what domain names did you use in your certificate creation command? Your error > [@tskale](#): > > urn:acme:error:malformed: Error creating new authz :: Issuance for IP addresses not supported says: You have tried to create a certificate with an ip address. Letsencrypt doesn't support such certificates. ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [August 28, 2019, 3:53pm UTC](https://community.letsencrypt.org/t/error-creating-new-authz-issuance-for-ip-addresses-not-supported/100855/3 "2019-08-28T15:53:34Z")
> [@JuergenAuer](#): > > what domain names did you use in your certificate creation command? I suspect (but may be wrong) that @tskale has `autocert` configured to try and issue certificates automatically in-line with requests that arrive when no certificate is available to satisfy the hostname provided by the client's TLS SNI value. If that's the case then I think you need to filter out requests where the SNI is an IP address and not a domain name. As @JuergenAuer mentioned Let's Encrypt doesn't issue certificates for anything other than domain name identifiers presently. ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [August 28, 2019, 3:59pm UTC](https://community.letsencrypt.org/t/error-creating-new-authz-issuance-for-ip-addresses-not-supported/100855/4 "2019-08-28T15:59:08Z")
> [@cpu](#): > > I suspect (but may be wrong) that @tskale has `autocert` configured to try and issue certificates automatically in-line with requests that arrive when no certificate is available to satisfy the hostname in provided by the client’s TLS SNI value. Ah, thanks, good to know. If there is such a feature -\> that may be the problem. ---
**Author:** ![tskale](https://avatars.discourse-cdn.com/v4/letter/t/74df32/32.png) [@tskale](https://community.letsencrypt.org/u/tskale)\ **Post date:** [August 28, 2019, 6:35pm UTC](https://community.letsencrypt.org/t/error-creating-new-authz-issuance-for-ip-addresses-not-supported/100855/5 "2019-08-28T18:35:32Z")
Thanks cpu. It was `autocert` configuration problem. It’s working ok now. ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [August 28, 2019, 7:41pm UTC](https://community.letsencrypt.org/t/error-creating-new-authz-issuance-for-ip-addresses-not-supported/100855/6 "2019-08-28T19:41:49Z")
Great, glad to hear it. Thanks for reporting back 👍 ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [September 27, 2019, 7:41pm UTC](https://community.letsencrypt.org/t/error-creating-new-authz-issuance-for-ip-addresses-not-supported/100855/7 "2019-09-27T19:41:51Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.