From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40])
	by lore.proxmox.com (Postfix) with ESMTPS id EB7FB1FF0BC
	for <inbox@lore.proxmox.com>; Thu, 29 Oct 2026 20:30:02 +0100 (CET)
Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1])
	by gate001.proxmox.com (Proxmox) with ESMTP id 27E6A21413;
	Thu, 29 Oct 2026 20:30:01 +0100 (CET)
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Erik Fastermann <e.fastermann@proxmox.com>
Subject: applied: [PATCH pve-guest-common] tunnel: websocket: prepend api
 token name when missing
Date: Thu, 29 Oct 2026 20:29:50 +0100
Message-ID: <179330218728.2032226.16424087102346863399.b4-ty@b4>
X-Mailer: git-send-email 2.47.3
In-Reply-To: <20260618110433.124789-1-e.fastermann@proxmox.com>
References: <20260618110433.124789-1-e.fastermann@proxmox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1793302196632
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.431 Adjusted score from AWL reputation of From:
 address
	DMARC_MISSING             0.1 Missing DMARC policy
	KAM_DMARC_STATUS         0.01 Test Rule for DKIM or SPF Failure with Strict
 Alignment (newer systems)
	RCVD_IN_DNSWL_MED        -2.3 Sender listed at https://www.dnswl.org/,
 medium trust
	SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
	SPF_PASS               -0.001 SPF: sender matches SPF record
Message-ID-Hash: YQGZCE4AATGIM2PLHJRS7VPBEEM2NMY2
X-Message-ID-Hash: YQGZCE4AATGIM2PLHJRS7VPBEEM2NMY2
X-MailFrom: t.lamprecht@proxmox.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop;
 banned-address; emergency; member-moderation; nonmember-moderation;
 administrivia; implicit-dest; max-recipients; max-size; news-moderation;
 no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pve-devel-owner@lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Subscribe: <mailto:pve-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pve-devel-leave@lists.proxmox.com>

On Thu, 18 Jun 2026 13:04:33 +0200, Erik Fastermann wrote:
> Ensure that the API token used in `fork_websocket_tunnel` is properly
> prefixed with 'PVEAPIToken=' if it isn't already.
> 
> Previously, if a token was supplied without this explicit prefix,
> initial API checks would pass successfully, but QEMU and LXC
> migrations would abruptly fail midway with the error "server didn't
> upgrade: 401 Unauthorized" when attempting to establish the websocket
> tunnel. This inconsistency created a confusing user experience, as the
> migration appeared to work fine initially.
> 
> [...]

Applied, thanks!

[1/1] tunnel: websocket: prepend api token name when missing
      https://git.proxmox.com/?p=pve-guest-common.git;a=commitdiff;h=38f27bab64a27533fb87ef3d7f8d2f81a22d0dab