stable-diffusion-webui
stable-diffusion-webui copied to clipboard
[Bug]: UI is broken after recent commits
Is there an existing issue for this?
- [X] I have searched the existing issues and checked the recent builds/commits
What happened?
WebUI doesn't work, errors in browser console:
Uncaught DOMException: Failed to execute 'appendChild' on 'Node': Only one element on document allowed.
at HTMLDocument.<anonymous> (https://my-domain.cc/file=/home/default/data/app/stablediffusion/javascript/imageviewer.js?1679728964.6552258:272:17)
Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'. TypeError: Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.
at generationParams.js?1679568324.2952483:13:17
at runCallback (script.js?1679728964.6592262:38:9)
at script.js?1679728964.6592262:44:31
at Array.forEach (<anonymous>)
at executeCallbacks (script.js?1679728964.6592262:44:11)
at MutationObserver.<anonymous> (script.js?1679728964.6592262:56:9)
Steps to reproduce the problem
- Git pull
- Run webui.sh
What should have happened?
\\
Commit where the problem happens
https://github.com/AUTOMATIC1111/stable-diffusion-webui/commit/275834ca9702377747aba5d81badf7053d0eb4d6
What platforms do you use to access the UI ?
Linux
What browsers do you use to access the UI ?
Google Chrome
Command Line Arguments
No
List of extensions
ControlNet, Dreambooth
Console logs
No errors in the app console
Additional information
Debian 11, the app is behind NGINX reverse proxy
I'd suggest to roll back master to something stable and continue in a separate branch if possible, please
I'd suggest to roll back master to something stable and continue in a separate branch if possible, please
how do you do that using git, and how do you go back to the main branch afterwards?
I mean, my suggestion is for the author of the repo @AUTOMATIC1111 since the master is unstable.
seems to be sorted now for me. quick work fellas!
generate forever right click still seems broken
generate forever right click still seems broken
Open browser dev tools console please. Are there any errors?
generate forever right click still seems broken
Open browser dev tools console please. Are there any errors?
yeah few errors for a couple of the extensions including animator, dynamic prompting and generationParams
- When I press the Generate button, nothing happens
- The word (token) counter, which is next to the Generate button, always shows "0/75", even though a long prompt is entered.
- The browser console gives errors:
script.js?1679734144.3962412:5
Uncaught (in promise) RangeError: Maximum call stack size exceeded at elem.getElementById (script.js?1679734144.3962412:5:41) at elem.getElementById (script.js?1679734144.3962412:5:57) at elem.getElementById (script.js?1679734144.3962412:5:57) at elem.getElementById (script.js?1679734144.3962412:5:57) at elem.getElementById (script.js?1679734144.3962412:5:57) at elem.getElementById (script.js?1679734144.3962412:5:57) at elem.getElementById (script.js?1679734144.3962412:5:57) at elem.getElementById (script.js?1679734144.3962412:5:57) at elem.getElementById (script.js?1679734144.3962412:5:57) at elem.getElementById (script.js?1679734144.3962412:5:57)
Same issue for me… The generate button does not respond, the words are not displayed in the counter, and the same errors in the browser (chrome)
Yep, I can't use it as well. Generate button doesn't work, updating addons doesn't work either. Lot's of console errors in the browser.
EDIT: Deactivating stable-diffusion-webui-images-browser extension at least makes updating and generating work again. Still some errors in the console (animator) and still problems like that the sampler dropdown shows "Euler a Euler a" till you click and CSS padding errors in the accordion elements for addons, even if animator extension is deactivated as well.
Yep, I can't use it as well. Generate button doesn't work, updating addons doesn't work either. Lot's of console errors in the browser.
EDIT: Deactivating stable-diffusion-webui-images-browser extension at least makes updating and generating work again. Still some errors in the console (animator) and still problems like that the sampler dropdown shows "Euler a Euler a" till you click and CSS padding errors in the accordion elements for addons, even if animator extension is deactivated as well.
Yeah, that’s work! Thanks!
Upgrading the extensions manually for their respective folders using git pull worked for me.
Upgrading the extensions manually for their respective folders using git pull worked for me.
Upgrading the extensions indeed fixes most of the issues, including ‘generate’, but the image-browser still seems to be broken. I will wait for an update for the extension.
Settings tab and checkpoint dropdown box is broken
Edit: I disabled some extensions and it seems to be fixed.
Same here, UI crashed after this commit.
Error loading script: main.py Traceback (most recent call last): File "C:\Users\sings\Documents\AI-Graphics\stable-diffusion-webui\modules\scripts.py", line 256, in load_scripts script_module = script_loading.load_module(scriptfile.path) File "C:\Users\sings\Documents\AI-Graphics\stable-diffusion-webui\modules\script_loading.py", line 11, in load_module module_spec.loader.exec_module(module) File "
", line 883, in exec_module File " ", line 241, in _call_with_frames_removed File "C:\Users\sings\Documents\AI-Graphics\stable-diffusion-webui\extensions\a1111-sd-webui-locon-main\scripts\main.py", line 10, in import lora ModuleNotFoundError: No module named 'lora'
No any actions can be taken inside the UI, including image browser and extensions update check.
Error still presents in imageviewer.js
posex doesn't work today without posex itself changing. I suspect the changes in the last 24 hours. Opening up the 'Posex' thing and clicking send to control net no longer opens up the pose editor. If I revert the set of changes that dropped in the last day it works. Is it "THIS" bug that covers the issue or should I enter one?
Quicksettings/settings page failing to load is caused by https://github.com/AlUlkesh/stable-diffusion-webui-images-browser/issues/96, update to latest version
Bugs as hell today after updated.
"ModuleNotFoundError: No module named 'lora' " in webui-user.dat
same here, getting error from lora module missing
same here, getting error from lora module missing
Actually let me take this back, after updating extensions and reboot the webui, it works fine.
Still doesn't work for me, even after manually updating all extensions. Reverted to 64b7e838 and it works fine again.
Still doesn't work for me, even after manually updating all extensions. Reverted to 64b7e83 and it works fine again.
I did too, got a usable UI back again. Here's what I did from the webui directory.
git reset --hard 64b7e83
Make sure you remove git pull out of your batch script if you normally have it update on startup, otherwise you're gonna get the broken UI right back again.
UI after updating, is a lot slow and too many JS errors:
https://i.imgur.com/cnBTYWz.png
UI after updating, is a lot slow and too many JS errors:
https://i.imgur.com/cnBTYWz.png
still doesn't work, still running 64b7e83. I've pulled to present just now, and get console full of errors and nothing works.
Edit: i also individually updated all plugins via git pull. still very broken.
After finally having time to do some poking around, it looks like my particular situation was using an nginx reverse proxy as the frontend. I had to add the following to the location / {}
block to get things working properly, due to the new UI changes using web sockets (wss protocol), and those not being forwarded through properly.
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;```
any progress?
I had similar problem - solved it by:
- disabling all custom extensions,
- restarting,
- (if after restart there are still errors - that's a problem, idk then),
- Update and enable extensions,
- At this point everything worked for me.
If there weren't any errors at step 3 but there are errors at step 5 - try to find which extension causes problems by disabling them one by one.
Newer versions have fixed this. Open a new issue if the problem persists as of the latest version.