Error Opening Certificate Store "WebHosting" about win-acme

[Bryan-Legend]

Is IIS installed? What OS are you on?

On Thu, Dec 3, 2015 at 4:13 PM, vatara [email protected] wrote:

I get this error after getting the certificate:

Opening Certificate Store "WebHosting"
System.Security.Cryptography.CryptographicException: The system cannot find the file specified.
at System.Security.Cryptography.X509Certificates.X509Store.Open(OpenFlags flags)
at LetsEncrypt.ACME.Simple.Program.InstallCertificate(Target binding, String pfxFilename, X509Store& store, X509Certificate2& certificate) in C:\Users\Bryan\Documents\letsencrypt-win-simple\letsencrypt-win-simple\Program.cs:line 266
at LetsEncrypt.ACME.Simple.Program.Auto(Target binding) in C:\Users\Bryan\Documents\letsencrypt-win-simple\letsencrypt-win-simple\Program.cs:line 239
at LetsEncrypt.ACME.Simple.Program.Main(String[] args) in C:\Users\Bryan\Documents\letsencrypt-win-simple\letsencrypt-win-simple\Program.cs:line 171

I'm not sure why that is...do I have to setup something with the
certificate store in Windows?

—
Reply to this email directly or view it on GitHub
#18.

[ebekker]

And are you running as admin with elevated privileges?

[vatara]

This is on Server 2008 R2. Running it as administrator.

[vatara]

Oh, yes, IIS is installed also.

[Bryan-Legend]

The manifest forces admin now so that'll never be the problem.

If you goto Control Panel->Manage Computer Certificates is there a Web
Hosting group like this:

[image: Inline image 1]

On Thu, Dec 3, 2015 at 4:45 PM, vatara [email protected] wrote:

Oh, yes, IIS is installed also.

—
Reply to this email directly or view it on GitHub
#18 (comment)
.

[c1982]

No WebHosting store name on Server 2008 R2 default but exist on Windows 2012 version. May be you can create manually.

[Bryan-Legend]

WebHosting is some special store that's implemented differently for perf.

I'll add some code to detect it and drop down to Personal if it's missing.

On Thu, Dec 3, 2015 at 4:52 PM, Oguzhan YILMAZ [email protected]
wrote:

No WebHosting store name on Server 2008 R2 default but exist on Windows
2012 version. May be you can create manually.

—
Reply to this email directly or view it on GitHub
#18 (comment)
.

[WilliamStam]

where does it find the Bryan from? edit: nvm i see now that its your name :D so something is definitely hard coded in

Windows Web Server 2008 R2

[Bryan-Legend]

I'm Bryan. It's the location of the source code where it was compiled from.

On Fri, Dec 4, 2015 at 12:08 AM, William Stam [email protected]
wrote:

where does it find the Bryan from? is it hard coded?

https://camo.githubusercontent.com/6a963a339a4b3527bb3ba53fd6e9a694a3bfb88b/687474703a2f2f7075752e73682f6c494f43372f623938613633653163662e706e67

—
Reply to this email directly or view it on GitHub
#18 (comment)
.

[WilliamStam]

figured as much. im guessing its throwing a fit cause of the whole "WebHosting" thing being missing on 2008? its not actually looking at those locations right?

[rdolezel]

WebHosting certificate store is a new feature in W2012 and newer.

[WilliamStam]

yips, so basically if you're using 2008 letsencrypt-win-simple wont work.

i was curious that its looking for C:\Users\Bryan\Documents\letsencrypt-win-simple\letsencrypt-win-simple\Program.cs was wondering if its trying to call a function in the file that doesnt exist.

[rdolezel]

No worries, it's expected behavior, not related to your installation.

[Bryan-Legend]

Fixed in 1.7

https://github.com/Lone-Coder/letsencrypt-win-simple/releases/tag/v1.7

[WilliamStam]

dude you are a LEGEND!! it works flawlessly (1.7) thank you SOOOOO much!!

[sceee]

Really nice, thank you very much it works!

[WilliamStam]

it just has a hard time when you add more certs to the server tho. so be
very carefully. my certs are all messed up now i think. still trying to
figure it out. think its that whole certs must have a static ip yada thing.
so each site would need a new ip im guessing. but for a single site this
project is amazing!!!!!

On Sat, Dec 5, 2015 at 2:23 PM, sceee [email protected] wrote:

Really nice, thank you very much it works!

—
Reply to this email directly or view it on GitHub
#18 (comment)
.