Certificate request process failed: System.IO.DirectoryNotFoundException

Hey there!

Not sure what I’m doing wrong here, but I setup a new domain “con.xxxxxx.cc” and when requesting a Cert, I get the following error. I’ve tried re-creating the certificate within Certificate Manager, and am still getting the same error.
Using DNS auth with Let’s Encrypt, and that all works correctly.

I cannot seem to find where to input a file path?

Certificate request process failed: System.IO.DirectoryNotFoundException: Could not find a part of the path ‘\.\con’.

It sounds like you might be using a Deployment Task like Deploy to Generic Server or Deploy to Apache.

These tasks ask for a file path for the exported certificate components and a common mistake is to only provide a folder, not a file name. You also need to provide the full path, not a relative path. So for instance to export a private key you would need something like C:\certs\privatekey.pem. The filename doesn’t matter too much depending on how you’re going to use is, but it can’t just be a folder name.

See also: Deployment Task - Deploy to Apache | Certify The Web Docs

The file paths are specified under the Tasks tab, edit your task and click the Task Parameters tab.

Note that if you have previous requested your cert ok but the deployment task failed, you don’t have to request your certificate again, just edit your Task , Save then click the Play button next to the task to try running the task.

Thank you! I have modified this, as it was missing, however, it is still giving me the same error. If I click the play button, it says the Source Certificate is missing.

@Turner you do need to complete a certificate request (click Request Certificate and have it proceed as far as your deployment tasks) at least once so that there’s a certificate to convert. Once your actual certificate order completes the managed certificate configuration has a certificate it can work with from then on, even if a deployment task then fails.

Be aware that if you delete your entire managed certificate configuration and start a new the app won’t know you previously had a cert, so don’t delete as you are then likely to run into issues with Certificate Authority rate limits (duplicate certificate order limits etc) and then you either have to change CA to keep working or wait for the rate limit to expire.

I am really not sure what I’m doing wrong. I created a brand new certificate request, just asking it to store in the certificate store. No extra tasks, still getting the same error.

Can I see a full log file? You can message it to me if you like, or just email support {at} certifytheweb.com

I should ask, does the path \con mean something to you or is Windows coming up with this path itself? “CON” is an old dos name and it’s making me wonder if there is something weird going on with this machine.

Is the app managing to creating a folder at C:\ProgramData\certify ok? There should be a bunch of files in there including an “assets” folder that contains folders with your certificate PFX files.