FreeFileSync Forum

Same error with the 11.13 beta. A cause could of course also be that the hoster does not use the most recent version of ProFTPD. But they are not willed - and I can understand that - to move away from the Ubuntu standard package version. It works, also with 11.12, with my Raspberry and the newest ...

Unfortunately the error is still in 11.12...

Hope FFS 11.12 is released today, since my donation subscription ends today 11:59 pm ... ;-)

Works on local server, which is ProFTPD 1.3.8rc1 now, with TLS 1.3 and TLS 1.2.
Fails on remote server with the error in the attachment. Seems not to work with 1.3. Installed the version with the 1.2 limitation again and that worked.

Don't know for sure. Installed is ProFTPD 1.3.6c-2 (Ubuntu). The config file says "ALL -SSLv3 -TLSv1 -TLSv1.1". So I assume TLSv1.3 is used once the client supports it.

Thanks for the beta version. I'll test it today at night and report here.

Update 10:49: Could already test the beta during a ...

Mea culpa! I indeed had TLS disabled for config 1 (because of this still open problem) and still enabled for config 2. Disabling TLS for both configs now does not show anymore the max. number of ftp connections error.

Maybe it's worth to add this restriction (connection re-use only if identical ...

The server (shared hosting service [of course not under my control] with ProFTPD and parameter MaxClientsPerUser = 10) counts correct.

If I set one FFS config to 10 parallel connections and only run this, it works. If I set one config to 11 and only run this, it - of course - fails.

If I set my 2 ...

:-) Ok, I sit back and wait.... I assume that FFS in general still has some problems with ftp. This problem is still unsolved. Because of this I cannot use TLS for syncing my remote server. I just tried it again. Still same error. Without TLS it works. FileZilla has no problems at all. But FFS is ...

Very sad that there are no more replies.... 😕

Any news about this error? Can you (Zenju) confirm it?

This is from tcpview. FFS creates 10 connections (and tries more) even that I configured 8 for each configuration. And no, I do not run them in parallel.

I already follow the above rules. The error does not occur if I quit FFS between the two runs. If I run the two configurations after another, the ftp connections of the 1st run are obviously not re-used and therefore the ftp server says too many connections.

I'm using FFS 11.11 (Donation Version) mostly with a Linux server. The server limits the number of parallel ftp user to 10.

Therefore I use a FFS ftp user limit of 8 (to allow an additional FileZilla session).

If I start a synchronisation of a configuration and shortly after that (1st one is ...

For testing purposes, I tried to sync the same files to my Raspberry Pi 4. Same error!

On the Pi 4, I can enable a full detail log of the ftp server. See attachment.

The error always is similar to following:
Transfer aborted after 63832064 bytes in 1.96 seconds
notice: user root: aborting ...

Nobody an idea?

Guess https://freefilesync.org/forum/viewtopic.php?t=8272 is the same problem!

Now I get the above curl error even on transfers to sub-directories. This time the file which cannot be written is "ftp://xxxxxxxx.kasserver.com/scripts/tools~1be6.ffs_tmp" (the IP of the server is the ...

What could cause this error?

19:48:11 Error: Cannot write file "ftp://ftp.XXX.de/sync.ffs_db.1c22.ffs_tmp".
CURLE_PARTIAL_FILE: server did not report OK, got 450
450 Transfer aborted. Link to file server lost [curl_easy_perform]
19:48:11 Error: Stopped

It only and always happens with ffs_tmp ...

That's for sure technically possible but kinda overkill for such a functionality...
I'll add "Feature Request" now to the title ;-)

Within this thread , the problem with syncing (reading) from Linux symbolic links was solved in FFS 11.6 (release notes: "Support reading FTP file symlinks"). This covers 99% of my use cases.

Yesterday, I changed a file on Windows, which is a symbolic link on Linux, and tried to sync it back.

That ...

Since I'm getting more and more configurations, it would be great to have a dialog allowing more colors to select for a configuration background.

For example (preview)

I know about the option to manually edit the configuration XML, but a dialog would be nicer...

Hi,

I could not manage it to have <VerifyCopiedFiles Enabled="false"/> in a configuration XML while keeping <VerifyCopiedFiles Enabled="true"/> in the global settings file. I did try it unter <FreeFileSync...> and <Synchronize> . But neither worked.

How is it done so that a configuration setting ...

Can confirm, that it works now. Also following (compare & sync) of a directory tree works well. Will make more tests tonight, but looks good so far :-)

Update Jan 22nd: Found no further errors. Works as expected :-)

For both, compare and sync, what rules does FFS apply to select either ASCII or binary mode?

One finding from the detailled ProFTPD logfile: For each failing file a is in the log. Any idea?

It's always the same error on random 2-3 files out of 21 files in the directory containing all the symlinks. I'll try to enable a full debug log of ProFTPD and check if I can see something. It's funny, that most of the time "apache2.conf" and "crontab" shows the problem.

I can't see a pattern. "Compare" usually works. But sometimes with 2-3 links to normal ASCII files error 550 (is not a directory) is displayed. Very strange...

If i do in FileZilla, it works now all time.

After having some issues with building ProFTPD V1.3.7a from source, I finally managed it. And voilà, it works with your initially provided FFS beta version. Direct links to files are now properly synced. And the size is properly shown in the Size column.

One strange thing: There is "sometimes" an ...

ProFTPD v1.3.7a seems to solve it. I'll try to compile it myself... (tomorrow - it's late now :-)

/etc/letsencrypt/archive/dyn.xxx.de/fullchain450.pem
If this is an exising file, then the SIZE FTP command should return its size, if not => FTP server bug

Yes, this path is correct! I'll check if I can install a better/newer ftp server on my Raspberry. Currently it's the latest available ...

Found an explanation how FileZilla does it:

The directory listings returned by the server may contain information about symbolic links, though this is not covered by neither the FTP specifications nor the SFTP specifications. If FileZilla encounters a symbolic link, it first tries to treat it like ...

Sorry, I did execute the FileZilla command before, but did not post it, as it also gave a 550 error:

Command: SIZE /opt/automation/config_links/cert/fullchain.pem
Response: 550 /opt/automation/config_links/cert/fullchain.pem: No such file or directory

And don't ask me why, but STAT works ...