Lmcq Auth Flux Decryption

If you've been handed a Flux model encrypted with LmcqAuthFluxEncryption, this is the node that decrypts and loads it - the Flux-specific counterpart to the pack's general LmcqAuthModelDecryption. It outputs a single MODEL, matching how Flux is normally loaded in ComfyUI: as a standalone diffusion-model file, separate from CLIP and VAE, unlike the bundled-checkpoint pattern SD1.5 and SDXL use.

The fields. model_name is a dropdown of encrypted Flux files it can find locally. model_password is the string the creator encrypted it with - exact match required. weight_dtype is the one field that isn't about encryption at all: it's the precision to load the decrypted weights at, with default, fp8_e4m3fn, fp8_e4m3fn_fast, and fp8_e5m2 as options - the same choice you'd make on a standard Flux UNET loader. This matters for VRAM: fp8 roughly halves memory versus full precision and, per community testing, does it at near-zero quality cost for Flux-class models, so if you're tight on VRAM, one of the fp8 options is the one to reach for rather than leaving it on default.

Why this outputs just MODEL. Because it's decrypting the diffusion transformer specifically, not a full checkpoint - you'll still need a separate CLIP loader and VAE loader wired in alongside it, exactly the way you would for any other Flux setup. If your workflow is failing downstream with a missing CLIP or VAE, that's expected here, not a bug in this node - it was never going to provide them.

The cloud dependency. This is part of LMCQ's Auth family, which per the README ties into a hosted authentication server for real-time validation - creators register there, and decryption can check machine binding, expiration, or usage limits against that service rather than purely offline. If decryption fails for reasons that don't look like a typo'd password, an unreachable auth server or an expired/limit-hit license on the creator's account is worth ruling out - something only the creator can resolve on their end, not something you can work around locally.

Installing it. Through ComfyUI Manager (search "ComfyUI-LMCQ") or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/sebord/ComfyUI-LMCQ

Restart ComfyUI afterward.

The bug that actually causes most support requests. Before chasing a password issue, check whether the node loaded at all - there's a well-documented, recurring problem where this pack's compiled runtime-protection module goes missing after install, throwing ModuleNotFoundError: No module named '...runtime.model_protection' (or api_model_protection) at ComfyUI startup. It's been reported directly by Flux NF4/Flux users on r/comfyui hitting this exact trace and getting stuck with no node in their list at all. Because the failure happens inside the pack's shared __init__.py, it doesn't just break this decryption node - it takes down the entire pack's registration, so if you're missing this node, you're missing all of them, image saver and utility nodes included. The pack's January 2026 changelog documents the fix: copy the Python-version-matching runtime files into the runtime folder, delete the mismatched ones, restart ComfyUI.

If the node does load and decryption still fails, work through it in order: confirm the password by copy-pasting rather than retyping it, check the file wasn't corrupted or partially downloaded, and if it was machine-locked, confirm your machine's code (from LmcqGetMachineCode) was actually added before the file was encrypted - a mismatch there needs the creator to re-issue the file, not something fixable on your side.