Troubleshooting

Fixes for the banners and errors you're most likely to see.

This Runpod machine’s GPU isn’t working

A red banner with this message means the GPU on the machine Runpod gave you can’t be used. It happens now and then on Community Cloud machines, and nothing inside the pod can fix it.

Fix: in the Runpod console, terminate the pod and deploy the template again. You’ll land on a different machine. If you already made work on this pod, back it up first. Deploying on Secure Cloud almost always avoids this.

This pod has no storage volume attached

The pod was deployed without a volume, so the models and your projects have nowhere to live.

Fix: terminate the pod and deploy again. On Runpod’s deploy page, click Add volume before Deploy Pod. The banner shows how much space your preset needs.

Downloading models

The amber banner at the top shows models still downloading after the first boot. Features unlock as their models arrive. Until then their Generate button is disabled, and hovering over it shows Model files still downloading.

On an RTX 4090, images are usually ready in about 3 minutes and everything else in 6–18 minutes. Check progress any time under Settings → Models.

A model download is waiting for a Hugging Face token

Some optional models, such as LTX-2.5, are gated: you have to accept their terms on Hugging Face before you can download them.

Fix: accept the terms on the model’s Hugging Face page. Then, under Settings → Models, paste a Hugging Face read token from that same account into the field under the download and click Save. The download starts within about 15 seconds.

A mode or page is missing

The studio hides features your pod has no models for. For example, the Video preset has no Edit, Angles or Perform, and the Perform preset has no Projects or Locations.

Fix: check Settings → Models. Groups marked Not enabled weren’t part of your preset. To get everything, deploy the Full studio preset from blockbuster.studio.

Setup is locked

A new studio can only be claimed in the first 15 minutes after the pod starts. If nobody created a password in that time, setup locks.

Fix: do one of these:

• Restart the pod from the Runpod console. Setup reopens for another 15 minutes.
• Click Edit Pod in Runpod and set STUDIO_PASSWORD to the password you want, ideally as a Runpod Secret.

Your models and films are kept either way.

I forgot my password

In the Runpod console, click Edit Pod and set STUDIO_PASSWORD to a new password. Saving restarts the pod, and the new password replaces the old one. Use a Runpod Secret so the password isn’t shown in plain text in the console.

After 10 sign-in attempts in a minute, the studio stops checking passwords for up to a minute, and the login screen keeps saying Incorrect password even when the password is right. Wait a minute before trying again.

Break down with AI is missing

Script breakdown needs an AI model. Connect one in Settings. Until you do, you can still build a film by hand.

A job failed

Open the Queue at the top right. Failed jobs show their error, and you can click Retry.

Storage is almost full

When less than 3 GB of storage is free, the studio refuses new jobs with The pod’s storage is almost full.

Fix: back up what you want to keep, then delete old images and videos from the gallery. If you keep running out, deploy a new pod with a larger volume.

A Civitai LoRA won’t import

Some Civitai files, including all NSFW ones, need a Civitai token. Add one under Settings → Download tokens.

Still stuck?

Open an issue on GitHub with what you were doing and the exact message you saw.