Open mmajdanski opened 1 year ago
We should not encourage this kind of unsafe practice, and it is hard to imagine any web site still doesn't have a properly signed cert given there is LetsEncrypt and others free signing services available. Nevertheless, this is not a bug in A1111's but on the host's side.
We should not encourage this kind of unsafe practice,
Why should it be a "unsafe practice" if a fallback/option is implemented for such cases?
and it is hard to imagine any web site still doesn't have a properly signed cert given there is LetsEncrypt and others free signing services available.
It's hard to imagine, why (some) websites should have a certificate, if there is nothing that uses personal data. The brainwash propaganda did it's work, obviously. If there is no (personal) data transfered, then why and what should be encrypted? There are more data stolen from hacks as from "man-in-the-middle" attacks. Just to get this straight.
Nevertheless, this is not a bug in A1111's but on the host's side.
Right, it's not a bug, but it would be a necessary feature to have, as no one from us can change the fact, if the host doesn't react to a request to correct this. But the developer could give us the option to "overwrite" this if needed. Just think about it, what will be faster and have more success: Asking the hoster to change his certificate or implement a switch to temporary use http?
I wouldn't bet much on asking the hoster ...
... just stumbled over this too; having no problem accessing the site from i.e. chrome or vivaldi (via https and on the same system of course); both think the certificate is valid.
it's a dropbox-like site of the university of heidelberg (germany), so i guess they don't need to issue self-signed certs. guess the error message is just some generic type caused by the ssl (or whatever) python module which failed to verify the CA (for whatever reason).
Is there an existing issue for this?
What happened?
[Bug]: Issues downloading LDSR Upscaling Model
There is an issue with Python trying to verify the certificate of the website. The issue seems to be that the SSL certificate on "https://heibox.uni-heidelberg.de/f/578df07c8fc04ffbadf3/?dl=1" is self signed. A good temporary fix we could put in place is download the LDSR upscaling model via http not https so that python does not give us the issue. Otherwise, have a flag for the download that allows for Self-Signed Certs.
Steps to reproduce the problem
What should have happened?
Model should have downloaded properly and not thrown an error
Commit where the problem happens
0cc0ee1b
What platforms do you use to access the UI ?
Windows
What browsers do you use to access the UI ?
Google Chrome
Command Line Arguments
List of extensions
No
Console logs
Additional information
No response