Necessary
Essential for the website's basic functionality.
By default, when an unrecognized disc is loaded, MakeMKV generates a dense cryptographic dump file ( .tgz ) and checks online servers for a corresponding verified key hash.
The Ultimate Guide to KeyDB.cfg for MakeMKV: Fix "Volume Key is Unknown" Errors
However, the keyword keydb.cfg often surfaces in the MakeMKV community for two specific reasons:
When the user wants to view information about the movie, they can use the keydb-cli command to retrieve the metadata from the KeyDB database. This can be done using a simple command, such as:
If you are seeing "The volume key is unknown" errors in MakeMKV even after trying to use a KEYDB.cfg file, consider these steps:
If you are running MakeMKV inside a Docker container (e.g., the jlesage/docker-makemkv image), the process is slightly different. You need to locate the container's equivalent of the data directory. While there's some debate about the necessity of the file (as MakeMKV has its own automatic downloader), users have reported success by adding the keydb.cfg file directly to the /appdata/config/data folder within the container. Additionally, you can specify the app data directory location in the settings.conf file, which tells the container where to look for KEYDB.cfg .
By default, when an unrecognized disc is loaded, MakeMKV generates a dense cryptographic dump file ( .tgz ) and checks online servers for a corresponding verified key hash.
The Ultimate Guide to KeyDB.cfg for MakeMKV: Fix "Volume Key is Unknown" Errors
However, the keyword keydb.cfg often surfaces in the MakeMKV community for two specific reasons:
When the user wants to view information about the movie, they can use the keydb-cli command to retrieve the metadata from the KeyDB database. This can be done using a simple command, such as:
If you are seeing "The volume key is unknown" errors in MakeMKV even after trying to use a KEYDB.cfg file, consider these steps:
If you are running MakeMKV inside a Docker container (e.g., the jlesage/docker-makemkv image), the process is slightly different. You need to locate the container's equivalent of the data directory. While there's some debate about the necessity of the file (as MakeMKV has its own automatic downloader), users have reported success by adding the keydb.cfg file directly to the /appdata/config/data folder within the container. Additionally, you can specify the app data directory location in the settings.conf file, which tells the container where to look for KEYDB.cfg .