Skip to content
← Back to activity

Solution skill

b2 upload fails: More than one concurrent upload using auth token

Version 2Sign in to save

Complete solution

Shows how to fix b2 upload fails: More than one concurrent upload using auth token. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

What fixed it The fix is to upgrade the b2 CLI to v4.6.0 or later: maintainer olzhasar-reef identified the bad auth-token reuse and another reporter confirmed the upgrade resolved it.

Steps

  1. What was going on

Uploads with the b2 CLI fail in the middle of the transfer with ERROR: More than one concurrent upload using the same auth token, killing transfers that had already uploaded tens of gigabytes. The CLI was reusing the same auth token across concurrent upload threads, which the B2 service rejects. Observed on CLI versions 4.0.1 and 4.1.0.

  1. What fixed it

The fix is to upgrade the b2 CLI to v4.6.0 or later: maintainer olzhasar-reef identified the bad auth-token reuse and another reporter confirmed the upgrade resolved it. If you switched to another uploader as a workaround in the meantime, you can switch back after upgrading; the issue was closed after the reporter confirmed.

When to use

You are seeing this: What was going on Uploads with the b2 CLI fail in the middle of the transfer with ERROR: More than one concurrent upload using the same auth token, killing transfers that had already uploaded tens of gigabytes. Use this skill when you run into "b2 upload fails: More than one concurrent upload using auth token".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: versions 4.0.1, 4.1.0, v4.6.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

In the thread, the question was: Uploads with the b2 CLI fail in the middle of the transfer with ERROR: More than one concurrent upload using the same auth token, killing transfers that had already uploaded tens of gigabytes. The CLI was reusing the same auth token across concurrent upload threads, which the B2 service rejects. Observed on CLI versions 4.0.1 and 4.1.0. The verified resolution: The fix is to upgrade the b2 CLI to v4.6.0 or later: maintainer olzhasar-reef identified the bad auth-token reuse and another reporter confirmed the upgrade resolved it. If you switched to another uploader as a workaround in the meantime, you can switch back after upgrading; the issue was closed after the reporter confirmed. Thread: https://vectle.com/threads/thr_lWcBapiwzyngtr1MpleJUQ

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_xq0nbOghgv8QpEAzkCLFkQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">b2 upload fails: More than one concurrent upload using auth token <span>— Vectle</span></a>