Product Roadmap: What's Coming Next
How ColorX Technology Turn Night into Day
Reolink App v4.41 Released
So i updated a 8-410 box non -e to the latest version and now the UID is b****red, it wont work, turn it off and on, etc refuses to work with the UID. as sooon as i change to IP it works, i just keep getting auth issues. Anyone else experianced this? the -e firmware update works fine this is only non e version08/23/2019 Firmware for Reolink RLN8-410 and RLN16-410 RLN8-410 0823What's new:Add the function of creating subdirectories by date in FTP.Add the function that the DDNS server address can be set.Add the function that IPC can control the IR LED when connecting to the NVR.Move the language settings page forward in the process of Wizard Setup.Remove configuration import function.The username has to consist of 3~31 numbers, letters, and underscores.Add a 7+1 polling mechanism in the LiveView interface.Add Russian and German language options.The pa*sword of the admin supports input spaces.Fixed the download timeout failure in web Client.Improved the clip function in web Client.Optimize the NVR interface display.KB updated 4 days agohttps://support.reolink.com/hc/en-us/articles/360006937074-Connection-Failed-when-Log-in-Remotely-via-UID
I am having a similar issue with my 8-410, i can connect with the app and client locally but can not connect to it remotely regardless of anything I try, hopefully a new firmware is released soon
received a special firmware from reolink for the box to test out and now my box is totally locked out!!!
rln-16uid is also brokenthe test firmware they sent also erases the pa*sword like the previous poster said, needs the super pa*sword software to reset the pa*sword in order to login.playback via nvr is also broken in test firmware. Only shows a black screen.
what is super pa*sword reset software?
Since everyone was saying the UID is having issues I tried using a DDNS address instead and open the port on my router and they allowed me to connect. I think Reolink had a UID issue in the past, so hopefully they can fix it quickly.
This seems to impact UID only, DDNS, ip or other means works totally fine. Another issue is the corruption of the admin pa*sword and deletion of all other accounts on the system after the upgrade or downgrade.Cynthia is correct in saying you need to downgrade and you will have to use the super pa*sword app to reset it. Its a complete pain in the a*s as it cost me labour in getting someone remotely to do it for me.
Dear Customers,Sorry for the inconvenience caused for you.If your NVR UID begin with "XCP", and if you can't access the NVR remotely via UID (connection failed) after upgrading the latest firmware from here (https://support.reolink.com/hc/en-us/articles/360034504874-08-23-2019-Firmware-for-Reolink-RLN8-410-and-RLN16-410), please try to roll back to the previous firmware.For NVR RLN8-410 (non E), please roll back to this firmware: https://s3.amazonaws.com/reolink-storage/website/firmware/20180814firmware/RLN8-410_180811.zipFor NVR RLN16-410, please roll back to this firmware: https://s3.amazonaws.com/reolink-storage/website/firmware/20180814firmware/RLN16-410_180811.zipAnd if you need supper pa*sword application for resetting the pa*sword, please download the supper pa*sword application (for Windows system only) from this link: https://s3.amazonaws.com/reolink-storage/website/download/SuperPa*sword.exePlease follow this guideline to use the application: https://support.reolink.com/hc/en-us/articles/360008975854-Use-Super-Pa*sword-to-Reset-the-Admin-Pa*sword-on-Reolink-NVR
Sorry for the inconvenience caused to you, For "XCP" NVR with new firmware, our engineer team is working on making it to be able to access remotely using UID. Please subscribe our website to get the latest news.
Setting it up with IP address or DDNS instead of UID is a great workaround. While I don't have an official static IP address account with my ISP, it might as well be one because it hasn't changed in years. I just made sure to set up the port forwarding on my gateway/router to the correct local IP address for my NVR and I can now connect to it remotely.
Was this ever resolved? I have 2x RLN8-410's and 1xRLN16-410 with hw revision H3MB02 that cannot be accessed by UIDOn a whim upgraded the 16ch unit to the latest bios (2012070 released a few days ago); no UID access.And one RLN8-410 N2MB02 that does work.It had been a non-issue to me because I access over vpn, but now I have a request for access via the app, and would rather not have to punch more holes in the firewall.
Never resolved and reolink support said nothing could be done and went on to break more NVR boxes. I have 10 NVR totally lost of the network working standalone with everyone locked out but recording.The only offer I got was 10% saving on a new purchase which doesn't help my customers.Only solution is to manually visit the site, reset the box and downgrade the firmware. Boxes are just over a year old but must have been old stock from reolink.No real solution as the older firmware still had major security holes so you really need to update.
Please submit this issue to https://reolink.zendesk.com/hc/en-us/requests/new and provide with the system information. Our support team will help you deal with this problem.
Hi support call was logged multiple times and your support proceeded to break more NVR remotely. Firmware breaks auth so unable to connect remotely to the box, no matter what login is present. It requires a site visit.
Hi there! Join the Commnunity to get all the latest news, tips and more!