Eugene Bekker

So to get most of you past this issue for now, you can set an optional [`WriteOutPath`](https://pkisharp.github.io/ACMESharp-docs/ext_docs/handlers/manual.html#write-out-path) to redirect the output to a file. And then you can open and...

@EagleIJoe -- the issue here is actually a bit more involved than that. The problem is that the Handler is writing its output directly to `Console.Out` (i.e. STDOUT of the...

@b9chris, good suggestion, contributions are always welcome!

Looks like a bug. Can you try running the clean up again, and immediately after you get the error, can you run this block of PS code: ```powershell & {...

What version of ACMESharp are you using? ```powershell PS> Get-Module ACMESharp | select Version ```

Actually, I found the bug -- it's at [this line](https://github.com/ebekker/ACMESharp/blob/f507d2328e6c2a2e7ccaeb037492698a22a601c4/ACMESharp/ACMESharp/AcmeClient.cs#L457) in the code that you have. And I was able to verify it with my (latest) version as well.

Can you try to run the same clean up operation again but this time, add the `-Regenerate` parameter flag to your command?

It is temporary, yes, there's some state that's being deleted and overwritten accidentally, and the flag I gave you forces ACMESharp to recompute that state with the CleanUp invocation.

Will do, thanks

Can I ask, how did you discover this issue? If you don't have an empty domain, I assume you didn't run into it personally? Was it reported by someone else?