You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: