Closed spuder closed 1 month ago
Honestly, for years I've always used the controller with https, the only "problem" being the warning each time I visited the webpage. If that is the problem you are complaining about, check out this video: https://www.youtube.com/watch?v=qlcVx-k-02E I tried it out sometime ago with success, quick and easy.
Keep me posted.
Thanks for the response. I'm finding that clicking past the https warnings isn't an option.
use the "https" prefix, not "http". It should only complain about the certificate
Closing for inactivity
As a user who setup the 'generic' compose file with portainer, I discovered that it requires https connectivity.
There does not appear to be a way to bypass https.
Workaround
One user has discovered that there is a way to use caddy as a proxy
https://community.ui.com/questions/What-is-the-HTTP-port-for-the-web-interface-of-the-unifi-controller/45be0099-59aa-4e60-bbeb-fd1a89a9b9cc#answer/43044288-8238-47bd-b39e-2154dac08aa5
Resolution
Is https actually required? If so it would be helpful to mention that in the documentation, or provide a caddy/nginx proxy to bypass that requirement.