Nightly "Connection Failed" errors when connecting to SS4.1 via iOS apps
Hello.
As I'm still testing (trial) SS4.1, I'm monitoring the feeds a lot more than usual in the evenings (tweaking the setup). One thing I continue to notice is that, on a daily basis (no pattern that I've been able to find at this point), when I attempt to connect to SS4.1 (via SecuritySpy or Spyglass iOS apps as well as through Safari on the iPhone, and other web browsers on various MacBooks—either on LAN or external), I'll get an error that I can't connect to the server.
The only way to make SS4.1 connectable again is to do one of the following:
- restart SS4.1
- connect to SS4.1 web interface from the Mac mini running SS4.1 (connecting from any other machine isn't possible)
Once I've done either of the above, I can connect to SS4.1 from iOS apps, web browsers, etc., without issue.
No issues with DNS (connections trace back to the machine running SS4.1, SS4.1 just doesn't respond, I can connect to other services on the same computer from tested client devices, etc.), SSL certificates, etc.
I've looked in the logs after this happens (both web log and regular logs) and don't see anything in there.
Any suggestions on looking into this further?
Thanks,
Kristin.
As I'm still testing (trial) SS4.1, I'm monitoring the feeds a lot more than usual in the evenings (tweaking the setup). One thing I continue to notice is that, on a daily basis (no pattern that I've been able to find at this point), when I attempt to connect to SS4.1 (via SecuritySpy or Spyglass iOS apps as well as through Safari on the iPhone, and other web browsers on various MacBooks—either on LAN or external), I'll get an error that I can't connect to the server.
The only way to make SS4.1 connectable again is to do one of the following:
- restart SS4.1
- connect to SS4.1 web interface from the Mac mini running SS4.1 (connecting from any other machine isn't possible)
Once I've done either of the above, I can connect to SS4.1 from iOS apps, web browsers, etc., without issue.
No issues with DNS (connections trace back to the machine running SS4.1, SS4.1 just doesn't respond, I can connect to other services on the same computer from tested client devices, etc.), SSL certificates, etc.
I've looked in the logs after this happens (both web log and regular logs) and don't see anything in there.
Any suggestions on looking into this further?
Thanks,
Kristin.
Comments
-
OK, ran into this issue again last night (and this morning) and I was able document the details of what was happening a lot better than what I was pulling from memory when I first wrong this post. With that, I was totally wrong with a couple of the details I'd written. Since I can't edit the above, I'm going to say ignore the above, and please see below for correct info.
Also, I wanted to include some additional details on my setup, with specific regards to DNS and the domain pointing to the server from outside.
- My internet connection has a static IP address, so I don't need/use any DDNS services.
- I have a dedicated subdomain for SS4.1 (securityspy.mydomain.com) that points to my static IP (and my router handles passing incoming connections from that domain to the appropriate internal server running SS4.1).
- I have a valid/active SSL certificate for the subdomain, and SS4.1 only accepts HTTPS connections.
After a lot of testing last night (jumping between LAN and WAN), I can confirm there are no issues connecting to SS4.1 via the iOS apps (Spyglass and Security Spy) FROM THE INTERNET. But, as soon as I jump on the LAN, I get the "can't connect to server" error in the iOS apps. But, it's ONLY the iOS apps that can't connect to the server. If I ping the subdomain from my iOS device, no issues. If I run a trace on the subdomain, it runs back to the server, no issues. If I connect via Mobile Safari to the subdomain, I can log into the web interface, no issues. The only issues relate back to the iOS apps no being able to connect, while on the LAN.
Once I notice this, if I log in via the web interface (on any device, including the iOS device that can't connect via iOS apps), or restart SS4.1, then attempt to connect again via the iOS apps, they connect without issue. But, after some period of time, it reverts back to not being able to connect again. Or, if I disconnect from the LAN (jump onto LTE), then back on LAN, I can't connect again (from the iOS apps).
So, wondering if there's something about the iOS apps that doesn't like connecting to the server via the domain name (vs the internal IP address) while on the LAN?
Is there any way I can get more info from SS4.1 about denying the connection from iOS apps or anything like that? Everything I look at (trace routes, pings, connecting to server from Safari, etc.) looks/works fine. Only issue is the iOS apps.
Thanks,
Kristin. -
Hi Kristin,
This issue is quite baffling and I'm afraid I have no ready solution for you. This is not something that we have come across ourselves or has been reported by any other user. The fact that connecting using Safari makes the iOS apps work again is particularly perplexing - this shouldn't have such an effect!
What about if you quit the iOS app (double-click the home button on the phone and swipe up on the app in question). When you open it again, does it then connect?
In terms of getting more information, SecuritySpy does write a web log (if this option is enabled under Preferences -> Web), however this will only list successful connections, and it sounds like the connection isn't even being established in the first place, so I suspect that nothing will be written to the log for these failed connections.
Perhaps it's a certificate issue - if you remove your custom SSL certificate(s) and key, and then restart SecuritySpy, do you see the same problem? In this case SecuritySpy will generate its own self-signed certificate.)
It would also be useful if you could test this on a second iOS device. If you don't see the issue, then perhaps there's a problem with the first iOS device (in which case you can try a restore via iTunes).
