Troubleshooting Common Issues

If you're having issues with SD.Next, please follow these steps designed to help weed out known issues first.
All users should do Steps #1 and #2 regardless of having a problem or not.

1. CLI Arguments

You should familiarize yourself with all available CLI arguments by typing webui.bat (or .sh) --help, which
will present a full list of them to you. There are likely options you have at your disposal that you are unaware of.

2. UI Config

If your ui-config.json file is larger than a few KB (1–20 KB is normal), delete it.

The file now saves only the differences from SD.Next's defaults rather than the full configuration. Stale entries from older versions can override new defaults and cause issues, including non-functional buttons.

3. Config

Often many issues are cleared up by simply deleting the config.json file and letting SD.Next generate a new one. However
this is destructive and annoying because you have to set all of your personal preferences again, including model/image paths.
Instead we recommend simply renaming config.json to config-backup.json. This way the system will generate a new file when
you restart SD.Next, while also preserving your paths and settings. You can always use --config config-backup.json to start
SD.Next back up with your previous settings, or undo the rename entirely if it did not help.

4. Use Debug Mode

If you're encountering errors, unexpected terminations, or other issues, start SD.Next with the --debug argument. This provides more detailed log output, which often exposes the root cause. Running with --debug at all times is generally recommended, though some users prefer to omit it to reduce log verbosity.

5. Safe Mode

Unless the issues you are having are directly involving an extension, it can be helpful to take all non-essential extensions
out of the equation (disabling them) for troubleshooting purposes. Therefore we advise starting up with the --safe argument
to see if any non-essential extensions are causing the issue at hand.