k6jav Posted March 14, 2009 Posted March 14, 2009 Remote access was working correctly for me until I updated the firmware to version 2.70 (I was running the version of firmware that shipped with the unit). After upgrading, I got the message that it could not connect. Has the port number of the unit changed? When I log in locally, no port number is listed. I saw a post that said if no port number was showing, forward port # 443. I tired this without luck. I tried remote access using both my dyndns account and the current IP address, but neither worked. I have rebooted the ISY, but that did not help. What am I doing wrong?
Sub-Routine Posted March 14, 2009 Posted March 14, 2009 Are you using HTTPS? I'm no expert but if you use HTTP then I think you have to forward port 80. Rand
k6jav Posted March 14, 2009 Author Posted March 14, 2009 I should have mentioned that I also tried forwarding port 80 with no luck. It appears that it is not a port forwarding issue, since when I put the ISY in the DMZ, I still received the error message, "unable to connect". In the address of the ISY, I am using the port number that I was prior to upgrading. Is this port number still correct? How do I verify it, since the help screen only gives me the IP address and no port number?
Sub-Routine Posted March 14, 2009 Posted March 14, 2009 I should have mentioned that I also tried forwarding port 80 with no luck. It appears that it is not a port forwarding issue, since when I put the ISY in the DMZ, I still received the error message, "unable to connect". In the address of the ISY, I am using the port number that I was prior to upgrading. Is this port number still correct? How do I verify it, since the help screen only gives me the IP address and no port number? No, the address should not have a port number since the update unless you change the port to that number. The new default https is port 443 and does not need to be appended to the address. If you change port 443 it is displayed in About as previously. See the Advanced_Configuration_Guide to read and change port assignments (CWP). Sorry for the confusion. Rand
MikeB Posted March 14, 2009 Posted March 14, 2009 Newer ISY firmware now uses standard port #s by default, so you will need to change the port forwarding in your router. We recommend forwarding port 443 to your ISY, since this ensures a secure connection from your remote location. You'll also need to create a certificate. See this article for more details: http://www.universal-devices.com/mwiki/ ... o_Your_ISY Once you correctly forward port 443 to your ISY, you should be able to connect using your external IP address (or DynDNS address if you prefer), but be sure to use HTTPS:// and not HTTP://. If you try all this and it does not work, it's possible that your ISP is blocking certain traffic to your home (because they don't want you to host your own web server). If that's the case, you could try configuring the ISY for a non-standard port. Use the Advanced Configuration guide that Rand linked you to to change the port via TELNET. For example, change the HTTPS port to something like 555 (whatever you prefer). Be sure to update your router's port forward after configuring the ISY and try again. Your URL would then have to be appended with :555. So, for example, it might be: https://myisy.dyndns.com:555 Please let us know how you make out.
k6jav Posted March 14, 2009 Author Posted March 14, 2009 Thank you for the information. I had always used HTTP and the update changed that to HTTPS, so with no certificate, forwarding either port 80 or port 443 did not work. Now that I have a certificate, everything works as it should. Thanks again.
MikeB Posted March 15, 2009 Posted March 15, 2009 Glad to hear. FYI, if you forward port 80 to the ISY that would work using HTTP://, but port 80 is more likely to be blocked by your ISP. HTTP is also not encrypted, so we do not recommend it in most circumstances.
Recommended Posts