Community Solution

Stable Diffusion Won't Launch from ZimaOS Dashboard: Fixes

After updating from ZimaOS 1.5.2 to 1.5.3, Stable Diffusion still worked by direct IP and port but failed from the dashboard launch link.

If Stable Diffusion opens correctly at http://ZIMA-IP:7860 but fails when launched from the ZimaOS dashboard, the AI app itself is probably running—the broken layer is the dashboard Web URL or browser launch path. Do not reinstall models or GPU drivers until you prove the container is actually failing.

The source case appeared after ZimaOS 1.5.3 and disappeared when the user reverted to 1.5.2. Today, ZimaOS is far beyond that release and Stable Diffusion remains in the App Store, so the correct 2026 guidance is to update to current stable ZimaOS and troubleshoot launch URL, browser filtering, container health, and GPU compatibility separately.

Step 1: Open the App by Direct IP and Port

The current ZimaOS Stable Diffusion package uses WebUI port 7860. Test:

http://YOUR-ZIMA-IP:7860

If AUTOMATIC1111 opens and can generate an image, the container and web server are alive.

Step 2: Check the App's Web URL in ZimaOS

Open the app settings and inspect the Web URL/port mapping. Current ZimaOS releases improved Docker Web URL handling and port configuration, so an old 1.5.3 dashboard-link bug should not be treated as a current permanent defect.

Step 3: Disable Browser Filtering for the Local Dashboard

A community reply in the original thread reported broken app-launch URLs in Brave until ad/tracker blocking was disabled for the ZimaOS dashboard.

Test a clean browser profile or private window. If direct IP works but only one browser's dashboard click fails, the browser is part of the problem.

Step 4: Confirm the Current App Container Is Running

docker ps
docker logs --tail 100 <stable-diffusion-container>

Look for a healthy WebUI startup rather than relying on the dashboard icon state.

Stable Diffusion Is Still a Current ZimaOS App

The current Stable Diffusion App Store page lists Stable Diffusion as an active AI application.

Do Not Confuse Dashboard Launch Problems with GPU Compatibility

In 2026, RTX 50-series users documented a different failure: ZimaOS could see the GPU, but the Stable Diffusion container's older PyTorch/CUDA stack did not support the new GPU architecture. That produces CUDA/kernel errors inside the app—not merely a dashboard link that points to the wrong URL.

The Stable Diffusion hardware guide covers that GPU-specific branch.

When to Reinstall the App

Reinstall only after you have checked the launch URL, container logs, browser behavior, and persistent model/output folders. If the app's configuration volume is persistent, reinstalling the container should not require redownloading every model—but verify paths before removal.

Do Not Revert to 1.5.2 Today

The rollback described by the source user was useful evidence in December 2025. It is not a current recommendation. Newer ZimaOS releases contain security, storage, memory, backup, and Docker fixes that did not exist in 1.5.x.

Check Whether the Dashboard URL Uses the Correct Scheme

A dashboard shortcut can fail if it generates HTTPS for a service that only listens on HTTP, or if it points to an old port after the app configuration changed. Compare the exact working direct URL with the Web URL saved in ZimaOS.

Preserve Models and Outputs Before Reinstalling

Stable Diffusion installations can accumulate many gigabytes of checkpoints, VAEs, LoRAs, extensions, and generated images. Before reinstalling, inspect the mapped host volumes and confirm those folders are outside the disposable container layer.

If the model/output paths are persistent, you can recreate the app without treating the container as the only copy of your AI assets.

Use Logs to Distinguish WebUI Failure from CUDA Failure

A healthy WebUI typically logs that it is listening on port 7860. CUDA architecture errors, missing kernels, or out-of-memory failures point to GPU/runtime compatibility instead. That distinction determines whether you should fix a URL or replace/update the container stack.

FAQ

Why does direct IP:7860 work but the dashboard button does not?

That points to the dashboard's generated Web URL, browser filtering, or frontend state rather than the Stable Diffusion web server itself.

Should I reinstall NVIDIA drivers?

Not if the app works through the direct URL. Driver problems usually prevent GPU execution inside Stable Diffusion, not only dashboard navigation.

Can Brave block ZimaOS app launch links?

A community user reported exactly that behavior. Test with shields/content blocking disabled for the local ZimaOS dashboard.

Is ZimaOS 1.5.3 still relevant?

Only as historical evidence. Update to the current stable release instead of reproducing a 2025 rollback.