Closed JustNeutral0 closed 1 year ago
so i'm actually kind of wondering if you're running into something like the issue i just opened upstream
It was actually something about a reference being undefined in the dream script, ill try and get an error code when i get home
so i'm actually kind of wondering if you're running into something like the issue i just opened upstream
Sorry about that
lmao no worries at all, your report got me to check on what might be happening and ran into something undesirable in the meantime, so, uh thanks either way? :D
Thats all i got with mobile, what im using to bring up the console wont let me get more details
Does it with any of the tools just about
some more details
i'm still pretty sure it's going to be happening in webUI as there's really nothing in openOutpaint that could even return a 500 unless you're running it standalone and something's really wrong with python's webserver...
Go to [local API docs](http://127.0.0.1:7860/docs)
Scroll down to POST sdapi/v1/txt2img, open it, click "try it out"
Paste the following into the input field
{ "batch_size": 1, "cfg_scale": 7, "enable_hr": false, "height": 512, "n_iter": 1, "negative_prompt": "test", "prompt": "test", "restore_faces": false, "sampler_index": "DDIM", "seed": "1", "steps": 1, "width": 512 }
- could you possibly supply the content of the POST request parameters and response from your browser's network tab?
![image](https://user-images.githubusercontent.com/1649724/225773631-a1706683-e815-44d3-982c-6c296e0bdae4.png)
![image](https://user-images.githubusercontent.com/1649724/225773720-5d61a1a3-ae70-480b-8d8c-cf72db67c603.png)
Will do when i get home later
is that what you needed?
almost - was hoping for the content of the payload tab in the first image but that should'nt be any different than what was passed through the API input field... unfortunately your results seem to confirm what i was thinking - looks like you've got something that's causing an issue with webUI and its API deeper than openOutpaint :(
not sure what A1111 extensions (etc) you've got going (and i might need to ask that in the issue template) but the easiest way to test that everything's working as expected from the very bottom would be to simply install a second "clean" copy of webUI to a different directory, enable the --api
flag on that and ensure that the txt2img API request returns a base64 image string and a status of 200
will be closing this as it's occurring in webUI; please reopen if the issue can be reproduced after confirming base webUI API functionality :)
...just out of curiosity, does it happen if you use http://127.0.0.1:7860 instead of http://localhost:7860 ?
I use --listen, but i haven't tried it with 127.0.0.1:7860, will attempt when i get home
What happened?
ran openOutpaint with newest version of webui, all tools report 500 internal server errors
Steps to reproduce the problem
What should have happened?
ran properly
Commit where the problem happens
latest
What platforms do you use to access openOutpaint?
Windows
What browsers do you use to access the UI ?
Google Chrome, Other (please list in additional information)
Browser Extensions/Addons
adblock and better ttv (twitch addon)
AUTOMATIC1111 webUI Commandline Arguments
--theme dark --xformers --medvram --listen --enable-insecure-extension-access --always-batch-cond-uncond --api --cors-allow-origins=http://localhost:3456
Additional information
using opera gx browser, same issue happens with chrome