Not seeing version 6.18 update
Not sure what is going on but I saw that 6.18 was released on Feb 12 and my system still is showing 6.17 as the latest version. I checked that I have internet access and could ping the SS website. Is there some staging algorithm in play to release new versions?
Comments
-
We do staged rollouts, whereby each new release is delivered gradually to customers over a 7-day period. This is the safest way to catch and fix any initial problems before they affect too many users, and evens out support queries. You can force the update to be available by holding the alt/option key while clicking the "Refresh" button under Settings > License. No problems have been reported with the 6.18 release.
-
Thanks Ben, that did the trick. I had just moved my cameras to their own VLAN and was wondering if somehow I had broken something. I had real issue with NTP and could not find a configuration that let my cameras then connect to a NTP server. Started looking for possibly installing my own NTP server and when I googled it up one of the options mentioned Security Spy has an NTP server. And lo and behold I installed the SS NTP and that problem was resolved! I'd like to understand the routing issues that made it so I had to do this... ( I had made sure the firewall was open for the NTP port ) but in the meantime it got me back to square one after moving my cameras to their own VLAN. I just love Security Spy.
-
Great to hear that SecuritySpy's NTP server has provided the solution here. This works as a relay between the cameras and a real Internet NTP server, forwarding the UDP packets back and forth.
A routing rule allowing UDP port 123 outbound from VLAN devices to a specific NTP server should work, but there is some complexity (needs a stateful firewall or explicit inbound return rule, and some NTP clients use ephemeral ports rather than 123). So SecuritySpy's relay solution is easier.
-
What's blowing my mind on all this is that I have a Unifi Dream Router and all my switches are Unifi switches. I have the Mac Mini with two network interfaces. One for the default network and one that is on the VLAN. I added the firewall rule to make sure that the NTP would be passed... but in reality I could never get it to work. This morning I tried to set the port on the switch that the VLAN adapter is on to use the Camera VLAN. When I did this it broke being able to see SS cameras from the app on my iPhone or from a browser on my Mac Studio ( which also has two ethernet adapters ... one also assigned to the VLAN ) Somehow I can't get the routing right somewhere... The Mac Mini running SS has its first network interface on my default network and the second one on the VLAN. But when I set that physical port for the second adapter to be on the VLAN then SS seems to want to use that interface even through its the second one... and nothing worked... I changed the physical port back to the default network and then everything works.
I had thought when I created the VLAN and updated SS to the new addresses for each camera that it would continue using the default network for its outbound internet traffic. But it doesn't appear to be the case.
I've obviously have screwed something up somewhere. Thus my new motto in life... "Always Something™"
-
You can always manually download the latest software here: https://bensoftware.com/securityspy/download.html instead of waiting for your Security Spy software to tell you that an update is available.
-
For reasons I don't understand I had to reboot my Mac server before I could connect to the updated software. I could see the camera's ok on the server but neither the mobile app or client (unregistered) version on the client could connect - and the latter were using local IP.
Still a reboot seems to have fixed it.
Dave
-
Tell Google Gemini or your preferred AI your network configuration and it'll help you solve it and give you lots of ideas. I couldn't have done what I've done in the last year without some AI assistance on the networking stuff...
