-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CERTIFICATE_VERIFY_FAILED #11
Comments
I'm aware of this issue and will be looking at it this afternoon. |
From what i've been able to tell so far, it's not the certificate itself, but having to do with internal api routes being wholly missing. I'm unsure exactly why but it at least appears that the progress bar route is not added when the api is set up using tls now. I don't know yet if it's because of an update to gradio, or one of the more recent updates to the webui relating to CORS. |
Looks like this is the issue gradio-app/gradio#563 |
Yeah I am getting a similar error but @Snazzie were you able to compile your code? I see https in your url. Did you add your certificates in the launch method and run it successfully? |
Ive done nothing except installing this extension via A1111 gui. And next time it launched, this issue occurred. |
Yeah, So I RDP into the machine and worked with the mic. It is working but I dont know what it is reading. It reads "you" for everything I say. |
If you are both trying to use this extension with the latest version, you need to disable it for now until this issue is resolved. There is no way to get it to function as it was before until there is a fix from gradio upstream. Otherwise, you will need to use an older commit of the webui. You can disable the extension without booting the ui by setting the disabled_extensions array to the following in your webui's config.json:
|
Do you happen to know which version is the latest version that will work with your extension? |
@hkpD It should work with: That's from what I last noted in https://github.com/camenduru/sd-webui-extension-records though so it is out of date. It should work with versions a bit newer as well. |
It did not work, but I'm using the DirectML version by lshqqytiger. I'm not sure if that makes any difference but it most likely does. |
@hkpD that fork is currently also using gradio 3.23 so it shouldn't work. |
Thank you for leading me toward the right answer. I found a version that works with your extension for now. |
As far as I can tell you can work around this issue by exporting and trusting the TLS cert as a "Trusted Certificate Authority" on the host OS of the computer you're using to browse to Automatic1111. Once I do that, I no longer get a warning in the browser and similarly the secure WebSocket connection (wss) can be established: I don't think this is really related to gradio app/gradio#563, although it's true that this env var is important for the automatic1111 server calls to its own endpoints. So, if that doesn't work there is another workaround where for now you can manually edit I have tested this on Windows & MacOS so far. |
I was able to do the same thing, but when I went to generate an image, the certificate error came up. This is what I received when I tried your second method for editing the blocks.py file.
|
Ah, my bad - you're right. I must have somehow been running an older version of a dependency or SOMETHING but I started having the same problem. FORTUNATELY it led to finding another workaround: gradio-app/gradio@417004f This disables cert verification for the http client used to make calls back to itself in the queuing module. edit: originally linked to a change in utils.py but that was extraneous. |
YES! Thank you guys so much! It is all working now and I am able to generate output |
The Web-socket thing was a problem on my machine. The |
Idk how fast it'll get merged but I opened a PR to update gradio and add |
@garrettsutula |
I'll cherry pick the commits over into that fork & submit a PR ¯_(ツ)_/¯ |
You should be able to fix this issue now by passing |
Steps:
The text was updated successfully, but these errors were encountered: