This article describes how to troubleshoot and potentially resolve issues with
Transfer Appliance online mode.

## Not configured for online operations

**Error:**

`This appliance has not been configured for online operations.`

**Solution:**

If you ordered an online appliance and received this error, contact
Transfer Appliance Team at [data-support@google.com](mailto:data-support@google.com).

If you ordered an offline appliance, this message is expected. Offline
appliances do not support online mode. If you need further assistance, contact
Transfer Appliance Team.

## Credential file is missing

**Error:**

`An error occurred while running hta containers: "credential file:
'/tmp/key.json is missing"`

**Solution:**

Verify that you did the following items:

- [Prepared IAM permissions and storage](https://docs.cloud.google.com/transfer-appliance/docs/4.0/prepare-permissions.md.txt).
- [Created a service account key](https://docs.cloud.google.com/iam/docs/creating-managing-service-account-keys#creating_service_account_keys) for the user-managed service account.
- Renamed the service account key to `key.json`
- Uploaded the service account key to `/tmp` on the appliance.

## Failed to run containers binary

**Error:**

`An error occurred while running hta containers: "Failed to run HTA
containers binary \"opt/ta_containers/ta_containers\": exit status 1"`

**Solution:**

Contact Transfer Appliance Team at [data-support@google.com](mailto:data-support@google.com) for assistance.

## API has not been used in project or it is disabled

**Error:**

`Storage Transfer API has not been used in project PROJECT_NUMBER before or it
is disabled.`

A similar error can occur for the Pub/Sub API or the
Cloud Storage API.

**Solution:**

Make sure that the required APIs are enabled in the project that you ordered
the appliance from. If the appliance service account belongs to a different
project, also enable the required APIs in the project that contains the
service account. The project number in the error message identifies the
project in which the API must be enabled.

For the list of required APIs, see
[Enable the APIs](https://docs.cloud.google.com/transfer-appliance/docs/4.0/prepare-online.md.txt#enable-apis).

## Failed to update Operating System

**Error:**

`Failed to update Operating System.
An error occurred while updating the appliance: "failed update OS: error
transferring configuration files: error setting up tmp mount for new srv
partition: error setting up mount /var/tmp/update1298680145: command
[mount /dev/sdc2 /var/tmp/update1298680145] failed with output: mount:
/var/tmp/update1298680145: special device /dev/sdc2 does not exist.\n and
error: exit status 32"`

**Solution:**

Contact Transfer Appliance Team at [data-support@google.com](mailto:data-support@google.com) for assistance.

## Update cannot be run without credentials file

**Error:**

`Update cannot be run without credentials file. Please upload credentials file
onto the appliance.`

This error occurs when trying to
[update software](https://docs.cloud.google.com/transfer-appliance/docs/4.0/update-software.md.txt) on the
Transfer Appliance.

**Solution:**

Make sure that you've completed the following steps:

- [Prepare IAM permissions and storage](https://docs.cloud.google.com/transfer-appliance/docs/4.0/prepare-permissions.md.txt).

- [Prepare for online transfer](https://docs.cloud.google.com/transfer-appliance/docs/4.0/prepare-online.md.txt). Specifically, ensure that you
  have:

  - Created a user-managed service account.
  - Granted appropriate permissions to the service account.
  - Created a service account key for the user-managed service account.
  - Renamed the key to `key.json` and uploaded it to `/tmp` on the appliance.

## Object prefix does not update to nil string

**Error:**

This error occurs when you expect the object prefix to default to the nil string when running update destination bucket but it does not.

Updating without the object prefix specified:

`ta online --bucket=myrandombucket`

Running this command does not update the object prefix to the nil string since the object prefix only updates if you specify the `--object_prefix` flag.

**Solution:**

Update with at least the object prefix specified:

`ta online --bucket=myrandombucket --object_prefix=""`

`ta online --bucket=myrandombucket --object_prefix=`

`ta online --object_prefix=""`

`ta online --object_prefix=`