|
To truly do away with the warning, you'd need: 1) a wildcard cert (say, "*.cpe.pcswin.com") 2) that cert installed on every CPE 3) a DNS record for every CPE management IP (i.e. "10-2-3-100.cpe.pcswin.com") 4) always access the CPE using the DNS record If you access the CPE via IP directly even with the above cert on it, the browser will still throw the cert warning because the FQDN you went to (which was just the IP) doesn't match the host name on the cert, which would be "*.cpe.pcswin.com". Jesse DuPont Network
Architect Celerity
Broadband LLC Like us! facebook.com/celeritybroadband On 2/3/17 8:04 AM, Steve Barnes wrote:
Having several thousand UBNT devices that use HTTPS, is there any way to get around the: Your Connection is not private, then clicking advanced and then Proceed to 10.0.0.1 (unsafe).Some I have turned the HTTPS off but would like the extra security when doing updates and the like. I have 6 techs and 10 systems that access all these and wanted to know if there was a work around. Steve Barnes Wireless Operations Manager New Lisbon Broadband NLBC.COM PCSWIN.COM 765-584-2288 ext:1101 |
_______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
