Can't rip blu-ray DVD's 24 hours after paying for the key.

[blakemavrix]

I was having an issue with the beta key ripping two different blue-ray DVD's, so I bought the license key but I'm still having the same issue

Evaluation period has expired, shareware functionality unavailable.
Evaluation period has expired. Please purchase an activation key if you've found this application useful. You may still use all free functionality without any restrictions.
Failed to open disc

I also attempted to rip a standard DVD and it worked.

[dcoke22]

The current beta key is valid until the end of May. MakeMKV is free while in beta

If you purchased a license you should've gotten an email with your permanent key.

Either way, you'll have to input the key into MakeMKV and restart MakeMKV. Find the 'Register' menu item in the 'Help' menu of MakeMKV to input the key.

Purchase MakeMKV
Even in an unlicensed state MakeMKV will rip a DVD. After the initial trial period, blu-rays and 4K UHDs require either a valid beta key or a purchased key.

[blakemavrix]

Again, the beta key stopped working (even the new one for April) and even the key I purchased and applied to makemkv says it worked in the web UI, but the terminal isn't working.

[tomty89]

Web UI? How / What exactly have you installed? Some docker image / container?

[blakemavrix]

Yes actually. It's been working great, even on Bluray's right up until I bought the license key.

[tomty89]

Have you even checked what's the last time the docker image was maintained / updated? And/Or what's the version of MakeMKV it consists of? And/Or which image from who exactly? How exactly did you / were you expected to pass a key into the MakeMKV instance in the container? Have you even checked that?

[16442496]

You can always install official and supported MakeMKV from here:

viewtopic.php?f=3&t=224

and then add your key from GUI or from terminal.

There is something about keys:
https://github.com/jlesage/docker-makem ... leshooting

"MakeMKV registration key to use. The key is written to the configuration file during container startup. When set to BETA, the latest beta key is automatically used. When set to UNSET, no key is automatically written to the configuration file."