Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System.IO.IOException: The directory name is invalid. #300

Closed
ashkansiroos opened this issue Sep 27, 2016 · 5 comments
Closed

System.IO.IOException: The directory name is invalid. #300

ashkansiroos opened this issue Sep 27, 2016 · 5 comments

Comments

@ashkansiroos
Copy link

Some months ago, I've generated my certificates using letsencrypt-win-simple and everything worked fine However, my certificate will be expired in 10 days and I did not set the auto-renewal, so I tried to regenerate the certificate the same way, but I've got this error:

Requesting Certificate
Request Status: Created
Saving Certificate to C:\Users\Administrator\AppData\Roaming\letsencrypt-win-si
mple\httpsacme-v01.api.letsencrypt.org\mydomain.com-crt.der
System.IO.IOException: The directory name is invalid.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.__Error.WinIOError()
at System.IO.Path.InternalGetTempFileName(Boolean checkHost)
at LetsEncrypt.ACME.Simple.Program.GetIssuerCertificate(CertificateRequest ce
rtificate, CertificateProvider cp)
at LetsEncrypt.ACME.Simple.Program.GetCertificate(Target binding)
at LetsEncrypt.ACME.Simple.Program.Auto(Target binding)
at LetsEncrypt.ACME.Simple.Plugin.Auto(Target target)
at LetsEncrypt.ACME.Simple.Program.Main(String[] args)

The folder
C:\Users\Administrator\AppData\Roaming\letsencrypt-win-si
mple\httpsacme-v01.api.letsencrypt.org\

Exists on the server and I could find mydomain.com-crt.der on that.

I tried removing related files in the directory, and running the file again. I've go the same error message, but also I could see that new files has been added to \httpsacme-v01.api.letsencrypt.org\ folder.

@ashkansiroos
Copy link
Author

P.S: I have the latest version (v1.9.1) and I am running it on windows server 2012 R2.
Also, I ran it using CMD (Administrator)

@Frogglet
Copy link

Frogglet commented Oct 3, 2016

Hey I had this problem as well, and I was able to solve it after installing new updates and disabling symantec antivirus on the server. Hope that helps.

@cgq355716727
Copy link

Hey I had this problem as well

@jclimac
Copy link

jclimac commented Apr 3, 2017

I'm getting exactly the same error. Using V1.9.3, running as administrator.

Is there any workaround?

Thanks!!

@WouterTinus
Copy link
Member

This should be fixed in #496, please report any issues there!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants