-
Notifications
You must be signed in to change notification settings - Fork 136
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
OpenSSL doesn't work in Firefox and Safari #341
Comments
+1 |
Here webui start the web server: Line 6770 This issue is related to how browser deals with TLS, I mean it's not really a webui issue. Running a public web server with a self signed certificate will get the exact same error/warning. |
Are you sure? I'm not an expert on civetweb but according to this issue (particularly the last comment) civetweb does support (and reccomend) it since 2015. Of yourse 2015 was 9 years ago however i don't know why they would remove support for something like this. In this issue too it seems to be possible and while here it didn't work finally this doesn't seem to be related to civetweb directly. |
True, it seems civetweb supports it... |
Isn't ChatGPT just a spellchecker 🤔? |
All non-chromium based Browsers we tested will not connect to a secure websocket when using a self-signed certificate.
using a non-self-signed certificate wouldn't be practical with webui. The problem seems to be that every non-chromium based browser doesn't accept wss connections to a diferent port than the website if the certificate of the websocket is self-signed.
Would it be possible to run the websocket on the same port as the built-in webserver? While most users will use a Chromium based browser, some will not and Safari and Firefox together do make up a significant portion of users.
This seems to be a known issue, at least for firefox.
Edit: An additional complication seems to be that WebUI will consider the website inaccessible if this occurs and show the "Access Denied, already running in another browser" when reloading the page, this will be shown until a successfull websocket connection is made from another browser
The text was updated successfully, but these errors were encountered: