• After configuring the API key following errors occur

    An error occurred: Unable to parse the p12 file. Is this a .p12 file? Is the password correct? OpenSSL error: error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag. Your settings could not be saved.

    Help me out solving this

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Moch Amir

    (@moch-a)

    your server can not read your p12 file
    please make sure the url pointed to p12 file is correct

    Hi,
    I have exactly the same error message. If I take the url that is in the field “Private Key Url Path” and enter it as an address in my browser, my p12 file starts to download. So that means that the address is correct doesn’t it? If I open the file in notepad++, it’s a lot of encrypted text, so I assume that’s the correct p12 file.

    Any ideas of what other reasons the plugin would say “unable to parse” than it simply couldn’t find the file?
    Thanks!

    Plugin Author Moch Amir

    (@moch-a)

    Yes, that was correct

    then the problem is in the api key
    just create/generate new one

    Ok, just created a new one. Looks like the same error:

    An error occurred: Unable to parse the p12 file. Is this a .p12 file? Is the password correct? OpenSSL error: error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag. Your settings could not be saved.

    So what do I do now?

    Plugin Author Moch Amir

    (@moch-a)

    remove whitespace from your p12 url

    There WAS whitespace. I removed it, but still got exactly the same error message. Is there some more debugging I could turn on or logs I could look at or could I send you the P12 file?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Unable to parse .p12 file’ is closed to new replies.