Failed to submit

[plitter]

I got this when I got to the step to submit the certificate. PS <Path>> Submit-ACMECertificate Submit-ACMECertificate : The remote name could not be resolved: 'acme-v01.api.letsencrypt.org' At line:1 char:1

• Submit-ACMECertificate

•   + CategoryInfo          : NotSpecified: (:) [Submit-ACMECertificate], WebException
    + FullyQualifiedErrorId : System.Net.WebException,ACMESharp.POSH.SubmitCertificate
  
  

And after when I try to check the certificate I get: PS <Path>> Update-ACMECertificate Update-ACMECertificate : Certificate has not been submitted yet; cannot update status At line:1 char:1

• Update-ACMECertificate

•   + CategoryInfo          : NotSpecified: (:) [Update-ACMECertificate], Exception
    + FullyQualifiedErrorId : System.Exception,ACMESharp.POSH.UpdateCertificate
  
  

And when I try to submit again I get: PS <Path>> Submit-ACMECertificate Submit-ACMECertificate : asset file already exists At line:1 char:1

• Submit-ACMECertificate

•   + CategoryInfo          : NotSpecified: (:) [Submit-ACMECertificate], IOException
    + FullyQualifiedErrorId : System.IO.IOException,ACMESharp.POSH.SubmitCertificate
  
  

For the record, when I ping acme-v01.api.letsencrypt.org, it resolves and pings normally.

EDIT: I had a _ in the alias, tried again without it and it completed successfully.

[ebekker]

Are you saying you got the unresolved DNS name error when you specified an invalid "Identifier Alias"?

[plitter]

No, the alias was correct, or it didn't complain when I made it at least(there was an _ in it, but not sure if that's the error). There was some errors with the connection, so maybe its the case that connection was down when I tried to run submit and it couldn't resolve. Thanks for fast response :)

[ebekker]

Cool, yeah it sounds like this was just a case of the DNS name was temporarily not resolving for some reason.

[plitter]

I guess this is a small usecase, but I would maybe add it to the wiki or allow for asset file to resubmit the request that it made or make the program not "save" that it has been sent, so that you can resubmit.

[ebekker]

Good ideas -- I think the underlying problem is a bug in the error handling logic and the code not cleaning up after itself properly or testing for this corner case.