Correct zName not found for TLS SNI challenge


When I try to renew my certificate I get the following error:

Error: urn:acme:error:malformed :: The request message was malformed :: Error creating new authz :: Name is blacklisted


Are you happy to say what your domain name is ?

I know there were some modification of the blacklisted names, and a few got caught up by accident.


Yeah this is always an problem here that people do not like to tell the domain.Even if it is not an blacklist problem.

#4 is the domain on the certificate that expires next sunday


@jsha can you tell something about this name ?
This is neigther banking related nor software.


This error looks kinda bogus. I’m checking the logs, and can’t find the actual blacklist failure for your domain.

Can you post the exact command you used and some of the log output?


Command: ./letsencrypt-auto renew

log output:

2016-02-29 17:38:38,780:DEBUG:acme.client:Storing nonce: 's\x85\x19@\xd8\xf4\x9c\x8bn%\xce@kJ.\t\x8bf\xc7\xa7\xee\xf5\xe1r1\xb5; \xc2\x95\xcb)'
2016-02-29 17:38:38,780:DEBUG:acme.client:Received response <Response [400]> (headers: {‘Content-Length’: ‘107’, ‘Expires’: ‘Mon, 29 Feb 2016 17:38:44 GMT’, ‘Server’: ‘nginx’, ‘Connection’: ‘close’, ‘Pragma’: ‘no-cache’, ‘Cache-Control’: ‘max-age=0, no-cache, no-store’, ‘Date’: ‘Mon, 29 Feb 2016 17:38:44 GMT’, ‘Content-Type’: ‘application/problem+json’, ‘Replay-Nonce’: ‘c4UZQNj0nItuJc5Aa0ouCYtmx6fu9eFyMbU7IMKVyyk’}): '{“type”:“urn:acme:error:malformed”,“detail”:“Error creating new authz :: Name is blacklisted”,“status”:400}'
2016-02-29 17:38:38,781:DEBUG:letsencrypt.cli:Exiting abnormally:
Traceback (most recent call last):
File “/root/.local/share/letsencrypt/bin/letsencrypt”, line 11, in
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/letsencrypt/”, line 1987, in main
return config.func(config, plugins)
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/letsencrypt/”, line 663, in run
lineage, action = _auth_from_domains(le_client, config, domains)
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/letsencrypt/”, line 458, in _auth_from_domains
new_certr, new_chain, new_key, _ = le_client.obtain_certificate(domains)
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/letsencrypt/”, line 252, in obtain_certificate
return self.obtain_certificate_from_csr(domains, csr) + (key, csr)
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/letsencrypt/”, line 225, in obtain_certificate_from_csr
authzr = self.auth_handler.get_authorizations(domains)
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/letsencrypt/”, line 74, in get_authorizations
domain, self.account.regr.new_authzr_uri)
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/”, line 216, in request_domain_challenges
typ=messages.IDENTIFIER_FQDN, value=domain), new_authz_uri)
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/”, line 196, in request_challenges
response =, new_authz)
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/”, line 644, in post
return self._check_response(response, content_type=content_type)
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/”, line 560, in _check_response
raise messages.Error.from_json(jobj)
Error: urn:acme:error:malformed :: The request message was malformed :: Error creating new authz :: Name is blacklisted


regarding the name it is my personal “Owncloud” server on AWS


@Hackerace Hi, you log contain the stacktrace but more interesting would be the query that cause the error.
The log only contain the part after the error. Good would be the last request before
:“Error creating new authz :: Name is blacklisted”,“status”:400}'
Maybe you had bsome other domains for testing that are now rejected.


Wait, is it possible that owncloud is on the list?


Just checked - no, it isn’t.


you wait.
it DOESNT log the domain names (especially when seeing a blacklist error)?

but owncloud cant be on the list because renew was used, aka renew a cert that already exists and I cant believe that owncloud can have a cert in the first place.


Okay, so I worked with @jsha to check the logs.

What actually happened was you tried to issue a certificate for That’s an Amazon domain, so it’s on the high-risk list.


but wait. is on the PSL, (I literally just checked) so there shouldnt be THAT much risk, since amazon officially acknowledges this as public domain.


Maybe we should have a further discussion about this particular case (maybe including folks from AWS), but being on the PSL doesn’t override the blacklist (even if it would have overriden the rate limit).


I think we should have an discussion at least WHAT is on the blacklist even if not all names mentioned.
I can remember you said in the past that it only contain about 200 domains that are relevant for banking.


and the domain says and not and I am certain that IE and firefox (dunno about others) at least highlight the root domain making it more obvious that it is not directly amazon.


You really want someone to be able to grab a cert for every * just by starting free-tier instances until they’ve cycled through all the available IP addresses? Remember it’s on the PSL so the rate limit wouldn’t stop them.


sothose names are IP based?
I thought every machine gets a URL based on the ID of the instance.


They are IP based, and they get reused as instances are stopped and new ones started up.