Fix a failed cloud import

Start with the message beside the connection test or the job’s Details in Imports. These checks apply to Import from another cloud, where dosya’s servers copy the files. If you ran a command on your computer, use the local rclone guide.

Resolve a refused start

Message or state	What to do
Upgrade required	Ask the destination workspace owner to review their plan. Remote import needs a paid plan, with limited trial access.
Payment needs attention	Use Update payment or ask the owner to correct the payment in billing. A paid plan label alone does not allow new imports after a payment lapse.
Allowance used	Check This month or Trial allowance. Regular allowances reset at the next calendar month in UTC; the trial cap covers the whole trial.
Too many running imports	Wait for an existing import to finish, or cancel one you no longer need. The owner’s other workspaces can use the same slots.
Could not check the plan	Try again later. Do not repeatedly create jobs while the plan check is unavailable.
Not available for your account yet	The feature is not currently available to this account. A different password will not resolve that message.
No permission to add files or use S3	Ask a workspace admin to check your role and the destination folder.
Folder not found	Choose the destination again in the current workspace. It may have been moved, deleted or selected in another workspace.

See plans and allowances before changing a subscription.

Address refused

Remote import refuses dosya’s own hosts and addresses, localhost and private network addresses. Check that you entered the source service’s public endpoint rather than a dosya WebDAV or S3 address. A private NAS address cannot be reached through this import flow. Do not substitute an IP address to bypass the refusal.

Steps: check the connection and source

1. Confirm the selected service and source account. Password managers can fill the wrong account’s details.
2. Check Folder to import, including the bucket name when the service needs one. Test the parent path if a folder cannot be found.
3. For a service marked Token, follow token authorization and paste the complete token again.
4. For Koofr, generate an app password for rclone from Koofr’s password settings. Enter that app password in Password, rather than your normal Koofr account password.
5. Select Test connection again. If too many tests have been attempted, wait before testing again.

Files failed after copying began

Open the destination and check what arrived. A failed or cancelled import can leave completed files in place. Done with errors also means the result is incomplete. Read Details, resolve the reported problem and start another import for the affected source folder when ready.

Keep the source files until you have checked the destination. When contacting support, include the service, status and error text, with tokens, passwords and private file names removed. See monitoring and cancellation for the table controls.

Expected result

After resolving the reported cause, Test connection succeeds and an eligible import can start. Inspect the destination and failed-file details before treating a previously partial copy as complete.

Related guides

• Check cloud import plans and allowances
• Monitor or cancel a cloud import
• Run rclone on your computer