When I am within the signal of my home LAN, my iPhone 5s running the iOS app version 1.58.00 connects just fine with the server. But as soon as I leave and am using only cell phone internet access, I cannot connect. What is odd is that my app WILL receive alerts if I'm away. I just can't connect and take a look at the full clips.
Unable to connect to server
- Thread starter Elinor
- Start date
fenderman
Staff member
- Joined
- Mar 9, 2014
- Messages
- 36,903
- Reaction score
- 21,275
you need to either port forward the webserver port or setup a vpn (more secure)...it wont magically work
fenderman
Staff member
- Joined
- Mar 9, 2014
- Messages
- 36,903
- Reaction score
- 21,275
something is set wrong...
Silas
Pulling my weight
Uninstall and then re-install the app on your phone, for some dumb reason this works on my androids with iVMS
Silas, I tried uninstalling and re-downloading then re-entering my username, password etc. While inside the LAN and using wifi I confirmed that the iOS app was able to connect to the server. I then turned off wifi and using only the cell connection tried to connect to the server and failed.
Fenderman, I'm not sure which settings you suggest are wrong but on the iPhone the following are set for Blue Iris:
use cellular data; allow notifications; show in Notification center (these come through, by the way, even though I can't connect to the server); sounds; and background App refresh is turned on.
To recap: everything used to work, until a power glitch at the house caused the DSL router to go off. When power was restored, of course the external IP address changed (because I don't have a static one). Blue Iris on the PC in the house knows about the new external IP address, and when I'm within the LAN using Blue Iris on my iPhone, it also knows about the new external IP address.
What else might I try?
Fenderman, I'm not sure which settings you suggest are wrong but on the iPhone the following are set for Blue Iris:
use cellular data; allow notifications; show in Notification center (these come through, by the way, even though I can't connect to the server); sounds; and background App refresh is turned on.
To recap: everything used to work, until a power glitch at the house caused the DSL router to go off. When power was restored, of course the external IP address changed (because I don't have a static one). Blue Iris on the PC in the house knows about the new external IP address, and when I'm within the LAN using Blue Iris on my iPhone, it also knows about the new external IP address.
What else might I try?
fenderman
Staff member
- Joined
- Mar 9, 2014
- Messages
- 36,903
- Reaction score
- 21,275
is the port number correct?
also make sure you have not selected https in the app..
fenderman
Staff member
- Joined
- Mar 9, 2014
- Messages
- 36,903
- Reaction score
- 21,275
confirm the IP ADDRESS and that the port is open with Open Port Check Tool
Did the local ip address of the pc change?
fenderman
Staff member
- Joined
- Mar 9, 2014
- Messages
- 36,903
- Reaction score
- 21,275
Port forwarding is set on the DSL Router to the port we want to use, for the IP address of the Blue Iris server. This is the port reported as "closed". The Blue Iris PC was turned off and on. The program came up and sees everything. Tried using the iPhone on cell only and it still failed to connect to the server.
How do I open the closed port?
How do I open the closed port?
Solved!
On a whim I decided to remove the port forwarding setting on the DSL router and then re-enter it. I also opted to select TCP/UDP protocols rather than just TCP. I applied the re-entered settings for the server IP address. Am thinking that somehow the table of these values became corrupted in the router and re-entering fixed it.
Ta da! iPhone now connects to the server when only on cell phone and outside of the LAN.
Thank you very much, Fenderman, for your help in sleuthing this out. With the next power outage, if this happens again, I'll know how to reset it and be off running again.
On a whim I decided to remove the port forwarding setting on the DSL router and then re-enter it. I also opted to select TCP/UDP protocols rather than just TCP. I applied the re-entered settings for the server IP address. Am thinking that somehow the table of these values became corrupted in the router and re-entering fixed it.
Ta da! iPhone now connects to the server when only on cell phone and outside of the LAN.
Thank you very much, Fenderman, for your help in sleuthing this out. With the next power outage, if this happens again, I'll know how to reset it and be off running again.
Elinor, I'm glad Fenderman got you going and I understand it works OK now when on cellular (the WAN) but am wondering if this would happen again if you had another power outage, so I have 2 questions:
1) When setting the port forward in your DSL modem did you forward to a device ( name of BI server) or to a specific IP address (of BI server)?
2) If the answer to #1 above is 'IP address', is your BI server configured with a static IP or is it set to DHCP (router assigns IP) ?
Hi TonyR--
The port forward in the DSL modem is set to a specific IP address of the computer in our house on which the Blue Iris server runs. My Blue Iris server is configured to DHCP. I have not seen this IP change with a power cycle. But today I'll run some experiments and if any wisdom comes from 'em I'll post back here.
The port forward in the DSL modem is set to a specific IP address of the computer in our house on which the Blue Iris server runs. My Blue Iris server is configured to DHCP. I have not seen this IP change with a power cycle. But today I'll run some experiments and if any wisdom comes from 'em I'll post back here.
You should definitely set the BI server to have a static IP and if possible also reserve that IP in the router.
The reason why the BI server's IP did not change with power cycling THIS time is that no other device took that IP and the server was ready sooner and 'lucked' out. Oftentimes after a power cycle when another device other than the BI server requests and gets an IP before the BI server is ready to accept, the IP previously used by the BI sever is assigned to the other device and the BI server gets a new IP.
The reason why the BI server's IP did not change with power cycling THIS time is that no other device took that IP and the server was ready sooner and 'lucked' out. Oftentimes after a power cycle when another device other than the BI server requests and gets an IP before the BI server is ready to accept, the IP previously used by the BI sever is assigned to the other device and the BI server gets a new IP.