Troubleshooting

Most Common Cause

After updating A1111 WebUI, the plugin may break due to changes. Use git checkout to revert A1111 version. Typically, I will try and fix it as soon as possible. However, changes will typically not be backwards compatible, meaning both A1111 WebUI and the plugin has to be updated after the plugin is fixed.

Plugin Docker didn't appear!

As a last resort, Restore Defaults under the Config docker should unhide all dockers and reset them to their default positions.

If none of the plugin's dockers (i.e., Inpaint, SD Plugin Config) are present under Settings > Dockers, follow steps 1 to 4 from Enabling the plugin. Stable Diffusion Plugin will likely be greyed out. Submit an issue with the error message that is shown when hovering over it.

If Stable Diffusion Plugin is not present, ensure you followed Install the plugin closely.

Network Errors

• If using https://github.com/papuSpartan/stable-diffusion-webui-auto-tls-https, do note you have to add the SSL cert to the system store as the plugin does not have a way to trust certs.
  • See: https://github.com/papuSpartan/stable-diffusion-webui-auto-tls-https#but-im-still-getting-certificate-errors--im-getting-warnings
• Not Found is equivalent to 404. Ensure --api is in COMMANDLINE_ARGS. As a sanity check, there should be a section titled "Interpause Backend API" at the bottom of the auto-generated API documentation at http://127.0.0.1:7860/docs.
• invalid JSON response check if you accidentally entered anything into "Optional Encryption Key" under the Config tab. If you intended to do so, check the key is correct.
• response timed out. Be patient.

Others

• If you used the symlink install, do check you didn't rename/move the repository or otherwise cause the symlink to become invalid.
• Are you running the modified backend? Do note the plugin isn't compatible with the backend of other plugins or the incomplete official API.
• Delete krita_diff_plugin.ini and krita_diff_plugin_scripts.ini from %APPDATA%\krita (on Windows) or ~/.config/krita (on Linux) if the plugin is unable to start.
• If the plugin is able to start but doesn't function as expected, try Restore Defaults under the Config tab.