You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ ws --https
Serving at https://Boreks-MacBook-Pro.local:8000, https://127.0.0.1:8000, https://192.168.1.163:8000
From this, I randomly chosen the last URL given only to encounter the "Your connection is not secure" issue in Chrome. I thought I've got my certificate misconfigured but then I noticed this in the imported lws certificate in macOS Keychain Access:
So I tried the 127.0.0.1 address and it worked, as well as localhost. (It still didn't work in Firefox but maybe they handle certificates differently, I don't know, I care mostly about Chrome.)
So maybe with HTTPS, only the first two links should be given? Or could the certificate be updated to work with the specific IP URL as well?
(Additional piece of feedback: for my purposes, I'd be more than happy with a single URL; receiving multiple doesn't make much sense in my scenarios. I guess that's for remote access via network but I never tried that; if that's not very common, maybe it could be hidden behind a flag to make the UX cleaner.)
The text was updated successfully, but these errors were encountered:
Regarding the last address (https://192.168.1.163:8000) not being covered by the default lws certificate, there's not much I can do about that. The 192.168.x.x IP will be different for every user so I can't create a standardised lws cert which covers every IP permutation (unless you know a way, in which case please share).
When I run
ws
, I get this message:From this, I randomly chosen the last URL given only to encounter the "Your connection is not secure" issue in Chrome. I thought I've got my certificate misconfigured but then I noticed this in the imported
lws
certificate in macOS Keychain Access:So I tried the
127.0.0.1
address and it worked, as well aslocalhost
. (It still didn't work in Firefox but maybe they handle certificates differently, I don't know, I care mostly about Chrome.)So maybe with HTTPS, only the first two links should be given? Or could the certificate be updated to work with the specific IP URL as well?
(Additional piece of feedback: for my purposes, I'd be more than happy with a single URL; receiving multiple doesn't make much sense in my scenarios. I guess that's for remote access via network but I never tried that; if that's not very common, maybe it could be hidden behind a flag to make the UX cleaner.)
The text was updated successfully, but these errors were encountered: