04-15-2018 11:52 AM
i have issue with rediscovering devices - not sure how many but quite lot devices changes properties to port 80 even if https is enabled for all of them. when i click link with IP address to connect to the device it fails because it begins with https and port is set to 80
is there kind of workaround to fix this or after every discovery i need to update also properies for all devices to make sure that port 443 is used?
i'm using aircontrol 2.1 via webgui
04-16-2018 05:54 AM
can you confirm that HTTP port changes after running discovery? I can't reproduce this by running discovery. I will try investigating this further.
04-16-2018 09:31 AM
Im using HTTPS where i can so im not sure if and how i can confirm question regarding HTTP... i can provide you any output from device ... but im not sure what can help ... maybe just note: i was playing with different ports configured via mass configuration in the past but im not sure how device preferences are loaded. whether is listed information loaded just somehow from device or this can be influenced by aircontrol database
04-16-2018 11:59 AM
but Device properties in AC2 are not influenced by that.... doing so would break any link to radios behind NATs.
Radio via WebGUI https 443 with LAN IP
Radio in AC2 with any custom port and FQDN accessible via NAT. (provided in device properties)
We all work for KUDOs here.
04-16-2018 01:00 PM
i can confirm just HTTPS port change after discovery because HTTPS is ticked in properties (for all of devices). just HTTP(s) port is different after discovery.