Download fail for 1.18.3 bin file on linux

[Richo]

Hi, I am trying to download the latest version of installer and the bin download either fails with a 520 error or is corrupt on expansion. The OSS file works fine. I use the repository on Mint but on a pure Debian OS I get errors on various python components so I have installed 1.18.1 manually. Just trying to upgrade. I have tried the download on multiple computers without luck.

Any suggestions?

[16442496]

Both, bin and oss works fine on pure, real Debian.

Open Terminal and try with wget:

wget https://www.makemkv.com/download/makemk ... 8.3.tar.gz && wget https://www.makemkv.com/download/makemk ... 8.3.tar.gz

[Richo]

I am still getting errors on the bin file. If you downloaded it fine, I can only assume it is corrupted geocaching for Australia or maybe slow network between me and my download location. My internet is fine but I could see that the download is very slow for the size of the files. I will try again tomorrow.

[Richo]

Re-reading your comment, I only mentioned the different OS' not in terms of compatability but as to why I was using the download rather than the repo. My specific problem is the download failure, not compatibility. Not sure if that is what you tried or if you were just saying that the download file will work on Debian. I have the 1.18.1 working on Debian so I have no reason to suspect that 1.18.3 would not work.

[maddy]

My recent system updates (which include the automated build and installation of makemkv from the provided packages) have begun failing with a hash mismatch error.

Code: Select all

┃ error: hash mismatch in fixed-output derivation '/nix/store/r8m5gqcrjk5lf2p07ws7zl4hag7a82gm-makemkv-bin-1.18.3.tar.gz.drv':
┃          specified: sha256-we5yCukbJ2p8ib6GEUbFuTRjGDHo1sj0U0BkNXJOkr0=
┃             got:    sha256-s8qloVEQU7+8HKLPo52FoPvhvuDZfqMzXndVoNzOkEM=

While debugging this, I tried downloading the package manually, and found that I was unable to extract it:

Code: Select all

$ wget https://www.makemkv.com/download/makemkv-bin-1.18.3.tar.gz
--2026-02-24 23:40:44--  https://www.makemkv.com/download/makemkv-bin-1.18.3.tar.gz
Resolving www.makemkv.com (www.makemkv.com)... 104.21.49.241, 172.67.195.244, 2606:4700:3035::ac43:c3f4, ...
Connecting to www.makemkv.com (www.makemkv.com)|104.21.49.241|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/octet-stream]
Saving to: ‘makemkv-bin-1.18.3.tar.gz’

makemkv-bin-1.18.3.tar.gz             [ <=>                                                          ]  16.98K  --.-KB/s    in 0.001s

2026-02-24 23:41:26 (24.5 MB/s) - ‘makemkv-bin-1.18.3.tar.gz’ saved [17383]

$ sha256sum makemkv-bin-1.18.3.tar.gz
b3caa5a1511053bfbc1ca2cfa39d85a0fbe1bee0d97ea3335e7755a0dcce9043  makemkv-bin-1.18.3.tar.gz
$ tar xfz makemkv-bin-1.18.3.tar.gz

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

I presume this is the cause of the errors.

[16442496]

Still works great with Debian 13 Stable.

Downloading and extracting with no errors.

Wget 1.25.0-2
Tar 1.35+dfsg-3.1

sha256sum are:
makemkv-bin-1.18.3.tar.gz
c1ee720ae91b276a7c89be861146c5b934631831e8d6c8f453406435724e92bd

makemkv-oss-1.18.3.tar.gz
bc8bb084ae3aabcd503d5bb93efc273e046e4fd4663d39a9836ce0c047fee823

I have no clue what is going on, on your machines.

[Richo]

Glad to hear I am not the only one Maddy. I ended up downloading it on my mobile phone as I still can't download it from the site on my home connection on any OS via any method (wget or browser). Hope the mobile phone method works for you. By the way I am running a pfsense firewall, but there was nothing obvious in the logs. I turned off pfBlockerNG, but that did not make any difference.

[Richo]

So I just upgraded my pfSense from 2.8.0 to 2.8.1 and I can now download it fine, go figure. I actually had to rebuild it as the NVMe crashed so maybe it was the drive casuing issues. I did not realise it had died until I tried to upgrade as I have not turned it off in months. If you have the same scenario, probably do some hardware testing before you reboot. Unlikely to be the issue for you but check your HDD for errors anyway.

[maermold]

I've noticed difficulty downloading the 1.18.3 files, or really any file.

I have been troubleshooting a persistent issue with MakeMKV 1.18.3 on a Linux/ARM environment for the past 7 days. After extensive testing, it appears that a seeming MakeMKV server instability is triggering a critical failure in the software’s network error-handling logic, rendering the Linux binary effectively unusable during this outage.

Symptom
When running makemkvcon (either via ARM/Docker or direct CLI), the process enters a permanent 100% CPU hang.
By enabling --debug, the log reveals the process is stuck in an infinite loop at this stage:
No SDF v0a5: [Drive ID]
SDF auto v0a5: [Drive ID]
Technical Investigation & "Broken Handshake"

Through network analysis and command-line isolation, I have confirmed the following from my part of the internet:
DNS Resolution: www.makemkv.com and forum.makemkv.com resolve correctly to Cloudflare IPs (172.67.195.244 / 104.21.49.241). However, ident.makemkv.com (which formu/reddit, I don't remember states this is used for key validation) does not resolve at all, even when queried directly against the authoritative NS servers.

CDN Failure: While the website may appear to load, it is sporadic. I have frequently encountered Cloudflare "Host Error" pages, indicating the origin server behind the CDN is unreachable.

The 8KB "SDF" Trap: Attempts to fetch https://www.makemkv.com/sdf.bin via CLI often result in an 8.2KB file. This is NOT the SDF table; it is the HTML for the Cloudflare 502/504 error page. The Linux binary appears to try and parse this HTML as a binary file, fails, and retries indefinitely, pinning the CPU.
This behavior of difficulty in retrieving files also extends to makemkv-bin-1.18.3.tar.gz and makemkv-oss-1.18.3.tar.gz

The "Unshare" Test: By running sudo unshare -n makemkvcon -r info dev:/dev/sr0 (stripping network access), the 100% CPU loop disappears instantly. However, the binary then fails with "This application version is too old," likely because it cannot perform the required "heartbeat" to validate the current Beta key or internal expiration date.

Evidence of Longevity
This doesn't appear to be a minor blip. Based on my logs and external reports:
Reddit reports suggest this behavior has been ongoing for ~7 days.
Forum metadata suggests origin server instability dating back to at least 2/11/26.
This renders automation tools like ARM (Automatic Ripping Machine) or MakeMKV-Auto-Rip completely non-functional as they cannot bypass the network-induced hang.

Potential Workaround/Ask
Manually injecting a verified 2MB sdf.bin into ~/.MakeMKV or _private_data.tar did not resolve the issue for me on 1.18.3; the binary still insisted on the "SDF auto" network check.

Is there a way to force the Linux binary into a "Strictly Offline" mode that honors local SDF files and the Beta key without the ident handshake? Or is 1.17.7 the only path forward until the origin server is restored?

[Salty_NZ]

Also unable to download them here. Same issue as others; I get about 17KB (which seems to actually be the beginning of the correct file; if gunzip < (file) I can see expected text like bits of a Makefile etc.) I'm in New Zealand.