1. Prerequisites for Connection
Before opening FileZilla, ensure you have the correct credentials from the hosting provider or server administrator. You will need:
- Hostname or IP Address: The server’s address (e.g.,
ftp.yourcompany.comor192.168.1.50). - Username: Your specific FTP/SFTP account username.
- Password: The secure password associated with the username.
- Port: The communication endpoint. Use Port 21 for standard FTP (not recommended for sensitive data) and Port 22 for SFTP (Secure FTP).
2. Installation and Setup
If you do not already have FileZilla installed on your workstation:
- Navigate to the official FileZilla website.
- Download the FileZilla Client (Do not download the FileZilla Server).
- Run the installer and follow the standard installation prompts for your operating system (Windows, macOS, or Linux).
3. Understanding the FileZilla Interface
Familiarizing yourself with the interface is essential for efficient workflow. The layout is divided into four primary sections.
- Top Pane (Message Log): Displays the status of your connection, command requests, and server responses. This is your primary diagnostic tool if a connection fails.
- Left Pane (Local Site): Displays the file directory of your local machine.
- Right Pane (Remote Site): Displays the file directory of the web server once connected.
- Bottom Pane (Transfer Queue): Tracks the progress of files actively being uploaded or downloaded, along with tabs for failed and successful transfers.
4. Establishing a Connection
There are two primary ways to connect to a server in FileZilla: the Quickconnect bar and the Site Manager.
Method A: The Quickconnect Bar (For One-Off Tasks)
Located directly beneath the toolbar, the Quickconnect bar is useful for rapid, temporary connections.
- Enter the Host, Username, Password, and Port into their respective fields.
- Click the Quickconnect button.
- If prompted with an “Unknown host key” warning (common with new SFTP connections), verify the host and check the box to “Always trust this host, add this key to the cache,” then click OK.
Method B: The Site Manager (Recommended for Ongoing Projects)
For plugin development or environments you access frequently, configuring the Site Manager saves time and enforces secure connection protocols.
- Go to File > Site Manager (or press
Ctrl+S/Cmd+S). - Click New Site and name it appropriately (e.g.,
Project Alpha Staging). - On the General tab, configure the following:
- Protocol: Select SFTP – SSH File Transfer Protocol whenever possible.
- Host: Enter the server IP or hostname.
- Logon Type: Select Normal (or “Key file” if using SSH keys for authentication).
- User / Password: Enter your credentials.
- Click Connect to initialize the session, or OK to save the profile for later.
5. Managing Files and Directories
Once connected, your remote server files will populate in the Right Pane.
Uploading Files (Deploying Plugins/Mockups)
Uploading direct to the server is the most efficient way to deploy large plugins or static mockup sites, bypassing the file-size upload limits often found in platforms like WordPress or Drupal.
- In the Left Pane (Local), navigate to the folder containing your plugin or mockup files.
- In the Right Pane (Remote), navigate to the target directory (e.g.,
/public_html/wp-content/plugins/). - Select the files/folders locally, right-click, and choose Upload, or simply drag and drop them from the left pane to the right pane.
Downloading Files (Backups and Troubleshooting)
- Locate the file you need to pull from the server in the Right Pane.
- Ensure your Left Pane is set to the folder where you want to save the file.
- Right-click the remote file and select Download, or drag it to the left pane.
6. Remote File Editing
For rapid plugin development or debugging, you can edit remote files directly without manually downloading and re-uploading them.
- Go to Edit > Settings > File editing.
- Select Use custom editor and browse your computer for your preferred IDE or text editor (e.g., Visual Studio Code, Sublime Text).
- Once configured, right-click any file in the Remote pane and select View/Edit.
- FileZilla will download a temporary copy and open it in your editor. When you save the file in your editor, FileZilla will automatically prompt you to upload the modified file back to the server.
7. Best Practices and Security
To maintain the integrity of our company’s infrastructure and client websites, adhere to the following guidelines:
- Always Prioritize SFTP: Standard FTP transmits data, including passwords, in plain text. SFTP encrypts the connection. Always use SFTP unless explicitly instructed otherwise by a systems administrator.
- Verify File Permissions: Incorrect file permissions can break web applications or create severe security vulnerabilities. You can change permissions by right-clicking a remote file/folder and selecting File permissions….
- Standard secure directories are usually set to
755. - Standard secure files are usually set to
644. - Never use
777(full read/write/execute for everyone) on a live server.
- Standard secure directories are usually set to
- Monitor the Transfer Queue: Before closing FileZilla, always check the “Failed transfers” tab at the bottom. A single failed file during a plugin upload can crash an entire website. If files fail, right-click them in the queue and select Reset and requeue all to try again.
By mastering FileZilla and adhering to these protocols, our development team can ensure stable deployments, rapid troubleshooting, and secure infrastructure management.
