I found a scenario where if you happen to hit the login page at just the right time when the controller is starting, you'll end up getting sent to https://<fqdn-or-ip>:<port>/null/login. It would be...

@Fae - bumping this up to see if we can do something similar for port 80 as that was also added and is now blocking the same settings page from being updated.

Unfortunately in version 5.5.6, the user interface also introduced showing the "HTTP Port for Controller Management" setting option. This field has the same issue as port 443 did previously. Could we...

@Fae - awesome, thanks for the guidance!

So which error in specific were you getting? What version of Chromium does the ppa you mentioned install?

I maintain the `mbentley/omada-controller` Docker images and I would like to discontinue support for older versions that TP-Link has stopped supporting as well but I was hoping to get clarification...