note if the files are text based then remember that Windows use CR+LF for end of line and Linux just uses LF this can cause confusion sometimes.

well ....
1. A FYI, Microsoft announced this year as part of a batch of similar announcements that at least on Win10 this invisible line feed character is being eliminated, so there won't be a problem using files modified by Windows and non-Windows text editors.

and forthermore
2. This has only happened on Windows if you use a Microsoft text editor (eg Notepad, Wordpad, etc). Even in Windows, if you use command line text editors or most 3rd party text editors, you won't have that LF problem. Over the years, this has been my personal solution... If I'm using a file that's modified on both Windows and Linux, I use a command line text editor to make changes in Windows.

a guess is that we are connecting to the server using a publickey, but when we exported the filezilla configuration it did not export our key file. We probably need to track down the key file on Windows, copy it over to our linux machine then browse to it in the configuratio

note if the files are text based then remember that Windows use CR+LF for end of line and Linux just uses LF this can cause confusion sometimes.

Not a problem for FileZilla, it treats the two the same in configuration files.

we are connecting to the server using a publickey, but when we exported the filezilla configuration it did not export our key file/

Technically you would be connecting using a private key. A public key is public by definition, everyone knows it and uses it. The site configuration at most contains the path to a private key, it never contains the private key.

Linux and MacOS should use an SSH keyfile somewhere (probably called .sshkeys or the like).

### BEGIN SIGNATURE BLOCK ###No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.All FileZilla products fully support IPv6.http://worldipv6launch.org
### END SIGNATURE BLOCK ###