SteveSBE Posted October 8, 2011 Share Posted October 8, 2011 Using Mobilinc Pro v3.03.00 I cannot access my ISY server via HTTPS either via the internet or over my local network. I use ISY 3.1.9. I recreated the self signed certificate (2048) but that didn't help. I've rebooted both my modem/router and the ISY server. I've tried accessing it using my dyndns Dynamic DNS Host name and also by using the external IP address...no luck. I can get to it via my browser using HTTPS on the local network on my Win7 PC. What's happening? Thanks, Steve Link to comment Share on other sites More sharing options...
elvisimprsntr Posted October 8, 2011 Share Posted October 8, 2011 my guess is that the broken UPnP in .8 and .9 ISY firmware will likely be a contributor. I've been informed this will be fixed in .10 firmware. i also am running MLPro and HD, but on iOS 5.0 GM Seed and haven't had any problems as you describe, and I use ISY static IP address and port forwarding in my router, and my router supports loop back. Link to comment Share on other sites More sharing options...
InsteonNut Posted October 9, 2011 Share Posted October 9, 2011 Hi Steve, There could be a couple of factors here: The UPnP issue in 3.1.9 may be an issue, loopback support in your router, and IP/Port information in MobiLinc does not match your ISY's IP/Port info. Try taking the Secure IP address and port from the MobiLinc->Lighting Controller settings and enter this into Safari on your iPhone: https://Your.Secure.IP.Address:Secure-Port Can Safari on your iPhone over cellular or Wi-Fi connect to your ISY? Please set the Connect Method to HTTPS for this test under My Settings->Lighting Controller. Let me know if this works or not and we can take the next diagonse step. Wes Link to comment Share on other sites More sharing options...
SteveSBE Posted October 9, 2011 Author Share Posted October 9, 2011 I did the following in this order: 1. With both WiFi and 3G on, entered https://Your.Secure.IP.Address into Safari. I could not access the ISY server. 2. Turned off WiFi and with only 3G on, entered https://Your.Secure.IP.Address into Safari. I could access the ISY server. 3. With WiFi off and with only 3G on, tried accessing via HTTPS using MobiLinc. I could access the ISY server. 4. Turned WiFi back on and with both WiFi and 3G on, tried both MobiLinc and Safari. I could not access the ISY server. It looks like there's a setting on my router preventing HTTPS access at home (HTTP works). (I'll try access via a remote WiFi too if I get a chance.) It should be noted that: 1. I could not access MobiLinc from work (using 3G only) on Friday...it would time out. I'll try again on Monday. 2. I have been able to access MobiLinc in the past before upgrading to ISY 3.1.9 and MobiLinc 3.03.00. 3. I've also tried it with my router firewall off...doesn't work. I've tried it with my router firewall on and my ports routed...doesn't work either. Per your comments: There could be a couple of factors here: The UPnP issue in 3.1.9 may be an issue, loopback support in your router, and IP/Port information in MobiLinc does not match your ISY's IP/Port info. 1. UPnP is off. Does it need to be on? 2. I have accessed MobiLinc in the past. What do I look for concerning loopback support? I have an Actiontec GT724R. 3. I've verified the IP/port multiple times...per my test above it looks like that's OK. Hi Steve, There could be a couple of factors here: The UPnP issue in 3.1.9 may be an issue, loopback support in your router, and IP/Port information in MobiLinc does not match your ISY's IP/Port info. Try taking the Secure IP address and port from the MobiLinc->Lighting Controller settings and enter this into Safari on your iPhone: https://Your.Secure.IP.Address:Secure-Port Can Safari on your iPhone over cellular or Wi-Fi connect to your ISY? Please set the Connect Method to HTTPS for this test under My Settings->Lighting Controller. Let me know if this works or not and we can take the next diagonse step. Wes Link to comment Share on other sites More sharing options...
InsteonNut Posted October 9, 2011 Share Posted October 9, 2011 Hi Steve, Ok, it looks like you can access your ISY with MobiLinc from 3G. (Don't know about the timeout issue you had. Your first bullet list indicated that this did work at one point). My guess is that there is a loopback issue here when you are on your home network. Here's my guess as to what's happening. With ISY firmware 3.1.9 UPnP doesn't reliably respond to MobiLinc's query. As a result, MobiLinc thinks you are away from your home network since it cannot see your ISY. MobiLinc will then use the HTTPS settings (assuming you have Auto selected for the Connection Method) to connect to you ISY. HTTPS will be either the router's IP address or a Dyndns address that points to your router's IP. Since you are inside of your network, your router needs to understand to loopback that IP address back internally to your network. Not all routers support this which may explain why HTTPS works when you really are outside of your network and doesn't work when you are inside your network. To isolate the loopback issue perform the following: 1. iPhone connected via Wi-Fi on your home network. 2. Change the connect method to HTTPS. 3. Attempt to sync with your ISY. If this fails, then the router is not looping back correctly. To confirm, do this: 1. With the iPhone still connected to your local Wi-Fi source change the secure IP address to the internal IP address (the real IP address of your ISY. 2. Change the connect method to HTTPS. 3. Attempt to sync with your ISY. If this works, then HTTPS and MobiLinc/ISY is all working correctly and the issue is with the router not forwarding the internal loopback IP back to your ISY. Until the 3.1.9 UPnP issue is resolved in 3.1.10 the work around is to set the connect method to HTTP when you are at home and HTTPS or Auto when you are away from home. This will force MobiLinc to use the right method to connect to your ISY without relaying on UPnP. Wes Link to comment Share on other sites More sharing options...
SteveSBE Posted October 9, 2011 Author Share Posted October 9, 2011 Wes, I tried what you asked me to do... 1. iPhone connected via Wi-Fi on your home network. 2. Change the connect method to HTTPS. 3. Attempt to sync with your ISY. It DID fail. To confirm, I did this: 1. With the iPhone still connected to your local Wi-Fi source change the secure IP address to the internal IP address (the real IP address of your ISY. 2. Change the connect method to HTTPS. 3. Attempt to sync with your ISY. It DID NOT fail. So it looks like HTTPS and MobiLinc/ISY are working correctly and the issue is with the router not forwarding the internal loopback IP back to your ISY. Thanks for your help. It looks like I'll need to wait for 3.1.9. Steve Link to comment Share on other sites More sharing options...
InsteonNut Posted October 9, 2011 Share Posted October 9, 2011 Hi Steve, Thanks for confirming your scenario. Just for clarity with other's reading this post, the UPnP issue should be solved in version 3.1.10. Wes Link to comment Share on other sites More sharing options...
awzulich Posted October 20, 2011 Share Posted October 20, 2011 I also have a problem connecting the MobilLinc Pro v03.03.00 with the ISY 99i v 3.1.9, but the issues are slightly different. - Using secure https: get network error/connection failure both remotely and on a local wifi network. Verified that the https IP is correct. - At a remote location, if I change connect to http: I get a green light on the lower left corner, and MobilLinc tries to connect, but does not change device. - putting local http IP on the secure https line and connecting locally through wifi: same network error using https. If I change to http for sync, it goes right through. MobilLinc worked flawlessly before change to v 3.1.9 and/or v 03.03.00 Would this be fixed by v 3.1.10 or is something else going on? Any thoughts would be appreciated - Link to comment Share on other sites More sharing options...
InsteonNut Posted October 20, 2011 Share Posted October 20, 2011 Hi Al, It sounds to me like a network setup issue. But, please upgrade to 3.1.10 and also upgrade MobiLinc to the latest from the app store and try local connect again on your local Wi-Fi. If that works, then set your iPhone to 3G and try remote access using the router's IP address with your port forwarding rules in place to reach your ISY device. Wes Link to comment Share on other sites More sharing options...
awzulich Posted October 24, 2011 Share Posted October 24, 2011 Hi Wes - I upgraded to 3.1.10 and MobiLinc 3.04.00. Port forwarding is enabled for the ISY. I am still able to connect via HTTP with wifi, but not HTTPS. Cannot connect with HTTP nor HTTPS via 3G. So, I'm back where I started with MobiLinc dead in the water. Link to comment Share on other sites More sharing options...
awzulich Posted October 24, 2011 Share Posted October 24, 2011 Hi Wes - I upgraded to 3.1.10 and MobiLinc 3.04.00. Port forwarding is enabled for the ISY. I am still able to connect via HTTP with wifi, but not HTTPS. Cannot connect with HTTP nor HTTPS via 3G. So, I'm back where I started with MobiLinc dead in the water. As an update, now Port Forwarding in the router will not recognize the ISY. Port forwarding can see the desktop and the wireless printer, but when I force the ISY IP address, it now lists it as "offline" .. thoughts? Link to comment Share on other sites More sharing options...
InsteonNut Posted October 25, 2011 Share Posted October 25, 2011 Hi Al, How is the router recognizing that the ISY may be offline? Is the router attempting to contact the ISY at the ISY's IP address/port to see if it'll respond? If the router can't see the ISY then I wouldn't expect MobiLinc or any other outside connection to be able to see your ISY either. I would try the standard troubleshooting things, like reboot the ISY and verify it's IP/port settings and how those compare to the router's settings. Before trying MobiLinc, while on 3G, try connecting to your ISY through your router using Safari. Once you have that working, and all your network settings are correct, then fire up MobiLinc and try to connect externally. Wes Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.