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!

I do not know how to change it, but I am pretty sure they wanted it locked (probably not in a binary) to reduce support issues.

PG2 uses/used the 80/443 ports (http redirects to https) and setting IoX (the ISY running on your eisy) to those ports, would conflict with that.  I know they deprecated PG2, but I think it is still there and running.  You could try opening the IP address of your eisy in a browser to see if Polyglot responds to the 80/443 ports.

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)

 

 

@Jason Madden this is nothing new to the eisy. The Polisy had similar restrictions. This has been somewhat discussed in another thread focused more on setting static IP, but your issue also revolves around the same issue for apparently why UDI made this change.

Support!

There were comments (when Polisy was released) that the number of support tickets dealing with network issues and users that set static IP. Many would set the (static) IP on the ISY994 rather than applying a router IP reservation then changed network equipment created a lot of tickets for support.

In an attempt to limit such issues the devices are set to not be altered by users. 

Additionally, with the implementation of node servers some external systems use different ports to communicate and could cause conflicts so I believe UDI made further use of limiting the port options so that internal and external connections would be handled by the eisy (and Polisy) and not something users could easily "corrupt" by using different (potential conflicting ports). 

I'm not sure what you mean by:

1 hour ago, Jason Madden said:

I have no desire to edit configurations, scripts and firewall settings across scores of devices.

Seems like it would just be the firewall to allow eisy in/out access and wouldn't impact other devices. But only you know your (apparent) intricate network situation. I wouldn't expect anything to change from the hardware side as it's been this way since the Polisy was released (about 3 years ago).

(really, "scores"? A "score" = 20...yeah...getting technical and comical, but figured you could handle it since you have a technical question/issue)

 

And FYI - I am a user; just like you and most others here. I'm not affiliated with Universal Devices in any capacity. Just a user helping others out; like so many here. 

 

16 minutes ago, Geddy said:

Seems like it would just be the firewall to allow eisy in/out access and wouldn't impact other devices. But only you know your (apparent) intricate network situation. I wouldn't expect anything to change from the hardware side as it's been this way since the Polisy was released (about 3 years ago).

If you have devices using the rest interface (or other node servers), then you would have to update the port setting on all those devices/servers.  I have half a dozen Shelly devices that I had to change the port settings on to talk to Polisy vs ISY (but since I chose to make the IP address of my Polisy different than the ISY, it was not a step I could have avoided anyway).  With 2 to 4 setting updates per device, I had close to 20 changes easily.  But in the whole process of migrating, it was definitely one of the quickest/easiest things I had to do.

20 hours ago, Jason Madden said:

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!

You may try to using port forwarding of your router to deal with the new ports but using the old ports externally like you did before. 

Example: Forward port 80 to 8080 at whatever IP your eisy is on and do the same for 443 to 8443.


TRI0N

I can safely say that some of those tickets were because at the beginning the Polisy would let you set the ports to 80/443, and then the whole system would need to be factory reset.  However, now the PG2 is on in the Eisy, there isn't a port conflict anymore.  I will say that a lot of ISY integrations (like the one for Stream Deck, and the one for Hoobs/Homeseer do not allow you to pick ports (even if you put it in the URL itself).  They simply do not work, which kinda sucks.  I have considered doing some work with my firewall and a hairpin firewall rule to work around this, but I never got around to it...