RLC-823A --> ftp ---> NAS Synology ???

[Rainman]

I have a new RLC-823A and am very happy with it.
I also have a Synology NAS, where my old cameras store their images without any problems.
On the NAS, creating folders, saving images, everything works like a charm.
I entered the same user credentials for FTP access to the NAS.
But then I get error 452 when I press TEST.

Transport mode is set to "Auto" but also to "PORT" or "PASV" same error.

What am I doing wrong ?

[joseph_1979]

@user_652120033566820_652120033566820 On the ftp server grant write permission to the ftp user you created for the camera.

[Rainman]

@joseph-chircop_497308027822318
On the NAS, creating folders, saving images, everything works like a charm.
I entered the same user credentials for FTP access to the NAS.

[user_682733777735876_682733777735876]

Did you get this to work? What was the solution?
I have an RLC-820A, RLC-520 and an RLC-842A and neither can connect to my Synology FTP. Error 454. When i use Filezilla to connect to the Synology FTP with the same credentials i can connect to it easily. All Synology user permissions are correct, otherwise Filezilla wouldn't work, right?

[joseph_1979]

@user_682733777735876_682733777735876 Try to transfer all files to the same directory. If you use FileZilla/Cerberus servers, directories can be created and files transferred from Cameras.

[user_682733777735876_682733777735876]

@joseph_1979 The problem is that my Reolink cameras can't connect to the Synology NAS at all. When i enter all ftp credentials and try the test button, Error 454 occurs: "Connection failed. Please check your network connection". They are at the same network using the same subnet. I just used Filezilla as a client to test the Synology FTP server, which works fine then. I don't use Filezilla as a server.

There has been some progress though. Although my RLC-820A stated there were no new updates, i found an update on the Reolink website. I updated it to v3.1.0.764_21121717 and now ftp does work with exactly the same settings as before.
Now i have to figure out how to get the RLC-842A and RLC-520 working. They do not have new firmware updates.


Edit,
Support replied quickly and sent me a new firmware for the RLC-842A, this fixed the issue. Next is the RLC-520.

[joseph_1979]

@user_682733777735876_682733777735876 So you had a very old firmware then. My recommendation is to send an email to Reolink support and ask if there is any new firmware. I do this for all my cameras every 3months. Sometimes the download center is not updated.

But if you have installed Filezilla/Cerberus server on your PC, you would have been able to ftp the files. This issue is not with Reolink cameras only but seen the same issue from other brands. Have no idea what NAS requires..... Maybe a wireshark trace will give some light.

[user_729461963661506_729461963661506]

I had the same issue this evening. Latest firmware on the RLC 520A and the Synology. The solution to resolve it was on the Synology in the advanced FTP settings, enable the change user root directories and set the root share to be the shared FTP folder. You can then specify a sub directory for multiple cameras in the Reolink Camera FTP settings.

[joseph_1979]

@user_729461963661506_729461963661506 So before updating the firmware of RLC 520A, the camera was able to ftp the file to Synology, right? Has there been any update on the Synology side which changed the file management part?

[user_729461963661506_729461963661506]

@joseph_1979 Not that I'm aware of as I upgraded the Synology after the units were connected and working. I do have one unit that does not FTP I think it gives a 451 error. This unit was different to all the others and had a dust cap on the POE connector.

[Ben L_363180304232580]

Argh; I already had a Reolink camera working for FTP; when adding a second one I got the 452 error. After close comparison, I noticed I had included a trailing / on the failing camera's "Remote Directory" setting - and that's enough to cause it to barf.

/path/camera/ does not work
/path/camera does work

[joseph_1979]

@ben-l_363180304232580 Correct. There shouldn't be a forward slash at the end of the Path name.