It seems like maybe this problem is on the LetsEncrypt server side, because there is demonstrably connectivity (the initial GET and HEAD requests work), and no error message is returned in the HTTP response, which I assume is not how the protocol is supposed to work. https://crt.sh/?q=www.greensfel…

Empty response from 'POST /acme/new-authz' with one particular cert

_az July 30, 2018, 10:24am 2

Does this happen every time? If so, could you tell me if this helps?

1 Like