I'm getting the following error when attempting to create a new certificate. Other certificates are created successfully, however, this specific one fails.
Unexpected error
+Response from server:
Code: InternalServerError
Content: Error
An error occurred while processing your request.
Reference #179.c8453c17.1488450658.2ec4c12e
This occurs during initiation of the challenges - i.e. before any authorization takes place. I'm trying to use HTTP authorization.
Does anyone know what could cause this?
EDIT: Seems to be failing for certain other domains as well. Some will work fine, others not.
I’m hitting the same issue at the moment, with different domains, and at different steps during the process. I’m using dehydrated with DNS-based challenge.
dehydrated doesn’t offer an option for a debug log. Here’s the output generated by one such failing run:
Processing linet.services with alternative names: www.linet.services
+ Signing domains...
+ Generating private key...
+ Generating signing request...
+ Requesting challenge for linet.services...
+ ERROR: An error occurred while sending post-request to https://acme-v01.api.letsencrypt.org/acme/new-authz (Status 500)
Details:
<HTML><HEAD><TITLE>Error</TITLE></HEAD><BODY>
An error occurred while processing your request.<p>
Reference #179.2e8f1402.1488455641.92b4b2
</BODY></HTML>
Sometimes the first “Requesting challenge for…” works, but subsequent ones for the same domain (different sub-domain, of course) don’t.
It happens both with our main domain that we’ve requested for already, and it happens with a brand-new domain (the linet.services shown above) that I’ve never requested LE certificates for.
We’re using the .Net library from ACMESharp. It’s highly integrated within our own internal APIs, so a debug log isn’t easilly produced - if ACMESharp even provides this (I’ll have to do some digging).
Is it possible to look up the Reference # within your systems to see what went wrong?
There may be someone around in a few hours that has access - I can’t (I’m just a moderator here )
From my perspective I know GetSSL best ( having written it ) - if you fancy doing a quick test for one domain using that ( it’s bash like dehydrated), it does have a full debug option though, which might help track down the issue.
Hello,
also getting lot's of Errors on Cert-Generation (some dozen Domains for now) - using our custom PHP Client:
2017-03-02 13:43:10 [error] HTTP Challenge for metzgerei-gasser.at is not available. Whole response: "Error</TITLE></HEAD>\nAn error occurred while processing your request.
@cpu - you mean more logs from different people or mor logs from me?
If there is anything I can do help speeding up locating the problem - just tell me what …
Andreas
Thinking about it more I think it would actually be most useful if yourself and @hognevevle, @mbunkus could provide some more information about where you’re generating these requests from geographically/source IP-wise.
Could you also run the following (Akamai always asks anyway):
One more thing to run if you would be so kind, futureweb (please un-obfuscate your XXXX when you actually run it, of course):
curl -vv -H “Pragma: akamai-x-get-cache-key, akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-get-true-cache-key, akamai-x-get-extracted-values, akamai-x-check-cacheable, akamai-x-get-request-id, akamai-x-serial-no, akamai-x-get-ssl-client-session-id, akamai-x-feo-trace” https://acme-v01.api.letsencrypt.org/acme/challenge/XXXXXXXX/XXXXXXXX
Thanks, futureweb. The team has opened an issue with Akamai (the CDN in front of the API) as the problem seems to be within their internal communication. We’ll post back when we’ve got news.
Thanks for the info!