[GH-ISSUE #134] SEC_ERROR_LEGACY_DATABASE #81

New issue

Closed

opened 2026-02-25 22:32:33 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 22:32:33 +03:00

Owner

Originally created by @tim-field on GitHub (Feb 12, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/134

Using the latest binary I'm getting the following error in ubuntu 16.10

./mkcert -install
Using the local CA at "/home/tim/.local/share/mkcert" ✨
ERROR: failed to execute "certutil -A": exit status 255

certutil: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key database is in an old, unsupported format.

There are a couple issue that reference this, but they are both closed #12 so not sure if this is a regression ?

Originally created by @tim-field on GitHub (Feb 12, 2019). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/134 Using the latest binary I'm getting the following error in ubuntu 16.10 ``` ./mkcert -install Using the local CA at "/home/tim/.local/share/mkcert" ✨ ERROR: failed to execute "certutil -A": exit status 255 certutil: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key database is in an old, unsupported format. ``` There are a couple issue that reference this, but they are both closed #12 so not sure if this is a regression ?

kerem closed this issue

2026-02-25 22:32:33 +03:00

kerem commented

2026-02-25 22:32:33 +03:00

Author

Owner

@adamdecaf commented on GitHub (Feb 13, 2019):

What version of Firefox/Chrome are you using? 16.10 might have the older cert8.db format, but that should still be supported by mkcert.

@adamdecaf commented on GitHub (Feb 13, 2019): What version of Firefox/Chrome are you using? 16.10 might have the older cert8.db format, but that should still be supported by mkcert.

kerem commented

2026-02-25 22:32:33 +03:00

Author

Owner

@tim-field commented on GitHub (Feb 13, 2019):

Firefox 65 ( default browser )
Chrome 72.0.3626.96 (Official Build) (64-bit)

@tim-field commented on GitHub (Feb 13, 2019): Firefox 65 ( default browser ) Chrome 72.0.3626.96 (Official Build) (64-bit)

kerem commented

2026-02-25 22:32:33 +03:00

Author

Owner

@adamdecaf commented on GitHub (Feb 14, 2019):

Those should both be on cert9.db, so the problem might be permissions or path related. Did mkcert output any additional debug information?

You're on v1.3.0, right? Did any debug tips from https://github.com/FiloSottile/mkcert/issues/12 give more information?

@adamdecaf commented on GitHub (Feb 14, 2019): Those should both be on cert9.db, so the problem might be permissions or path related. Did `mkcert` output any additional debug information? You're on v1.3.0, right? Did any debug tips from https://github.com/FiloSottile/mkcert/issues/12 give more information?

kerem commented

2026-02-25 22:32:33 +03:00

Author

Owner

@tim-field commented on GitHub (Feb 20, 2019):

Ok I looked in profile ~/.mozzila/firefox and found a few profiles, all seemed to still be using cert8.db

I removed this directory, and started firefox again, and mkcert now works! So something up with my firefox install then, not updating its cert database.

@tim-field commented on GitHub (Feb 20, 2019): Ok I looked in profile ~/.mozzila/firefox and found a few profiles, all seemed to still be using cert8.db I removed this directory, and started firefox again, and mkcert now works! So something up with my firefox install then, not updating its cert database.