How to manage FTP accounts in Kiravo

Open a website in the hosting control panel, then choose Advanced → FTP. FTP accounts give an external file-transfer client access to the website’s files. They are separate from client-area contacts, database users, and the website’s SSH login.

Use the browser-based File manager if you only need to upload or edit a few files. An FTP account is useful for repeated transfers or a collaborator who needs file access without access to the panel.

Create an FTP account

If there are no accounts, the page shows No FTP accounts and Add account.

1. Click Add account and check the usage and allowance shown on the form.
2. Enter Username. The domain suffix shown beside it is part of the full login name. For example, developer beside @example.com becomes developer@example.com.
3. Set Directory to the folder the account should access. The / shown by the form refers to the website’s home directory. A subdirectory such as public_html/wp-content/uploads limits the account to that part of the site. Check the folder in File manager before using its path.
4. Set a unique Password, or use the key button to generate one. The form requires at least 10 characters, including a lowercase letter, an uppercase letter, a number, and a special character.
5. Save the full username, password, and directory in your password manager, then click Add. Use Cancel to leave without creating access.
6. Check the resulting account entry and directory before sharing the credentials.

Give a collaborator only the directory they need. Access to application code or configuration files can also expose database credentials or let someone change the website’s behavior.

Connect to the server with an FTP client

Confirm the server hostname, protocol, port, and encryption mode for your hosting service before connecting. Use the full FTP username and the password set for that account. If the panel does not provide the connection values, ask support rather than assuming the website domain is the FTP server.

FTP with TLS and SFTP are different protocols. SFTP uses SSH access and is not enabled merely by creating an FTP account. For that workflow, see SSH access. Choose an encrypted protocol supported by your service and enter its matching credentials. The WordPress guide to FileZilla also explains which connection details to obtain from your host.

FileZilla or Cyberduck

Create a saved connection in your client’s connection manager. Enter the confirmed protocol, hostname, port, full username, and password. Select the encryption mode required by the service, then connect.

Check any certificate or host-key warning against the expected server details. Do not bypass a mismatch to make the connection work.

Once connected, check the remote directory before transferring anything. Download a copy before overwriting an existing file, wait for the transfer to finish, and check the affected page in the browser.

If the connection fails

• For a rejected login, check the full username including its domain suffix and the current FTP password.
• For a timeout, check the hostname, port, and protocol against the service’s connection details.
• For a successful login with missing files, check the account’s Directory. The assigned folder may appear as the root in your FTP client.
• For an upload denied by the server, check the destination path, storage allowance, and file permissions before broadening access.

Include the client error and time of the attempt when contacting support. Do not send the password or a screenshot containing saved credentials.

Edit an existing FTP account

Return to Advanced → FTP and open the account’s edit action. Review its directory and any password controls offered. Save the intended change and reconnect your client to check the result.

If you change a password, update saved connections and deployment tools that use it. Check the directory with the collaborator before widening their access.

Remove an FTP account

Use the account’s delete action and verify the username before confirming removal. Removing access is separate from deleting the website’s files. Review any other credentials the collaborator has, since deleting an FTP account does not revoke separate panel or SSH access.

When a collaboration ends, remove accounts that are no longer needed and check that scheduled transfers or deployments do not still depend on them.