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

--centralsslstore not creating multiple pfx files like it did before #584

Closed
FreakyBigFoot opened this issue Sep 25, 2017 · 1 comment
Closed
Assignees

Comments

@FreakyBigFoot
Copy link

FreakyBigFoot commented Sep 25, 2017

I can't seem to find any documentation about this changing. In earlier version I would run this command: letsencrypt.exe --san --centralsslstore D:\certs\

This would create a pfx file for each binding and automatically update the IIS instance with the 2 443 bindings.(domain.com & www.domain.com)

I tried using this command: letsencrypt.exe --plugin iissite --siteid 1 --centralsslstore "d:\certs"

This only created 1 pfx file for domain.com. The script use to create 1 pfx file per binding.

Any input would be greatly appreciated. The way centralized SSL works is the pfx file name needs to match the binding so 2 need to be created.

Edit: It is creating both new bindings in IIS, it's just not creating a pfx for each binding. So only domain.com is viewable with SSL while www.domain.com fails.

@FreakyBigFoot FreakyBigFoot changed the title --centralsslstore not creating 2 pfx files like it did before --centralsslstore not creating multiple pfx files like it did before Sep 25, 2017
@WouterTinus WouterTinus self-assigned this Sep 25, 2017
WouterTinus added a commit that referenced this issue Sep 27, 2017
@WouterTinus
Copy link
Member

This has been fixed in v1.9.6.2

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

No branches or pull requests

2 participants