Jason Madden

Thanks for the history! I've never used PG2, so I was unaware that it had coopted those ports. That said, there's nothing listening on the standard ports out of the box, so that shouldn't be an issue: # lsof -i -n -P | grep LISTEN sshd 1666 root 3u IPv6 0xfffffe00d95c1438 0t0 TCP *:22 (LISTEN) sshd 1666 root 4u IPv4 0xfffffe00d95c1000 0t0 TCP *:22 (LISTEN) mosquitto 2569 isy 11u IPv4 0xfffffe00d9610ca8 0t0 TCP *:8881 (LISTEN) mosquitto 2569 isy 15u IPv4 0xfffffe00d9610870 0t0 TCP *:8882 (LISTEN) mosquitto 2569 isy 16u IPv6 0xfffffe00d9610438 0t0 TCP *:8883 (LISTEN) mosquitto 2569 isy 17u IPv4 0xfffffe00d9610000 0t0 TCP *:8883 (LISTEN) isy-freeb 2618 isy 17u IPv6 0xfffffe00d9952ca8 0t0 TCP *:8080 (LISTEN) isy-freeb 2618 isy 18u IPv6 0xfffffe00d9952870 0t0 TCP *:8443 (LISTEN) node 2859 polyglot 25u IPv4 0xfffffe00d960f518 0t0 TCP *:3000 (LISTEN)

I'm migrating from my 994 to a brand-new EISY via a backup-and-restore. I'm currently stuck on getting the HTTP/S ports correct. The 994 was using the standard ports (80 and 443) and that's what I need the EISY to do as well, as I have no desire to edit configurations, scripts and firewall settings across scores of devices. Unfortunately, the admin GUI now disables changing those settings. No problem, I'm quite happy working on a *IX command line (although mostly Linux these days), so I went looking for where that might be configured in the filesystem. I found and changed `/var/isy/FILES/CONF/NETWORK.CFG` to `<WebServer><httpPort>80</httpPort><httpsPort>443</httpsPort></WebServer>` (and what I assume is just the multicast DNS advertisement settings in `/usr/local/etc/udx.d/static/mdns.services`), but after a reboot `/usr/local/bin/isy-freebsd-x64` is still binding to the wrong ports (8080 and 8443), which is also what is still shown in the GUI. Does anyone know how to make the EISY use the desired ports? (Hopefully it's not hardcoded in the binary and I have to wind up running a portforwarder or something.) Thanks for any help!