SadTalker and NVIDIA GeForce RTX 5060 Ti

John6666 · November 17, 2025, 6:15am

It looks like git or git-lfs didn’t complete properly…?

Good, this explains the problem very clearly.

Right now your Comfyui-SadTalker folder only contains SadTalker/:

$ cd ~/comfy/sadtalker/ComfyUI/custom_nodes
$ ls
Comfyui-SadTalker

$ ls Comfyui-SadTalker
SadTalker

But the real plugin repo on GitHub looks like this:

Comfyui-SadTalker/
  SadTalker/
  examples/
  nodes/
  web/
  workflow/
  README.md
  __init__.py
  requirements.txt

So in your new workspace you only copied the **model directory** (`SadTalker/.../checkpoints`) but **none of the Python code** (`__init__.py`, `nodes/`, etc.).  

If there is no `__init__.py` and no `nodes/`, ComfyUI cannot register nodes named `SadTalker`, `ShowAudio`, `LoadRefVideo`, `ShowVideo`. That is exactly why the workflow pop-up says those node types are missing.

The good news: this is easy to fix.

---

## 1. Fix the plugin folder (get the full code, not only models)

You have two ways: copy from your old install, or re-clone from GitHub.

### Option A: copy the full plugin from the first ComfyUI

If your original ComfyUI (the first one) has a working Comfyui-SadTalker, just copy it.

```bash
# activate the venv for the NEW install (so you don't get confused)
source ~/comfy/comfy-env/bin/activate

# remove the incomplete folder in the new workspace
rm -rf ~/comfy/sadtalker/ComfyUI/custom_nodes/Comfyui-SadTalker

# copy the complete plugin directory from the first ComfyUI
cp -a ~/comfy/ComfyUI/custom_nodes/Comfyui-SadTalker \
      ~/comfy/sadtalker/ComfyUI/custom_nodes/

Then check:

cd ~/comfy/sadtalker/ComfyUI/custom_nodes/Comfyui-SadTalker
ls
# you should now see something like:
# SadTalker  examples  nodes  web  workflow  README.md  __init__.py  requirements.txt

Your checkpoints can stay where they are; you’ve already copied them into SadTalker/checkpoints.

Option B: re-clone from GitHub in the new workspace

If you’d rather pull a fresh copy:

source ~/comfy/comfy-env/bin/activate

cd ~/comfy/sadtalker/ComfyUI/custom_nodes
rm -rf Comfyui-SadTalker
git clone https://github.com/haomole/Comfyui-SadTalker.git

cd Comfyui-SadTalker
ls
# expect: SadTalker  examples  nodes  web  workflow  README.md  __init__.py  requirements.txt

Now recreate the checkpoints directory inside this fresh repo and copy your model files into it:

mkdir -p SadTalker/checkpoints
cp ~/comfy/ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints/* \
   SadTalker/checkpoints/

(Or copy from wherever you originally downloaded the SadTalker models.)

2. Install the plugin’s Python dependencies (in this venv)

Still inside the venv and the new plugin:

cd ~/comfy/sadtalker/ComfyUI/custom_nodes/Comfyui-SadTalker
python -m pip install -r requirements.txt

On Python 3.11 this should pull prebuilt wheels (including numpy==1.23.4) and finish quickly. (GitHub)

If pip complains about some missing build tool or a single package, install that package separately in the same venv and rerun.

Example manual installs that fix the usual errors:

python -m pip install moviepy==1.0.3 imageio[ffmpeg] librosa soundfile

A Reddit user with the same “Missing Node Types: SadTalker, ShowAudio, LoadRefVideo, ShowVideo” pop-up fixed it by installing moviepy into the ComfyUI environment. (Reddit)

3. Restart ComfyUI and check the import log

Now restart ComfyUI from the terminal so you can see errors:

cd ~/comfy/sadtalker
comfy --workspace=~/comfy/sadtalker launch -- --listen 127.0.0.1 --port 8190

On startup you should see a section like:

0.0 seconds: .../custom_nodes/Comfyui-SadTalker

If you still see:

0.0 seconds (IMPORT FAILED): .../custom_nodes/Comfyui-SadTalker

read the few lines above that line: they will say which module is missing (e.g. No module named 'moviepy.editor'). Install that module into this venv and restart again.

4. Confirm the nodes now exist in the UI

Once there is no (IMPORT FAILED):

Open ComfyUI in your browser on http://127.0.0.1:8190.
Right-click → node search, type SadTalker.
You should see nodes named:
- SadTalker
- ShowAudio
- LoadRefVideo
- ShowVideo

These node names come directly from the plugin’s nodes directory and __init__.py mappings. (GitHub)

If you can add them manually, loading your workflow will no longer show the “Some Nodes Are Missing” dialog.

5. How to isolate problems in ComfyUI (beginner-safe checklist)

When any custom node gives you trouble, use this pattern:

Check folder layout
- custom_nodes/<PluginName>/ should match the GitHub repo (look for __init__.py, nodes/, requirements.txt). (GitHub)
Always run ComfyUI from a terminal
- Watch for lines like IMPORT FAILED and read the traceback directly above them. That tells you the real cause. (GitHub)
Install missing Python packages in the same venv
- source <venv>/bin/activate
- python -m pip install <package>
Keep data separate from code in your head
- Checkpoints/weights (*.safetensors, *.pth) only affect running the node.
- Missing node pop-ups are almost always due to code not loading, not missing weights.
Test the plugin alone if needed
- Temporarily rename other custom_nodes/* folders with .off at the end, restart, and see if the problem persists. This makes it clear whether the issue is that plugin or a conflict.

Bottom line

Your new workspace currently has only the SadTalker/ model directory, not the full Comfyui-SadTalker plugin.
Fix by copying or cloning the entire repo (with nodes/, __init__.py, etc.), then installing its requirements in the same venv.
After that, ComfyUI should register the SadTalker, ShowAudio, LoadRefVideo, and ShowVideo nodes, and the workflow will load normally.

John6666 · November 17, 2025, 6:22am

Oh…

There are many reports of Git-related problems around ComfyUI, but they fall into a few clear buckets. Knowing which bucket you’re in makes debugging much easier.

1. Where Git is used in the ComfyUI world

Git gets invoked in several places:

Installing / updating ComfyUI itself (git clone, git pull, comfy-cli). (ComfyUI)
Installing custom nodes via ComfyUI-Manager (“Install”, “Update”, “Install via Git URL”, “Try fix”). (Hugging Face)
Manual custom-node install (you yourself git clone into custom_nodes/). (ComfyUI)

So when “Git fails with ComfyUI” it is usually one of:

Git itself is missing or not visible.
Manager / comfy-cli can’t run Git (PATH / security).
Git can’t reach GitHub (network).
The ComfyUI folder is not a git repo, so git pull / “Update ComfyUI” fails.

2. Common, documented Git failures

2.1 Git missing or not on PATH

Symptoms:

ComfyUI desktop / Manager says “Git is not installed” even though you installed it.
Running git inside the UI’s bundled shell fails.

Examples:

Windows Git installed via Scoop is not detected; ComfyUI shows an error screen even though git --version works in a normal terminal. (GitHub)
Users see the classic "'git' is not recognized as an internal or external command" until they add Git’s cmd directory to PATH. (Stack Overflow)

Fix pattern (applies to Linux too, just with different paths):

In the same shell / venv that runs ComfyUI, run:
```
git --version
which git           # Linux/macOS
```
If this fails or which git is empty, Git is not visible to that environment.
Install Git or add it to PATH (Linux: sudo apt install git; Windows: add C:\Program Files\Git\cmd to PATH). (ComfyUI Wiki)

2.2 “Bad git executable” in ComfyUI-Manager (GitPython)

Manager uses GitPython. If GitPython can’t find a working git binary, you get:

“Bad git executable… All git commands will error until this is rectified.” (GitHub)

This appears in the ComfyUI console and Manager logs.

Fix:

Ensure git is on PATH for the ComfyUI process, or set GIT_PYTHON_GIT_EXECUTABLE=/full/path/to/git. (GitHub)

2.3 Security level blocking Git operations (your earlier error)

ComfyUI-Manager has a security policy. At the default security_level = normal, it blocks installing some custom nodes and Git URLs and shows:

“This action is not allowed with this security level configuration.” (GitHub)

This is not Git breaking; Manager is deliberately refusing to run Git for that operation.

Fix:

Edit ComfyUI/user/default/ComfyUI-Manager/config.ini. (GitHub)
Set:
```
security_level = weak
```
Restart ComfyUI, install the needed node, then optionally set it back to normal.

Several guides and posts (including in Japanese) describe exactly this step to get past the “not allowed” error when installing nodes via Git URL. ((note Subtitles))

2.4 Git can’t talk to GitHub (network / proxy / firewall)

If your OS or hosting environment can’t reach github.com, Manager reports install failures and logs git clone errors. The Comfy forum has threads where Manager fails to install nodes and logs show Git itself failing to clone due to network problems. (ComfyUI)

Fix pattern:

From the same machine, run in a terminal:
```
git ls-remote https://github.com/comfyanonymous/ComfyUI.git
```
or any node repo. If this fails, the issue is firewall, DNS, or proxy—not ComfyUI.
Configure your proxy (e.g. http_proxy, https_proxy) or whitelist GitHub.

2.5 “fatal: not a git repository” when updating ComfyUI

If ComfyUI was installed from a zip and not via git clone, the folder has no .git directory. Then running git pull or Manager’s “Update ComfyUI” yields:

fatal: not a git repository (or any of the parent directories): .git (GitHub)

Fix:

Reinstall ComfyUI using git clone as the docs recommend, or accept that you can’t update via Git in that copy. (ComfyUI)

2.6 Manager “Install via Git URL” button doing nothing (UI bug)

There is at least one Desktop/Manager bug where clicking “Install via Git URL” simply doesn’t open the dialog. Users report this on the Comfy forum. (ComfyUI)

Fix / workaround:

Update to the latest ComfyUI-Manager and Desktop build.
If still broken, manually git clone the node into custom_nodes/ and pip install -r requirements.txt. (ComfyUI)

3. How to systematically isolate Git problems (beginner-safe)

You can follow this checklist on your Linux host:

Check Git itself (inside your Comfy venv)
```
source ~/comfy/comfy-env/bin/activate  # or your venv
git --version
which git
```
- If either fails → install Git or fix PATH. (ComfyUI Wiki)
Check ComfyUI’s log for Git/Manager errors
- Start ComfyUI from a terminal.
- Look for lines mentioning:
  - Bad git executable (GitPython) (GitHub)
  - This action is not allowed with this security level configuration (Manager security) (GitHub)
  - fatal: not a git repository (not cloned with Git) (GitHub)
Test network access to GitHub
```
git ls-remote https://github.com/ltdrdata/ComfyUI-Manager.git
```
- If this fails while your browser can reach GitHub, you likely have a proxy or firewall rule affecting the terminal. (ComfyUI)
For node installs that Manager refuses
- Edit ComfyUI-Manager/config.ini and temporarily set security_level = weak, as described in multiple guides. (comfyui-guides.runcomfy.com)
If Manager UI is flaky
- Update ComfyUI-Manager and ComfyUI to current versions.
- If “Install via Git URL” still doesn’t open, use manual git clone as docs describe. (ComfyUI)

Short answer

Yes, there are many reports of Git failing around ComfyUI—but they’re mostly about environment and Manager settings, not ComfyUI’s core engine.
For your environment (Linux + venv), the safest approach is:
1. Verify git and network from the same venv.
2. Check Manager’s security level and logs.
3. If Manager is awkward, fall back to git clone + pip install -r requirements.txt in custom_nodes/.

Vihaananand · November 17, 2025, 10:49am

Hello,
To install SadTalker I used the following command:
$ comfy --workspace=~/comfy/sadtalker install

Topic		Replies	Views
"Load Diffusion Model" and "Unet Loader (GGUF)" null/undefined Beginners	8	9697	March 22, 2025
I cannot seem to run any workflow on runpod on comfyui Models	3	121	January 5, 2026
Forge & Comfyui Problems Beginners	5	1124	February 12, 2025
The newest newbie for ComfyUI Beginners	1	217	June 17, 2025
Looking for an open source image-to-video to test with Intel ARC GPU Beginners	13	1613	February 26, 2025

SadTalker and NVIDIA GeForce RTX 5060 Ti

Option B: re-clone from GitHub in the new workspace

2. Install the plugin’s Python dependencies (in this venv)

3. Restart ComfyUI and check the import log

4. Confirm the nodes now exist in the UI

5. How to isolate problems in ComfyUI (beginner-safe checklist)

Bottom line

1. Where Git is used in the ComfyUI world

2. Common, documented Git failures

2.1 Git missing or not on PATH

2.2 “Bad git executable” in ComfyUI-Manager (GitPython)

2.3 Security level blocking Git operations (your earlier error)

2.4 Git can’t talk to GitHub (network / proxy / firewall)

2.5 “fatal: not a git repository” when updating ComfyUI

2.6 Manager “Install via Git URL” button doing nothing (UI bug)

3. How to systematically isolate Git problems (beginner-safe)

Short answer

Related topics