From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: applied-series: [PATCH proxmox{,-backup} 0/4] fix #3723: allow using node http proxy for remote connections
Date: Wed, 11 Mar 2026 16:01:49 +0100 [thread overview]
Message-ID: <1773241235.29r0k04i4f.astroid@yuna.none> (raw)
In-Reply-To: <20260211161845.1006528-1-c.ebner@proxmox.com>
with a small follow-up switching the precende in pbs-client around -
since passing in an explicitly configured proxy is opt-in, it makes
sense for that to take precedence over an env variable.
On February 11, 2026 5:18 pm, Christian Ebner wrote:
> 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
>
>
>
>
>
prev parent reply other threads:[~2026-03-11 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 16:18 Christian Ebner
2026-02-11 16:18 ` [PATCH proxmox 1/1] pbs-api-types: remote: add flag to use node proxy for remote connect Christian Ebner
2026-02-11 16:18 ` [PATCH proxmox-backup 1/3] http client: use http proxy from client options if set Christian Ebner
2026-02-11 16:18 ` [PATCH proxmox-backup 2/3] fix #3723: api: remote: optionally use node proxy config for http client Christian Ebner
2026-02-11 16:18 ` [PATCH proxmox-backup 3/3] ui: expose flag to use node's http proxy in remote edit window Christian Ebner
2026-03-11 15:01 ` Fabian Grünbichler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1773241235.29r0k04i4f.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.