Troubleshooting

Troubleshooting

"Render failed" and no picture

Open Agents — the reason is reported there, and the failure panel on Generate names it too.

The common causes:

• Out of memory. A 1024×1024 SDXL render wants 10–11 GB. Use a smaller shape, fewer steps, or SD-Turbo at 512px. Compute tells you whether a job fits before you start it.
• The engine is not installed. System → install it.

The first render takes forever

The model is loading into the graphics card, which happens once per session per model. Later renders are much faster. Switching models pays it again.

Rating or comparing says nothing was recorded

History logging is off by default (System → Settings). While it is off, renders are not recorded, so there is nothing to rate. Turn it on; renders made after that can be rated.

Training finished but there is no adapter

ImageForge does not include the trainer. If kohya sd-scripts is not installed in ~/sd-scripts, a run writes its configuration and stops, and says so. See Training a LoRA.

HuggingFace search finds nothing

If it reports it could not reach HuggingFace, check your connection. Note that gated models need a token — see System and licences.

An agent cannot connect

• The configuration only fills in after the engine is installed — before that the API screen says so.
• Paths outside ImageForge's own folders are refused by design. Set IMAGEFORGE_IMAGE_DIRS to allow a folder of your own. See Agents and the API.

Windows blocks the installer

ImageForge is not code-signed. More info → Run anyway, or verify the SHA-256 against the release first. See Installing.

Renders are extremely slow

You are probably on the processor build. System reports the graphics card and which engine build is installed. Without a supported NVIDIA card, minutes per render is expected.