I can understand the inconvenience.
If you use the ip address, you shoud not have the problem, but if you use a fqdn over https, you will have the problem, because it does not resolve to the internal built-in default certificate of the controller. If you have your own CA you can deploy an SSL certificate for the controller with its specific fqdn and your problem will go away https://arubanetworkskb.secure.force.com/pkb/articles/HowTo/R-55
If you think this should work, even with the built-in default certificate, please open a case with our ideas portal on the support site, so that we can track this issue.