openVPN minor problem

I am installing openvpn for one of my current personal research project. During the signing of certificate, I encounter a minor problem.

Certificate is to be certified until Jun 3 16:09:50 2017 GMT (3650 days)
Sign the certificate? [y/n]:y
failed to update database
TXT_DB error number 2

I went to Google and found out that alot of people are giving different advice which might due to the different method of setup for the software. So I try to solve the problem based on the error given, after 30 minutes of pulling my hair, I finally managed to solve it. It is due to the one of the value (commonName) insert during the signing of certificate.

The commonName for Certificate authority and client certificate must not be the same.

Just sharing one of my problem encountered today :)

20 Comments

  1. Ciaran:

    That one’s tripped me up several times – not a friendly error message at all. Glad you solved it.

  2. admin:

    Ya, I love to solve error because it’s challenging :D

    Enjoy!

  3. iggy:

    Thanks heaps,

    You have saved me hours of frustration.

    Al the best.

  4. frebal:

    Thank you for solving that problem.

  5. admin:

    Most welcome! :D

  6. Mike:

    Man! This was extremely helpful! Many THANKS!

  7. LinkRage:

    Thanks man!!! You’ve just saved me hours or something…! ;)

  8. Vlad:

    Mike – that was briliant! Thank you very much

  9. Turmis:

    Thanks!! I love you :)

  10. admin:

    You are most welcome guys. I’m glad to help along.

  11. John Bond:

    Thanksssssssss Mannnn God Bless you

  12. Ed:

    Bless you dude, you ended my 2-hour swearing

  13. Toby:

    Didn’t do the trick :-/

  14. admin:

    Let me know the exact error message you get.

  15. Mykeself:

    Thanks dude, might this help you climb higher in Google#s ranking!

  16. Anthony Altemara:

    Thanks!!!!

  17. Mike:

    had the same but still getting it, with “could not find C:\program files\openvpn\easy-rsa\keys\*.old” any ideas?

  18. Vike:

    I had a similar thing happen, but for me it was because I already had an old key with that name and hadn’t revoked it. You have to revoke it to overwrite it with a new key- use “revoke-full keyname”

  19. Ben:

    Thank you!!! Took me forever, but this was the last site i found when i googled the problem and it was the fix. None of the tutorials tell you this!

  20. indra:

    Thanks a lot … my mistake is i input my server name 2 times when creating new client cert
    Common Name (eg, your name or your server’s hostname)[]

    * i thought i must input my server hostname here lol

Leave a comment