Get a stalled handoff moving again

A request or delivery link will not open

Check that you have the entire URL, that its hostname is the expected deployment, and that you are using the right kind of link. /r/ accepts incoming files; /s/ provides an outgoing delivery.

Enter the link password, not your administrator password. If the owner closed or revoked the link, its expiry passed, or its allowance is exhausted, ask the owner to inspect it. Repeated password guesses can trigger a throttle.

The app is preparing but nothing is transferring

The client reads the selection to build the content identities and package manifest. Many small files, a slow source drive, or a network share can make preparation noticeable. Keep files available and unchanged and compare the client’s stage with its network activity.

On a receive, the server may also need to prepare the selected delivery for native transfer. A delay here is different from a failed connection. Record the stage and error, if one appears.

QUIC is not being used

Native transfer needs an enabled endpoint and a reachable UDP port. The deployment’s advertised address, host firewall, and network firewall must all allow it. If the server is behind NAT, its native UDP ports must be forwarded to the server; a TCP forwarding rule will not work. Both native send and native receive listeners need their own configured path. A normal HTTPS reverse proxy does not carry the separate native listener.

Check the transport displayed by the client. HTTP fallback can be expected on a network that blocks UDP. A browser transfer uses HTTPS and is not the native QUIC path.

For a facility deployment, follow native listener setup. If the certificate identity has changed, confirm the new identity with the operator before trusting it.

A transfer stopped halfway

Keep the original source files, chosen destination, partial files, and client history in place. Check the connection, free disk space, mounted drives, link expiry, and quota. Then use Resume or Retry, or votport resume TRANSFER_ID.

Do not delete hidden partial or lease files to tidy the destination before recovery. They can be needed to reuse progress and an existing HTTP download allowance. A password may be required again; revoked access cannot be recovered with a cached allowance.

For browser uploads, inspect the receive history before resending the whole folder: completed files may already have been published. A new upload does not overwrite them and can create suffixed duplicates.

The network is finished but the job is not

“Verifying and finishing” means the client is completing integrity checks and publication. Keep the app open and the destination mounted. The current native clients mark a file complete after publication or verification, not simply after its network byte counter reaches the expected size.

The card’s total elapsed time includes finishing. Its average transfer speed covers bytes moved in the current attempt and excludes the later verification/publication time. A resumed job’s reused bytes are not new network traffic.

The destination cannot be written

Confirm the folder exists, is writable by the process, remains mounted, and has room for partial data and completion work. For a server receive path, inspect the storage-probe error rather than making the directory world-writable.

Network filesystems must meet the supported identity, hard-link, ownership, and publication requirements. Storage guidance explains the commit profiles and operating boundaries.

Verification failed

Keep the exact error and identify which file failed. Confirm that the receipt belongs to the file you selected and to the issuing deployment. A matching name is not a matching cryptographic identity.

Do not rename an incomplete file as the completed result or bypass the check to meet a deadline. Ask the owner to verify the source and provide a new valid copy. The receipt guide separates signature failures from content mismatches.

Ask for support

Include the deployment address without private tokens, client and server release if known, operating system, approximate time and timezone, transfer ID, transport, file count and approximate sizes, stage, and exact error text. Describe what changed before the failure.

Leave passwords, bearer URLs, automation tokens, and confidential files out of public reports. Contact the VOTPort team for a port licensing inquiry or help arranging the appropriate support path.