01-02-2019 04:40 AM - edited 01-02-2019 04:44 AM
Today I've migrated my Cloudekey v1 to a new Cloudkey GEN2.
I'm using a public SSL on the Cloudkey to connect more secure.
When connecting to https://unifi.mydomain.ext I'm logging in on my Cloudkey
When connecting to https://unifi.mydomain.ext:8443 I'm logging in on my controller.
Both works flawless with SSL and the connection is secure.
When I'm logged in to the Cloudkey and click on the button to Launch the Unifi SDN, it tries to connect to the internal IP in stead of the hostname, giving a certificate error (since it connects on IP and not on hostname)
With the Cloudkey v1 the behavior was that it connects to the hostname.
How can I configure the Cloudkey GEN2 to have the same (more secure) behavior ?
I'm using a:
01-02-2019 04:47 AM
You can't change these buttons.
Maybe @UBNT-TomS can add the feature.
USG-XG-8 • USG-4-PRO • USG
USW-XG-16 • USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W 3x • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD 2x • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M • UAP-AC-M-PRO 2x
UAS-XG • UCK-G2-PLUS • UCK-G2 • UCK
01-03-2019 03:20 AM
That's to bad it's not configurable.
Also to bad that the default behaviore is broken in the GEN2 Cloudkey.
in the mean time I'm gonna try to compare the ngix configuration between v1 en GEN2 to see if I can find any hint in why it is not working.
Hopefully @UBNT-TomS can/will add this as a feature to make it configurable or report it as a bug since the default behaviore is broken in GEN2.