stable-diffusion-webui
stable-diffusion-webui copied to clipboard
AUTOMATIC1111
[Bug]: Img2Img and Inpaint have stopped working
Is there an existing issue for this?
- [X] I have searched the existing issues and checked the recent builds/commits
What happened?
Everything in the img2img tab has stopped working (txt2img works perfectly).
Img2img and inpaint are the main 2 things I use, I can upload an image into these parts but the moment I enter my prompt/settings and click generate nothing happens. I wait and wait but no image is generated and no error messages are shown in automatic1111 or the terminal.
Steps to reproduce the problem
- Upload an image to img2img or inpaint.
- Add a prompt/negative and some settings.
- Add a mask if you're using inpaint.
- Click the generate button.
- Nothing happens, no new image appears even after waiting 10 minutes. No error messages appear either.
What should have happened?
I follow the above steps and once I click generate a new image appears, typically in 10-20 seconds as I have a fast GPU. This is what was happening up until Monday when the problem began.
Commit where the problem happens
0cc0ee1b
What platforms do you use to access the UI ?
Other/Cloud
What browsers do you use to access the UI ?
Google Chrome, Microsoft Edge
Command Line Arguments
I've added --xformers to COMMANDLINE_ARGS=
List of extensions
No.
Console logs
There's nothing to see here otherwise I would do this. The terminal only shows something if I use txt2img because that still works fine for me. Once I try using img2img or inpaint nothing happens and the terminal is completely dormant as if I'm not using stable diffusion/auto1111 at all.
Additional information
I'm pretty sure this issue is only affecting people who use notebooks (colab/paperspace) to run Stable Diffusion. I personally use paperspace and this notebook to run it. I've opened a bug report over there which can be found here.
Fixes I've tried so far:
Using different models to rule out any issues with a particular one. Fresh install of Stable Diffusion. Reverting to an older commit. Working in the Microsoft Edge browser instead of Chrome.
None of these things helped.
can confirm, inpainting broke very recently. google did just update their python version on collab to 3.9 but fastben released a fix to the notebook there and it was working -for a little bit-. I could see in the network tab that the response to /internal/progress call in the background was the Gradio "No interface is running right now" page - even though the automatic ui would load with a normal visit to the gradio url.
would love to get inpainting back !
can confirm, inpainting broke very recently. google did just update their python version on collab to 3.9 but fastben released a fix to the notebook there and it was working -for a little bit-. I could see in the network tab that the response to /internal/progress call in the background was the Gradio "No interface is running right now" page - even though the automatic ui would load with a normal visit to the gradio url.
would love to get inpainting back !
Yeah, I spoke to someone else suffering this problem and they thought it was to do with Python as well. Inpainting is the main thing I use so I'm desperate for this to be fixed.
Same here on a Ubuntu machine , I can't even load an image into the img2img tab, it just doesn't do anything and when trying to send it to img2img or inpaint from the image browser , red 'error' message apperss in the UI.
Same here on a Ubuntu machine , I can't even load an image into the img2img tab, it just doesn't do anything and when trying to send it to img2img or inpaint from the image browser , red 'error' message apperss in the UI.
Yeah, I've started to have trouble even loading images into the img2img tab too, not that it makes much difference when it doesn't work. Red error messages are becoming more frequent.
OK, I updated my Python to 3.10 and that seems to have fixed the problem (only tested for a few minutes but everything was working perfectly).
OK, I updated my Python to 3.10 and that seems to have fixed the problem (only tested for a few minutes but everything was working perfectly).
Tried it again today, worked for 15 minutes before breaking again so you can probably ignore this comment.
im using colab and same problem, anyone know how to fix?
Yeah, it seems to only be a problem for people running SD through notebooks. I've seen multiple colab and paperspace users report this issue but the wider SD community (people using it through their own PC's) don't seem to have a problem. There's no mention of it on the biggest discord servers/subreddits and I imagine if inpainting/img2img had broken for everyone it would be huge news by now.
An issue for colab was opened yesterday if you want to follow.
OK, I tried going back to an older auto1111 commit from the 2nd of March and that seems to have fixed the issue, I've just spent the last 90 minutes inpainting with absolutely no problems. For anyone who wants to try this, the commit I used was: fc3063d9b924c094b59229269f4afe722b120d88
OK, I tried going back to an older auto1111 commit from the 2nd of March and that seems to have fixed the issue, I've just spent the last 90 minutes inpainting with absolutely no problems. For anyone who wants to try this, the commit I used was: [fc3063d]
Thank you so much! It works now
OK, I tried going back to an older auto1111 commit from the 2nd of March and that seems to have fixed the issue, I've just spent the last 90 minutes inpainting with absolutely no problems. For anyone who wants to try this, the commit I used was: fc3063d
Update: Now this older commit isn't working for me! I'm starting to go insane trying to fix this damn problem. I guess I'll try a different commit but I don't hold out much hope.
Update: Now this older commit isn't working for me! I'm starting to go insane trying to fix this damn problem. I guess I'll try a different commit but I don't hold out much hope.
Can confirm, it stoped working again even with the old commit, if you find another way please share, this is really annoying
not for me It's still working for me, since yesterday, maybe try both the old commit and that checkbox
For me both img2img and inpainting are not working at the moment. I can send a generation to inpainting, mask the area, but when I hit generate it does nothing.
Checking "use_localtunnel" seems to solve the issue
This is what I've found too. Basically Gradio is the problem. Since switching to something different I've had zero problems.
If you use colab this notebook has multiple Gradio alternatives.
The colab notebook from TheLastBen has a box you can tick to use "localtunnel" instead of Gradio.
I also think ngrok is allowed on colab so you could switch to that. It's pretty simple, here's a tutorial.
As for anyone using paperspace, that's a little tougher. They ban you for using ngrok and pretty much any other proxy tunnel. This guide is your best bet but it's pretty complicated.
Has this issue been resolved? The convo dropped off last month. I'm still having this issue. Have not tried any of the above suggestions as most / all have shown to have not fixed the problem.
Has this issue been resolved? The convo dropped off last month. I'm still having this issue. Have not tried any of the above suggestions as most / all have shown to have not fixed the problem.
Since switching from Gradio everything has continued to work superbly for me.
Make sure to check your log in your shell for the exact failure. What the issue for me was was that I was using the wrong image file type. Apparently, Img2Img only uses TIFF files. So try converting your image type to TIFF and see if that works.
Thanks! This seems to be the issue. It won’t allow tiff but I got it working with jpg. Will try some other formats to see what all works. Maybe tif. It is great to be back at it so thank you again.
Sent from Yahoo Mail for iPhone
On Saturday, May 6, 2023, 12:50 PM, hossamantarkorin @.***> wrote:
Make sure to check your log in your shell for the exact failure. What the issue for me was was that I was using the wrong image file type. Apparently, Img2Img only uses TIFF files. So try converting your image type to TIFF and see if that works.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
