Runtime error diagnosed: the Space downloads its own model from a gated repo, so startup gets a 403

#10
by nootxlm - opened

This Space is in RUNTIME_ERROR. The startup traceback ends with:

huggingface_hub.errors.GatedRepoError: 403 Client Error.
Cannot access gated repo for url https://huggingface.co/stabilityai/stable-virtual-camera/resolve/main/model.safetensors.
Access to model stabilityai/stable-virtual-camera is restricted and you are not in the authorized list.

Mechanism

The Space loads its weights from the model repo stabilityai/stable-virtual-camera — its own model repo — and that repo is gated. The Space's runtime runs without a token authorized for that repo, so the very first weight download returns 403 and startup dies before the app exists. This is not a code or dependency fault: requirements.txt and the app can be perfect and the Space still cannot start, for anyone, until the access question is settled. Every visitor sees a dead demo for a model they also cannot download without approval.

Fix

Either side of the gate works:

  1. Make the model repo public (or grant the Space's runtime access to it), so the demo can load the weights it exists to show; or
  2. If the weights must stay gated, add a repository secret HF_TOKEN for an account that has been granted access, and have the app pass that token when downloading — and say on the Space card that the demo needs it, so the gated state is a choice rather than a silent failure.

Option 1 matches how the sibling Stability Spaces run and is the one that revives the demo for everyone.

Prove-wrong check

Open the model repo logged out: if model.safetensors downloads without approval, the gate is not the cause. Or restart the Space after granting access: if it still dies at the same 403 on the same URL, this diagnosis is wrong.

Sign up or log in to comment