SS 6.19

ChrisH
ChrisH
edited March 19 in SecuritySpy

Upgraded to 6.19 today and now 7 of my 12 cameras are not working. Authentication failed is what it says.

All cameras are Amcrest and no settings camera side have been changed, all passwords and users are the same.

I tried to go back to 6.18 and it did not help.

All cameras have been restarted and the M4 mini was also restarted.

Edit: I finally got the cameras to work by setting the cameras to Dahua profile, they all were previously working under Onvif profile.

Comments

  • Ben
    Ben

    I think the specific version number here is a coincidence, most likely what interrupted things was the quitting/reopening of SecuritySpy for the purposes of installing the new version. As you have discovered, switching to the Dahua (or Amcrest) profile is the solution here, hopefully that will continue to work well for you. I'm not sure what could be going wrong with the ONVIF profile, but we'll take a look to see if we can make some tweaks to make it more reliable for these particular cameras.

  • knowz
    knowz

    Morning,

    As of a few moments ago on 11/01/26 I am experienced a similar challenge. I am running sSpy 6.21 and have been since shortly after it was released. All cameras but for 1 are Amcrest.

    In my case, I was checking time stamps on cameras as Daylight Savings Time ended a short while ago. I had one camera that was not displaying time change in sSpy even though when accessing the camera directly using camera's browser interface the correct time was displaying. For kicks I Quit and Restarted sSpy. All Amcrest Cameras that were using "ONVIF profile" for some years now failed to connect with "Authentication Failed" error. A ReoLink running "ONVIF profile" and 2 Amcrest cameras that were running the "Amcrest Profile" connected properly on the restart.

    I do have some vague recollection of experiencing a challenge when enabling "ONVIF profile" on a Amcrest some months ago. It would not work. I subsequently used the Amcrest Profile to connect to the camera and then was able to successfully switch to the "ONVIF profile."

    I did the above just now and switching to the "ONVIF profile" was successful. For the moment I am leaving well enough alone and not Quitting/Restarting sSpy to see if sSpy is able to regain camera connection using the "ONVIF profile" after a restart. I will report back once I do so.

  • knowz
    knowz

    Update. I performed a restart of my sSpy server just now and sSpy was able to successfully re-connect with all Amcrest cameras using the "ONVIF profile." JIC it might be somehow pertinent. The sSpy storage drive is connected via USB.

  • Ben
    Ben

    We are aware that some users have seen authentication issues with Amcrest cameras from time to time. In the latest beta version of SecuritySpy (currently 6.22b18) there are some fixes for authentication, although these are not specific to Amcrest, so that's worth a try, but may or may not help.

    If you're still seeing authentication errors with the ONVIF profile in the latest beta, then the solution is to switch to the Amcrest profile, which doesn't exhibit this issue. As far as we can tell, there are no bugs in SecuritySpy's authentication mechanism as of this latest beta version.

    ONVIF authentication involves the camera comparing a client-supplied timestamp with its own internal clock, so a camera whose internal time is set incorrectly could potentially cause this issue. SecuritySpy tries to correct for this by first obtaining the camera's current clock time, then supplying corrected timestamps based on this. However, some cameras don't supply this information, in which case SecuritySpy is unable to apply this correction.

Categories