FreeFileSync Forum

Fixed! Converting the IPv6 server config to a single string and back indeed had a bug:
https://www.mediafire.com/file_premium/pt4vaju4rqj5kbc/FreeFileSync_13.8_%255BBeta%255D_Windows_Setup.exe Zenju, 16 Jul 2024, 06:53

Thank you so much! I've tested the beta version and everything is fine now.

I think the brackets might be required for IPv6 to distinguish the address from domain names? FreeFileSync doesn't do any parsing and just forwards to getAddrInfo. I've further confirmed that it may fail even with the brackets. All characters after the last colon, just as the case without brackets ...

adding some trash characters to the end

Example?

What I saw, was to add square brackets around the address.
So if IPv6 is:
fe80::219:99ff:fe20:c251
use:
[fe80::219:99ff:fe20:c251]

(I have no way of testing.) therube, 12 Jul 2024, 17:37

I see... It works as well and should be the proper way. Thank you so much!

the last four hex digits Hex? In any case, aren't they going to be the "Port" number, & those 4 digits should be place in the Port: box, & not included directly into the Server/IP: box. https://freefilesync.org/images/manual/sftp-login.png Thank you for your reply! I am using the bare ipv6 address ...

I am using FreeFileSync on Windows to connect to a server through SFTP with its ipv6 address. When I browse the directory, it works well and I can view the existing files. But after I confirm the settings, the last four hex digits of the address are dropped mysteriously so I can complete neither ...