Connection Failed: The server that responded is not SecuritySpy

lsandell
lsandell
edited November 2021 in SecuritySpy

I am running version 5.3.4

I had originally run this on an old iMac and it was running fine and I could access the cameras, etc. thru a web browser and through the app on my iPhone. Because of the old iMacs lack of performance, I re-installed SecuritySpy from my original download to a new Mac-Mini M1. I then uninstalled SecuritySpy for my old iMac (and had disconnected it from the LAN).

I can use everything just fine on the Mac mini. I did have to give the DDNS a new name, tested it and the test light turned green. I tried adding the new DDNS on the iPhone app and that is when I get the error message, "Connection Failed: The server that responded is not SecuritySpy". I have deleted the app from my iPhone twice, re-installed and gotten the same result.

I can access the software from another computer on the network using the static IP address.

Any help would be much appreciated. I do love the software!!

Lynn Sandell

Comments

  • Ben
    Ben

    Hi Lynn, great to hear you love the software!

    It's difficult to know exactly what is going wrong here, but some possible causes of this problem include incorrect port numbers, or illegal/special characters in names of cameras/groups/schedules. If you would like us to investigate this for you, could you please email us at support@bensoftware.com and provide SecuritySpy's debug file (SecuritySpy menu > Debug submenu > Create Debug File On Desktop), as well as a screenshot of any port forwarding settings you have created in your router that you may have created.

  • jsc524
    jsc524

    I'm having the exact same problem, was this resolved?

  • Ben
    Ben

    Hi @jsc524 so that we can help you with this problem, please email us and include a debug file (SecuritySpy menu > Debug > Create Debug File On Desktop), and let us know exactly what details you are using to add your SecuritySpy server to the iOS app. There is no one solution to this problem; there must be some specific issue with your setup that is causing this.

Categories