search

Aircoookie / WLED-App

Mobile app for controlling and discovering WLED lights
MIT License
312 stars 77 forks source link

Support for HTTPS endpoints & Basic Auth #14

Open anoff opened 3 years ago

anoff commented 3 years ago

Hey 🍪,

is there any way to address WLED endpoints from the (Android) app using https?

I want to expose my endpoints to the internet - at least for some time to play around. But for some basic security I want to rum them behind a reverse proxy with basic auth + SSL encryption. The app seems to always prepend http:// to the entered hostname, so I end up with http://https://user:password@host as an entry, leading to a broken URL and no connection at all. Basic Auth works using [http://]user:password@host at least for discovering the WLED but opening the panel of the individual endpoint there are several connection errors, probably caused by this one

TypeError: Failed to execute 'fetch' on 'Window':
Request cannot be constructed from a URL that includes credentials: /json/si

Amazing work on the WLED ecosystem, greetings from 🇯🇵

kirktindel commented 2 years ago

I just wanted to plus-one this. I don't care so much about encryption, HTTPS and I don't even mind cert errors. I just want WLED to be able to operate on a different IP port than port 80 (unencrypted HTTP).

I've spent many hours looking up the subject and haven't found anything that seems pertinent, aside from requests for this. Hopefully if enough of us keep asking for https, they'll include it (and, hopefully for me, the ability to use port 443)

Dr-Bix commented 2 years ago

What about fronting the ESP32 with a Raspberry Pi (or some other web server) and reverse proxying the HTTPS requests to the ESP32/WLED? Nginx is apparently rather simple to configure for this. Would the Mobile App support this?