---
schema_version: "1"
id: 57162ac135156e4d586fce873c7ae47f18d1f7154846ac309dac9e9fe0334b84
title: Troubleshooting FTP Connector
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/ftp-connector/latest/ftp-troubleshooting.md
canonical_url: https://docs.mulesoft.com/ftp-connector/latest/ftp-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 36d12ddddbdd68eaa829e2beaa06138be887215cccc52f0bc2027bc56c04e367
description: MuleSoft Documentation Site
release: "2.0"
latest: true
---
---
product: FTP Connector
version: 2.0
is-latest-version: true
---

# Troubleshooting FTP Connector

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To troubleshoot Anypoint Connector for FTP (FTP Connector), become familiar with the information
about troubleshooting Mule application issues.

## Troubleshoot Mule Application Issues

Sometimes you are not sure why the application is failing and you require a better understanding of
what is going on in the app’s interaction with the FTP server.

To resolve this error:

- Use the configuration file to increase the logging level on the server side.

- Try to replicate the issue using an FTP client, for example, Cyberduck or Filezilla. If the issue
  also occurs with these clients, then it is likely that the issue is not related to the Mule app.

- Get better and more detailed logs on the Mule app side by enabling verbose logging for FTP
  Connector and for the JSCH driver:

  1.  Access Anypoint Studio and navigate to the **Package Explorer** view.

  2.  Open your application’s project name.

  3.  Open the `src/main/resources` path folder.

  4.  Open the `log4j2.xml` file inside the folder.

  5.  If the following line is already in the `log4j2.xml` file, uncomment it to enable it;
      otherwise, add it:

      ```xml
          <AsyncLogger name="org.mule.extension.ftp" level="TRACE"/>
          <AsyncLogger name="org.apache.commons.net" level="DEBUG"/>
      ```

  6.  Add the following argument to your run configuration:

      \`-M-Djavax.net.debug=ssl,handshake\`

- Try to minimize or remove unnecessary DataWeave data transformations (you could even use
  hard-coded data) to minimize the app’s complexity and determine whether the issue is with the
  interaction between the app and the FTP server.

For additional information about enabling verbose logging for SDK components in your Mule
application, see the [troubleshoot SDK components](https://docs.mulesoft.com/mule-sdk/latest/troubleshooting)
documentation.

## Understand Common Throws

Here is a list of common throw messages and how to interpret them.

- FTP:ACCESS\_DENIED

An FTP Connector operation attempted to access an FTP server path and performed an action for which
the user does not have permission.

- FTP:CONNECTIVITY

The connection to the FTP server was interrupted.

- FTP:FILE\_ALREADY\_EXISTS

An attempt was made to create a file with the same location and name as an existing file.

- FTP:FILE\_LOCK

An attempt to lock a file was unsuccessful.

- FTP:ILLEGAL\_CONTENT

The **Write** operation received invalid content to write.

- FTP:ILLEGAL\_PATH

The specified path is invalid because, for example, it does not exist.

- FTP:RETRY\_EXHAUSTED

Retries of an execution block are exhausted.

## See Also

- [FTP Connector Reference](https://docs.mulesoft.com/ftp-connector/latest/ftp-documentation)

- [Salesforce Help](https://help.salesforce.com)

- [Known Issues](https://help.salesforce.com/s/issues)