I like to keep stuff local, so I run Home Assistant both locally and do not access it from the internet (other than over a private VPN). I run http.
I’ve had a lot of issues in the last year with certain tools deciding this is bad, and I must use HTTPS, but usually can work around it.
I tried using sqlite web, which used to work (maybe a year ago last used) and now get 404 errors on the first query. I also get a header as below. I have no idea if the 404 is related to the warning (I added the option I think to chrome so I could use the microphone).
Or is sqlite web just broken in some way? Note SQLite Web works fine for the initial display (it shiows version (3.41.2), etc. But when I put a simple query in the query box and hit execute, it switches the 404 above.
Note I have no reason to think the database has a problem, I was just going to clear out a bunch of bogus states from a bad esphome device. Running HA 2023.10.2 supervisor 2023.10.0 os 10.5 on a HyperV VM.
Bottom line - is there some simple way to figure out if this is due to http (vs https), or if this is a sqlite web problem (and maybe a pointer where to go for that if so)?
Linwood
PS. I should also note that ESPHome’s display has started giving an initial “busy” popup and 502 Bad Gateway, a retry then works (and works OK for all functions). ESPHome does not give the above http warning. This may be completely unrelated, but also just recently started. I have 19 ESPHome devices, it started when I added the 19th. It may just be a race condition and unrelated, but thought would mention in case it rings a bell.