The Invalid Transfer Profile error comes in the below form:FATAL [202X-XX-XX XX:XX:XX] Invalid transfer profile . Valid transfer profiles:
- Receiving this error means that you are using a vendor name that has not been setup yet
- One way to check this is by opening the configuration.yaml file and viewing the list of vendors and verifying that the vendor you tried using is not on that list
To resolve this error:
- Ensure that you have not misspelled the name of the vendor, check the “Valid vendors: ” part of the error to see if any are listed
- If no vendors are listed under “Valid vendors: ” then you will need to go to the configuration.yaml configuration file and add in the vendor, below is proper formatting:
transfer_profiles:
profileone:
profile: profile_name
accelerated: true
bucket: bucket_name
prefix: prefix
region: us-west-2
daemon_mode:
enabled: true
base_path: /media/drive/
*If you are still not seeing your vendor, make sure your yaml is properly formatted and make sure you are editing the correct yaml file (these are tied to the user signed in) . On Windows, make sure not to run CMD.exe or PowerShell as Administrator otherwise it will try to read from a configuration file that is not the local user one.
Comments
0 comments
Article is closed for comments.