WebFTP issues
Use the message or symptom below to find why a WebFTP transfer failed and what to do next.
Limits
| Limit | Value |
|---|---|
| File or folder name | Up to 128 characters; up to 124 for a folder on an object-storage deployment. |
| Path | Up to 512 characters. |
| Session duration | 1 day from opening the session. This limit is not adjustable. |
| Transfer lifetime | 1 day from creating the transfer. |
| Monthly transfer volume | Depends on the workspace’s plan. See Plans & billing. |
Error codes
Find the error code below. The CLI may show a shorter message without a code; see CLI messages.
| Code | Meaning | What to do |
|---|---|---|
webftp_name_too_long# | "That name is too long to store. Shorten it and try again." The file or folder name exceeds the name limit. | Shorten the name to at most 128 characters, or 124 for a folder on an object-storage deployment, and retry the transfer. |
max_length# | "Input is too long. Please enter a shorter text." The path exceeds 512 characters. | Shorten the path, or move the file to a folder closer to the root, then retry the transfer. |
webftp_invalid_path# | "You can only select files within the same directory." A multi-file download includes files from different folders. | Download each folder's files separately. |
webftp_limit_exceeded# | "This workspace has used its WebFTP transfer volume for this month. New transfers can start again when the month resets, or after a plan upgrade." The workspace has used its monthly WebFTP transfer volume. Transfers already running can finish. | Wait for the monthly usage reset, or upgrade the workspace's plan before starting another transfer. |
webftp_content_not_accepted# | "This deployment moves file content through object storage, so it can't be sent to the server directly. Refresh the page and try again." The upload method does not match this deployment's file-transfer requirements. | Refresh the page and retry. If you are using alpacon cp, update the CLI and retry. |
auth_interactive_channel_requires_presence# | "A token can't open a Websh, editor or WebFTP session. Sign in with alpacon login or the web console and try again." A token cannot open a WebFTP session. | Sign in with alpacon login or the web console, then try again. |
The error message reference has the console wording for webftp_name_too_long, max_length, webftp_invalid_path, webftp_limit_exceeded, webftp_content_not_accepted, and auth_interactive_channel_requires_presence.
The session closed on its own
A WebFTP session ends 1 day after it opened. Activity and browser reconnects do not reset this time limit, and you cannot extend it in settings. Open WebFTP again to continue transferring files.
A session also ends when the file-transfer service restarts or its work session ends. If the work session has expired, completed, or been revoked, request another work session before opening WebFTP.
A transfer is missing from the list
A transfer expires 1 day after it is created. After expiry, it does not appear in the transfer list and you cannot open its details. Expired transfers and their stored files are deleted 7 days after expiry. Start the transfer again if you still need the file.
CLI messages
The alpacon cp command does not include the error code in every refusal. Check the operation and the input alongside its message:
Invalid input.: an overlong file or folder name can produce this message. Shorten the name to the limit above and retry.path: Invalid input.: a multi-file download that spans different folders produces this message. Download the files from each folder separately.files: Invalid input.: an older client can produce this message when its upload method is not supported by the deployment. Update the CLI and retry.plan limit reached: WebFTP transfer volume this month.: the workspace has used its monthly transfer allowance. The message includes reset and upgrade guidance; wait for the reset or review Plans & billing.