Editing FAQ

This is a list of frequently asked questions and corresponding answers. Please read this topic carefully before asking any questions.

== General FAQ ==

<ol>

<li><b>How much does FileZilla cost?<br />Is FileZilla free?<br />Can FileZilla be used commercially?</b><br />
FileZilla is free open-source software distributed under the terms of the [http://filezilla.sourceforge.net/GPL.html GNU General Public License] free of charge.
<br />
Basically this means that everyone, including corporate entities, can use FileZilla, including but not limited to private, educational and commercial use.
</li>
<li><b>What do the version numbers of FileZilla mean?</b><br />
The version numbers of FileZilla (client and server) are in the following format: n.n.n[c], where n is a number and c an alphabetical character.
The first number is the major version number followed by two minor version numbers. The character at the end is optional and indicates maintenance releases, which mostly fix bugs; the "a" or "b" suffix does NOT imply the instabilities conventionally associated with an "alpha" or "beta" quality release.

<br />
<br />
Example: 2.2.4 would be the original version, the first maintenance would then get 2.2.4a as version, the next 2.2.4b and so on.
<br />
<br />
</li>

<li>
<b>I have a question, where can I get help?</b><br />
Most importantly, don't rush. Think before you ask. What are you trying to do? What is happening instead? What should have happened?
You might find the following two guides of interest:<br />
[http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] by Eric S. Raymond<br />
[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively] by Simon Tatham
</li>

<li>
<b>How to get in contact with with the FileZilla team?</b><br />
There are several ways to establish [http://filezilla-project.org/contact.php contact] with the developers: the easiest way might be the use of our [http://forum.filezilla-project.org forum] or, if a direct conversation is needed, IRC - #filezilla at freenode (<i>chat.freenode.net</i> or see the [http://freenode.net/irc_servers.shtml list of servers]).
</li>

</ol>

== FileZilla Client FAQ ==

<ol>
<li><b>I can't list the contents of any directory on the server or I can't transfer any files</b><br />
<b>I get "Critical transfer errors"</b><br />
<b>I can't connect to my server</b><br />
Most likely incorrect configuration of either FileZilla, your firewall, your router or a combination of it. Please read the [[Network Configuration]] guide.
</li>

<li><b>What are the command line options supported by FileZilla?</b><br />

See [[Command-line arguments (Client)]]</li>

<li><b>Where does FileZilla store all its sites and settings?</b><br />
The location of FileZilla's settings directory depends on your operating system. On most systems, sites and settings are stored in the ''~/.filezilla'' directory. The odd exception is Windows, where the settings are stored in the ''%APPDATA%/FileZilla'' directory.
</li>

<li><b>Why won't FileZilla start anymore?</b><br />
This could happen if for some reason your FileZilla installation or the settings get corrupted. 
First try to reinstall FileZilla, this won't change your settings.
If that does not help, delete FileZilla's settings directory (see above). Notice that all your settings and sites are lost if you do this without taking a backup. 
</li>

<li><b>I can't start FileZilla under Windows 95, 98, ME, NT4 or 2000, it terminates with a runtime error.</b><br />
The most recent versions of FileZilla no longer support Windows 9x/ME/NT4/2000. Please consider upgrading your OS to Windows XP or higher, especially since the older Windows versions are no longer supported by Microsoft. Using older versions of FileZilla is not recommended due to known security vulnerabilities.
</li>

<li><b>I want to help, how can I translate the FileZilla client?</b><br />
Please see http://filezilla-project.org/translations.php for details.
</li>

<li><b>FileZilla does not display or transfer files containing non-English characters</b><br />
Please see the [[Character Set]] entry.
</li>

</ol>

== FileZilla Server FAQ ==

<ol>
<li><b>I've just installed the server and after starting the interface, it asks for a server address.</b><br />
The administration interface can be used to configure local or remote servers. Most likely you want to configure your local server. In this case enter 127.0.0.1 as server address. For the server port, you have to enter the same port number you did specify during installation for the admin port. (default: 14148). If you set a password, enter it. If you want the administration interface to remember it, select the appropriate checkbox.</li>

<li><b>I'm behind a <u>firewall</u> and nobody can connect to my server or transfer files / directory listings</b><br />
You have to configure your firewall to allow incoming connections on the ftp/ftps port (default: 21/990), as well as allowing outgoing connections from the server. In FTP Active Mode, FileZilla Server tries to use a port whose value is equal to the ftp port for outgoing connections minus one. If that fails it tries to use a port number that is equal to the ftp port  plus one, then it requests a port from the operating system. For that reason it might be easier to allow all outgoing connections from the server. Further you have to allow a port range for incoming connections for passive mode transfers. You can specify a port range on the "Passive mode" page in the settings dialog. In most cases, a range like 5000-5100 is sufficient. With certain firewalls, FileZilla Server might not be able to determine the external IP address. In this case you have to enter manually the IP address (or the host name) on the “Passive mode” page in the settings dialog.
</li>

<li><b>I'm behind a <u>router</u> and nobody can connect to my server or transfer files / directory listings</b><br />
You have to configure your router to forward the ftp/ftps port (default: 21/990) to the server machine. Further you have to forward a port range for passive mode transfers. You can specify that port range on the "Passive mode" page in the settings dialog. In most cases, a range like 5000-5100 is sufficient. Most likely, FileZilla Server might not be able to determine the external IP address if it is behind a router. In this case you have to enter manually the IP address (or your host name) on the Passive mode page in the settings dialog. </li>

<li><b>I'm behind a <u>router and a firewall</u> and nobody can connect to my server or transfer files / directory listings</b><br />
Just follow both steps 2 and 3 in this case.
</li>

<li><b>How can I enable anonymous logins?</b><br />
Just create an account with the name <i>anonymous</i> or any other name of your choice and select from the Credentials top-down menu the "Do not require a password to log in" option.
</li>

<li><b>How can I test that my server can be reached from the internet?</b><br />
The easiest way to test the connection to your server is from an external machine. You can test the accessibility of your server using the free service from http://ftptest.net/.  Note that connecting from inside the local network or localhost might not work as firewalls and/or routers could forward ports only for requests coming from outside the internal network.
</li>

<li><b>How do mount points work? How can I share multiple mount points?</b><br />

Let's say you want to make your picture collection in D:\mypictures available as /pictures for a specific User or Group. Create the user/group and in the right panel click on the Add button and set the Virtual path to / and the Native path to D:\mypictures. Now the server will display the virtual directory pictures right in the root directory for that user or group and its content will be that of D:\mypictures.
If you want to share multiple mount points just add more of them.

<li><b>The Administration interface says that the virtual and/or native path is invalid, or that it must be absolute or not be empty, how do I fix that?</b><br />

Mount point paths, both the virtual and native ones, must be entered in a specific format. To learn more about that format, The native path is a local file path, the virtual path is the path that the FTP users will see and it is mapped to the native path by FileZilla Server. To add a mount point click on the Add button and enter a virtual path (eg. \) and a native path (eg, C:\ftproot\sample).



</li>

<li><b>How can I share network drives?</b><br />
Generally sharing network drives is not recommended, as all data has to be transferred twice. Just install FileZilla Server on the other machine instead.
If you still want to share a network drives with FileZilla Server, make sure the account FileZilla Server runs under has access to the network drive. By default, FileZilla Server runs using the SYSTEM account. You can change the account FileZilla Server uses on the service page in the management console of Windows: Start -> Settings -> Control Panel -> Administrative Tools -> Services -> FileZilla Server FTP server -> Log On.

However, even then sharing mapped network drives might not work since Windows networking has some bugs.
</li>

<li>'''Is it safe for all user and groups settings to upgrade from older Filezilla server?'''<br/>
Upgrading to the newest version is always recommended, configurations are automatically migrated.</li>

<li>'''I have forgotten my password for connection to my server via administration interface. How can I reset it?'''<br/>
The password is stored in the <filezilla><admin><password> section of the server settings file. You should completely remove the <password> section and restart the server. After that you can connect to the server without password.
By default the settings file is stored in %appdata%\filezilla-server folder of the user who started the server. The windows service run as System user by default. The path of System user's appdata is %windir%\system32\config\systemprofile\AppData\Local\.
Also you can find out the settings file path in logs. Just open <installation folder>\Logs\filezilla-server.log and find a line with "Settings written to " string.
</li>
</ol>
@@ Line 26: / Line 26: @@
 You might find the following two guides of interest:<br />
 [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] by Eric S. Raymond<br />
-[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively] by Simon Tatham<br />
+[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively] by Simon Tatham
-Please also have a look at the [[Limitations|known limitations of FileZilla]]
 </li>
@@ Line 51: / Line 50: @@
 <li><b>Where does FileZilla store all its sites and settings?</b><br />
-The location of FileZilla's settings directory depends on your operating system. On most systems, sites and settings are stored in the ''~/.config/filezilla'' directory. The odd exception is Windows, where the settings are stored in the ''%APPDATA%/FileZilla'' directory.
+The location of FileZilla's settings directory depends on your operating system. On most systems, sites and settings are stored in the ''~/.filezilla'' directory. The odd exception is Windows, where the settings are stored in the ''%APPDATA%/FileZilla'' directory.
 </li>
@@ Line 60: / Line 59: @@
 </li>
-<li><b>I can't start FileZilla under Windows 95, 98, ME, NT4, 2000 or XP, it terminates with a runtime error.</b><br />
+<li><b>I can't start FileZilla under Windows 95, 98, ME, NT4 or 2000, it terminates with a runtime error.</b><br />
-The most recent versions of FileZilla no longer support Windows 9x/ME/NT4/2000/XP. Please consider upgrading your OS to Windows Vista or higher, especially since the older Windows versions are no longer supported by Microsoft. Using older versions of FileZilla is not recommended due to known security vulnerabilities.
+The most recent versions of FileZilla no longer support Windows 9x/ME/NT4/2000. Please consider upgrading your OS to Windows XP or higher, especially since the older Windows versions are no longer supported by Microsoft. Using older versions of FileZilla is not recommended due to known security vulnerabilities.
 </li>