# DefaultCentralSslPfxPassword Problem

**URL:** <https://community.letsencrypt.org/t/defaultcentralsslpfxpassword-problem/88847>\
**Category:** Server\
**Created:** [March 16, 2019, 10:09am UTC](https://community.letsencrypt.org/t/defaultcentralsslpfxpassword-problem/88847 "2019-03-16T10:09:02Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joaquim1](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@Joaquim1](https://community.letsencrypt.org/u/Joaquim1)\
**Post date:** [March 16, 2019, 10:09am UTC](https://community.letsencrypt.org/t/defaultcentralsslpfxpassword-problem/88847/1 "2019-03-16T10:09:02Z")

</div>

Hi everyone,

First of allThanks to you for your great tool. My web site is HTTPS up and running Fine.

## My system :

- Windows Server 2012 R2
- [INFO] A simple Windows ACMEv2 client (WACS)
- [INFO] Software version 2.0.3.206 (RELEASE)
- [INFO] IIS version 8.5
- [INFO] Please report issues at [https://github.com/PKISharp/win-acme](https://github.com/PKISharp/win-acme)

## I use WACS which created theses files :

- C:\ProgramData\win-acme\[acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)\Registration\_v2
- C:\ProgramData\win-acme\[acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)\Signer\_v2
- C:\ProgramData\win-acme\[acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)\MYID.renewal.json
- C:\ProgramData\win-acme\[acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)\Certificates\MYID-cache.pfx
- C:\ProgramData\win-acme\[acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)\Certificates\MYID-csr.pem

## Inside MYID.renewal.json :

“Id”: MYID",  
“LastFriendlyName”: “[IISSite] Default Web Site”,  
“PfxPasswordProtected”: “enc-\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*==”,  
“TargetPluginOptions”:

## Settings:

in my SETTINGS.CONFIG in WACS folder, i tried adding my password in the VALUE section of :  
\<setting name=“DefaultCentralSslPassword” serializeAs=“String”\>  
\<value\>MYPASSWORD\</value\>  
\</setting\>  
\<setting name=“DefaultCentralSslPfxPassword” serializeAs=“String”\>  
\<value\>MYPASSWORD\</value\>  
\</setting\>

## My Issue:

My problem is that I need to use the PFXPasswordProtected, but in my application when , I call the PFX file using my password, it displays "The specified network password is not correct. ".

## Tools to acess PFX: ASP PAGE :

Commands :  
Set oEncrypt = Server.CreateObject(“Persits.CryptoManager”)  
Set oStore = oEncrypt.OpenStoreFromPFX(“C:\ProgramData\win-acme\[acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)\Certificates\MY-ID.pfx”, “MYPASSWORD”)

## Error message:

Persits.CryptoManager.1 error ‘800a0064’  
The specified network password is not correct.

## Question:

How to generate my own password to be embeded in the PFX file ?

Kind Regards,  
Joaquim

---

<div class="post-metadata">

**Author:** ![Joaquim1](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@Joaquim1](https://community.letsencrypt.org/u/Joaquim1)\
**Post date:** [March 16, 2019, 4:56pm UTC](https://community.letsencrypt.org/t/defaultcentralsslpfxpassword-problem/88847/2 "2019-03-16T16:56:15Z")

</div>

## Tools to access PFX : Windows Certificate Import Wizard :

I get the same problem when I use Windows Certificate Import Wizard  
After selecting the PFX file. I need to type the password, but I get a window “The password you entered is incorrect”.

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [March 16, 2019, 5:30pm UTC](https://community.letsencrypt.org/t/defaultcentralsslpfxpassword-problem/88847/3 "2019-03-16T17:30:13Z")

</div>

Hi @Joaquim1

> [@Joaquim1](#):
>
> My problem is that I need to use the PFXPasswordProtected, but in my application when , I call the PFX file using my password, it displays "The specified network password is not correct. ".

perhaps you use non-ASCII characters. Or the file format of your settings.conf is wrong, so the password is saved as UTF-16 or something else.

---

<div class="post-metadata">

**Author:** ![Joaquim1](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@Joaquim1](https://community.letsencrypt.org/u/Joaquim1)\
**Post date:** [March 19, 2019, 8:42pm UTC](https://community.letsencrypt.org/t/defaultcentralsslpfxpassword-problem/88847/4 "2019-03-19T20:42:12Z")

</div>

Thanks a lot JuergenAuer,

I checked all the file format and ANSI was ok. No UTF-8.

But I was doing it the wrong way.

I got the right answer from [https://github.com/PKISharp/win-acme/issues/1071](https://github.com/PKISharp/win-acme/issues/1071)

The dirty way works !

I still have an issue with (Central Certificate Store (CCS). I also posted the error in [https://github.com/PKISharp/win-acme/issues/1071](https://github.com/PKISharp/win-acme/issues/1071)

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [March 19, 2019, 9:56pm UTC](https://community.letsencrypt.org/t/defaultcentralsslpfxpassword-problem/88847/5 "2019-03-19T21:56:16Z")

</div>

> [@Joaquim1](#):
>
> I got the right answer from [DefaultCentralSslPfxPassword Problem · Issue #1071 · win-acme/win-acme · GitHub](https://github.com/PKISharp/win-acme/issues/1071)

Ah, thanks, so there are two different passwords.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [April 18, 2019, 9:56pm UTC](https://community.letsencrypt.org/t/defaultcentralsslpfxpassword-problem/88847/6 "2019-04-18T21:56:19Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
