Fix transfer and resume errors

The receiver declined this transfer offer.

The receiver chose not to accept this offer. Confirm that you sent the intended files to the intended person before offering them again. A decline is not a connection fault.

The transfer ended before it completed.

Check both computers for a more specific message, correct that problem, and use the recovery action offered. Keep the original files and destination progress; a failed attempt does not mean all completed files must be sent again.

The transfer was interrupted before durable completion.

Keep both tabs open and restore any lost connectivity or file access. Use the recovery action shown. If a new tunnel is needed, offer the same set and select the same destination so WolfP2P can verify reusable content. See recovery limits.

The transfer ended after making no confirmed progress within the allowed time.

No confirmed progress arrived within the allowed time. Check that both people are present, both computers are awake, and no permission or destination decision is waiting. Then use the available recovery or new-transfer action.

This attempt stopped because no transfer progress was confirmed in time. The sender can start recovery while the transfer is still available.

Check both panels for a waiting permission prompt, destination problem, or lost connection. Keep the source and destination. The sender can start recovery, and the receiver should then follow any local permission or destination request. The transfer’s overall lifetime continues while recovery is attempted; a moving network indicator does not confirm saved progress.

The transfer reached its maximum lifetime before completion.

This attempt cannot continue beyond its lifetime. Follow the panel’s next action to offer the files again. Preserve destination content for verification; restarting an attempt does not necessarily mean resending every completed file.

Automatic recovery stopped when the suspension allowance expired. The sender can start recovery while the transfer is still available.

The automatic attempt stopped, but that alone does not mean the transfer’s overall lifetime or saved progress expired. Keep the source and destination. The sender can start recovery; the receiver should wait for that action and then restore destination access if requested.

This browser has already completed its local transfer work.

This browser has no more local transfer work to perform. Check the overall result and the other participant’s status before closing the session. Local completion alone should not be treated as confirmation of the other browser’s outcome.

The destination could not confirm durable completion.

Do not treat this attempt as complete yet. On the receiving computer, check storage, access, and the current recovery message. Keep the original source until WolfP2P confirms that the destination has been durably saved and verified.

WolfP2P encountered an unexpected problem.

Keep the source and destination. Follow the recovery action shown, and avoid reloading while useful recovery is in progress. If the same action repeatedly fails, note the code, both browser versions, and what you were doing, then report the problem.

The saved checkpoint does not match the source content.

The saved checkpoint does not match the source content. Do not force resume from it. Keep the intended source unchanged and follow the panel’s restart or new-offer action so destination content can be checked again.

The completed destination content did not match the source verification value.

Do not use the affected destination file as a verified copy or delete the original. Keep the source unchanged, check drive and file access, and follow the offered recovery action. A repeated mismatch should be reported; it is not a malware-scan result.

Content verification is not available for this source or destination.

Do not assume an existing or received file is verified. Restore readable access to the source and destination and follow the panel’s available action. Check browser compatibility if verification remains unavailable.

WolfP2P could not verify the completed destination content.

Keep the source and do not treat the destination as a verified copy yet. Check that the receiver still has access to the file and drive, then use the offered recovery action. This message does not itself say that the contents differ; the verification operation could not finish.

This browser no longer holds the record of which transfer it was recovering, so that transfer cannot be resumed. Files already received are still where they were saved.

This is not a missing folder or a refused permission, and choosing files again will not answer it: what is gone is the identity of the transfer itself, so there is nothing left to resume into. Close the outcome and start a new transfer. Anything already written to the destination stays there, and the file list and transfer report remain available wherever this browser still holds them.

The saved transfer record does not match the offered file set.

Check that the sender selected the intended original file set. If names, sizes, or the set changed, use a new offer instead of applying an unrelated saved record. The receiver should review that offer and destination.

The saved progress cannot be applied to this transfer.

Use the current panel’s restart or new-offer action. Preserve destination files: WolfP2P may still verify completed files for reuse even when this particular saved progress record cannot be applied. See what recovery preserves.

Source preparation stopped after five minutes without new progress. The sender can try again while the transfer is still available.

WolfP2P stopped receiving measured progress from source preparation for five minutes. Large files can take longer overall while progress continues. Check that the source drive is connected and accessible, then try again while recovery is offered. The timeout alone does not identify the cause of the stall.

The waiting window ended. Start a new transfer when both participants are ready.

Choosing files, answering an offer, and retrying before acceptance have a twenty-minute human wait. Once source-folder enumeration starts, five minutes without new progress ends that work. Start again when both participants can continue. If files were already saved during an earlier attempt, keep them for verification and reuse.

Recovery preparation stopped when its time limit expired. The sender can start recovery again while the transfer is still available.

The current recovery-preparation attempt stopped. The sender can start recovery again while the transfer remains available. Keep the source and destination; this expiry alone does not end the transfer’s lifetime or delete saved progress.

The tunnel closed as complete, but this side did not confirm completion.

The two sides disagree about whether the transfer finished. Do not assume either answer. Open the file list to see exactly which files were written here, and check the same list on the other computer before deciding whether anything needs sending again.

The two browsers are using incompatible protocol versions.

Both participants need compatible versions of WolfP2P. Preserve source and destination files; once this stopped session is no longer recovering, reload the official site on both computers and establish a new tunnel.

The two browsers cannot continue because their transfer protocols differ.

The browsers cannot continue this attempt together. Preserve the files, reload the official site on both computers after this stopped attempt, and establish a new tunnel. Do not bypass the compatibility check.

The transfer received a file chunk that did not match the protocol.

The received chunk did not meet the transfer protocol. Do not assume the current file is complete. Keep the source and use the recovery action shown. If it repeats with both browsers on the current site, report the error.

The received content-verification value was invalid.

The verification value was invalid, so it cannot prove that the file is correct. Keep the original and use the panel’s recovery action. If it repeats, report the error with the code and browser versions.

The received file position or size is outside the offered file range.

The received data refers to a position or size outside the offered file. Keep the source unchanged and follow the recovery action shown. Do not treat the destination as complete just because some bytes arrived.

The content-verification request did not match the active transfer.

The request did not belong to the active transfer’s expected verification work. Follow the available recovery action and preserve the files. Repeated failures on current browsers should be reported.

The content-verification response did not match the active transfer.

The response did not match the active verification request. Do not count it as evidence of matching content. Follow the panel’s recovery action and report repeated failures.

The received message belongs to a different transfer.

WolfP2P rejected a message for another transfer. Use the current panel’s available action and avoid controlling the same saved session from extra tabs. If it repeats, retain the code when reporting it.

A transfer entry exceeds the supported manifest limit.

This is a limit on an entry in the transfer description, not necessarily on the file’s byte size. Note the affected entry and code, and report the problem if you cannot offer it. Do not assume changing large-file mode fixes this limit.

The received transfer message was invalid.

The browsers cannot safely use this message. Keep the files and follow the recovery action shown. If it repeats after both browsers load the current site for a new session, report it.

The received transfer message exceeded the supported size limit.

The protocol message exceeded its supported limit. This does not by itself mean the selected file is too large. Keep the files, follow the available next action, and report repeated failures.

The received Safe or Quick mode value was invalid.

The received mode value was not valid. Use a mode offered by the current panel when starting again; do not attempt to override it. If both browsers use the current site and this repeats, report it.

The received transfer plan does not match the offered files.

WolfP2P cannot safely apply a plan that disagrees with the offered files. Keep the source unchanged, review the intended set, and follow the panel’s recovery or new-offer action.

The transfer offer was invalid or incomplete.

The offer was incomplete or invalid. Check the intended source selection and use the new-offer action when available. If it repeatedly fails with the current site on both browsers, report it.

This browser received transfer work for the wrong participant role.

The transfer message does not fit this browser’s sender or receiver role. Follow the current panel’s recovery action. If it repeats in a new session, report the code and describe which computer was sending.

WolfP2P could not save the report because its local transfer context is missing. The transfer outcome is unchanged.

No—the report-saving problem does not change the transfer outcome. Check the transfer result separately. If reporting the issue, include this code and the result shown; the missing local context may prevent saving this report.

WolfP2P could not save the local transfer report. The transfer outcome is unchanged.

The transfer outcome is unchanged. Check the result shown in the panel rather than sending the files again just to create a report. Keep the error code if you need to report the missing record.

The local report update did not finish. The transfer outcome is unchanged.

Do not repeat a successful file transfer merely because its local report update failed. The transfer outcome is unchanged, but the report may be incomplete. Use the panel result and keep this code if you need support.

The peer's browser does not have permission to access the files needed to continue.

Ask the other participant to follow the permission message on the other computer and grant access to the intended files or destination. Changing permissions on your computer will not restore access on the other one.

The peer's browser cannot open the file or folder chooser needed to continue.

The other participant needs to open the official site directly in a browser with the required chooser. The other participant can check browser compatibility. Opening a chooser on your computer will not resolve that limitation.

The peer's destination does not have enough space to continue the transfer.

The destination on the other computer needs attention. Ask that participant to check drive space and browser quota or choose another destination. Do not delete your source copy to address a storage problem on the other computer.

Reading or writing a file failed on the peer's device, so the transfer stopped.

Ask the other participant to read the more specific local message and check the source or destination access, drive connection, and available storage on that computer as applicable. Use the recovery action after that issue is resolved.

The peer’s place in the tunnel ended when that browser’s connection to the service did.

The other browser lost its live service attachment. Its reserved seat may still be recoverable, and this message does not establish an intentional departure or a retired tunnel. Follow the current panel while the owning browser reconnects.

The peer moved to another tab, which reclaimed that place in the tunnel.

The person is still there; the tab you were paired with is not. Nothing is wrong on your side. Wait for the new tab to reconnect, or agree a new tunnel if it does not.

Another tab took over the peer’s place in the tunnel.

A replacement connection holds the other participant’s seat. Wait for that browser to reconnect and follow the panel’s recovery action. This message does not provide or prove a transfer of recovery authority to another device.

The transfer ended in failure on the peer’s side.

The record carries no further reason, so nothing more specific can be said about it. Whatever was written before it stopped is still on your disk. Ask the other participant what appeared there, and offer the same set again when the other side is ready.

The other side treated the transfer as finished while this one did not.

The two computers disagree about the outcome, and neither answer should be assumed. Compare the file lists on both sides. Anything missing here can be offered again; WolfP2P verifies what already arrived rather than resending it.

The transfer was interrupted on the peer’s side.

An interruption is the recoverable kind of stop, but whether it can still be picked up depends on the state your own session is in. Check what the panel offers you now. If recovery is not available, offer the same set again.