search

AUTOMATIC1111 / stable-diffusion-webui

Stable Diffusion web UI
GNU Affero General Public License v3.0
140.93k stars 26.66k forks source link

No Longer Working in Browser #803

Closed coldphone closed 2 years ago

coldphone commented 2 years ago

Hi, all. I'm very new to this so sorry in advance if this is something dumb.

Earlier today, I set up Stable Diffusion using this guide: https://www.howtogeek.com/830179/how-to-run-stable-diffusion-on-your-pc-to-generate-ai-images/

However, I started looking for a GUI version and came upon this great project. I set it up using the guide here: https://stablediffusionguides.carrd.co/#one

I'll note that both of these installs/folder locations are separate. This GUI version seemed to install fine and I opened it in my browser and was poking around in it. I left it open for a little while and decided to try a prompt -- I got a generic error message and when I reloaded the page, I could no longer connect (used both http://127.0.0.1:7860/ and http://localhost:7860/). The other cmd-based one is still working fine. Is there anything I should be checking to get the WebUI working again?

kiancn commented 2 years ago

have you tried running webui-user.bat again? You need to run that bat file every time you have done a system restart or closed the terminal window that launces when you run webui-user.bat (because the server started by gradio shuts down). One proper way to terminate the server that starts on your computer when you run webui-user.bat is to have the terminal window in focus and press ctrl+c one or more times (a single time can sometimes be used to get the app 'unstuck'), and then read the cmd-line.

coldphone commented 2 years ago

have you tried running webui-user.bat again? You need to run that bat file every time you have done a system restart or closed the terminal window that launces when you run webui-user.bat (because the server started by gradio shuts down). One proper way to terminate the server that starts on your computer when you run webui-user.bat is to have the terminal window in focus and press ctrl+c one or more times (a single time can sometimes be used to get the app 'unstuck'), and then read the cmd-line.

That did it, thank you!