I have spent a lot of time testing and trying different stuff to get my setup to work and I am hoping someone can point me in the right direction to solve my issue:
disabling EPSV as in above issue did not resolve my problem.
I also tried disabling MLSD.
sometimes (I cannot figure out when/how) when tested it works as intended, but mostly not. FTPing with filezilla to server works fine.
for testing both machines with no firewall
Vers: 1.55.1
can you post the full debug log that inlcudes the error
the name of the remote in the command does not match the name of the remote in the config file.
sorry, for the confusion: the config I showed is the config for the ftp remote. the one in the command is my crypt remote that points to that ftp remote.
with the exact same command (with a few more files) this happens (until the point where I cancel it, because otherwise it would run for days): https://pastebin.com/d5isw4kv
sorry, i gave up on unreliable ftp many years ago, so i cannot help much with that.
not sure you know that rclone can act as a ftp server.
better yet rclone can act as sftp server, which can use checksums to ensure files are transferred without corruption and crypt the data during transit.
thanks for trying though.
its already planned to run on peer to peer VPN so any additional layer of encryption just kills performance (end point is a Pi4).
Maybe you have an alternative suggestion what I can use as "lightweight endpoint" over not so great internet? The aim is to have my Pi with an external hard drive as off-site backup location. It will run within a VPN connection.
@tomstull I had exactly the same issue as you and almost the same setup (rclone @ raspbian <-> vsftpd @ openwrt). Following @ncw's advice and using latest beta solved it.
pi@ZEROPI:~ $ rclone version
rclone v1.56.0-beta.5554.e635f4c0b
- os/version: raspbian 10.9
- os/kernel: 5.10.17+ (armv6l)
- os/type: linux
- os/arch: arm
- go/version: go1.16.5
- go/linking: static
- go/tags: none