v3.1.0.764（beta）Snap URL function out of service
-
Snap URL function out of service with this software.
I have installed the v3.1.0.764（beta）firmware on my 3 RLC 811A cameras
The Snap URL function does not work. you will get the main login page. and you are asked to put the user name and the password.
when downgraded to the old version it is OK again.
I testted my RLC 810 cameras with v3.1.0.764_21121703 firware to. They have the same behavier. -
Jumping on, i have just installed the same beta for my RLC 511WA and albeit it worked, it moved all of the privacy spots set up. Easy to fix..... but just thought I would mention it if Reolink see this
-
@metal-me_488723804848306 Hello there, thank you for the feedback. By saying snap URL, do you mean FTP upload feature, RTSP URL, or the IP address URL to access the camera via web UI? Please specify so we can help. Thanks.
-
@tazzy_423116622815407 Hello Tazzy, please check if you have clicked Update configure File before you upgrade the firmware. If yes, all the settings will be removed.
However, it is suggested to remove all the previous settings when you upgrade your camera with v3.1.0.764(beta) because it is an important upgrade from the previous version. With all the settings cleared, you will be able to get a better experience of the new features.
-
@reolink-lorenz that will be quite a pain if i have to reset all. Can you confirm why I need to do this?
p.s. I can now access the camera on different WIFI networks and 4G - Thanks -
@tazzy_423116622815407 There are major updates in this firmware version and we will share more info in a later post.
To deliver the best performance, we recommend you to click Update Configure Files when you upgrade the camera with the latest firmware. Of course, this is a suggestion and you don't have to do so. But clearing all the settings and setting them up again may deliver better results. Hope this helps. -
@reolink-lorenz Hi. When I installed the v3.1.0.764 firmware on my two 510WA, the integration from Home Assistant stopped working completely.
When I reverted to v.3.0.0.494, the integration started working again.
I know, that it's not your problem that third party integration stops working, but I thought I would let you know in case something is not right regarding this in the beta version.
Have a nice day
/Lars. -
@reolink-lorenz
FTP works as well as FTPS.
this funstion will not work.
example:
1. Snap a picture of the ipc device
http://192.168.123.145/cgi-bin/api.cgi?cmd=Snap&channel=0&width=640&height=360&rs=000000&user=admin&password=xxxx
Kaspersky internet security is installed. -
@metal-me_488723804848306 Hello there, this issue happens because we have enabled HTTPS and disabled HTTP by default in the v3.1.0.764 firmware. You may change the http to https in the snap URL to see if it works.
Or, you may access the camera via web browser and enable HTTP. Note that the settings to enable/disable HTTP is available on web UI only now. But it will be available in the next desktop client update, which is ver 8.6, coming soon within a month.
Let us know if you have any other questions.
-
@lars_455575943418087 Hi Lars, thank you for the feedback. This issue happens because the ONVIF is disabled by default in the v3.1.0764 firmware.
You may access the camera via a web browser and enable ONVIF. Note that the settings to enable/disable ONVIF is available on web UI only now. But it will be available in the next desktop client update, which is ver 8.6, coming soon within a month.
Let us know if you have any other questions.
-
@reolink-lorenz
using https in the Snap url works but it is first blocked by Kaspersky because you use a self signed CA root certificate and not not signed by a publicly trusted certificate authority signed CA certificate in the firmware.
This make no sense.
the webbrowser and Kaspersky will first block the Snap capture everytime until you have given the clicked the OK.
you have to include a authority signed CA certificate in the firmware.Disadvantages of a Self-Signed SSL Certificate
- No browsers and operating systems trust self-signed certificates.
- The browsers will not show visual indicators of trust like a padlock symbol and HTTPS in front of the domain name.
- Snapshot captured in this way have to proceed through a security warning page with error messages like “error_self_signed_cert” or “sec_error_untrusted_issuer” or “err_cert_authority_invalid” to access your content.
- This means that you must manually click on the ”Accept Risk” button to capture the snapshot.
-
@metal-me_488723804848306 Hello there, thank you for the feedback. We will take a further look into the authority signed CA certificate.
An easy workaround is to disable the HTTPS and enable HTTP only. Use the original snap URL with HTTP and it shall work. Let us know if you have any questions.
