From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 7C6AA1FF13B for ; Wed, 11 Feb 2026 17:18:26 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 38EE832D5D; Wed, 11 Feb 2026 17:19:12 +0100 (CET) From: Christian Ebner To: pbs-devel@lists.proxmox.com Subject: [PATCH proxmox{,-backup} 0/4] fix #3723: allow using node http proxy for remote connections Date: Wed, 11 Feb 2026 17:18:41 +0100 Message-ID: <20260211161845.1006528-1-c.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 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: 1770826655266 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.048 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: IOZJHKM6DVREYE5JOCEBYR6VJUUITEYQ X-Message-ID-Hash: IOZJHKM6DVREYE5JOCEBYR6VJUUITEYQ X-MailFrom: c.ebner@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 Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: These patches allow setting a boolean flag on a remote's configuration to control whether or not to use the http proxy settings of the Proxmox Backup Server node for the connection. The default remains to not use the node's proxy, guaranteeing full backwards compatibility. If no http proxy is configured, the flag has no effect and no proxy will be used. Currently it is only possible to set a custom per-remote proxy setting, which can however be easily added on-demand. Note: Testing was performed using https://www.mitmproxy.org/ Fingerprint on the PBS remote must then match the one provided by the proxy, the proxy must be started with `--ssl-insecure` if self-signed certificates are use on the remote. Link to the issue in the bugtracker: https://bugzilla.proxmox.com/show_bug.cgi?id=3723 proxmox: Christian Ebner (1): pbs-api-types: remote: add flag to use node proxy for remote connect pbs-api-types/src/remote.rs | 14 ++++++++++++++ 1 file changed, 14 insertions(+) proxmox-backup: Christian Ebner (3): http client: use http proxy from client options if set fix #3723: api: remote: optionally use node proxy config for http client ui: expose flag to use node's http proxy in remote edit window pbs-client/src/http_client.rs | 9 +++++++++ src/api2/config/remote.rs | 13 +++++++++++++ src/config/node.rs | 5 +++++ www/window/RemoteEdit.js | 19 +++++++++++++++++++ 4 files changed, 46 insertions(+) Summary over all repositories: 5 files changed, 60 insertions(+), 0 deletions(-) -- Generated by murpp 0.9.0