From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 32A581FF13F for ; Thu, 12 Feb 2026 14:58:23 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C93E210611; Thu, 12 Feb 2026 14:59:09 +0100 (CET) From: Samuel Rufinatscha To: pbs-devel@lists.proxmox.com Subject: [PATCH proxmox-backup 1/1] fix #7311: bin: init proxmox_acme_api in proxmox-daily-update Date: Thu, 12 Feb 2026 14:58:29 +0100 Message-ID: <20260212135829.313029-2-s.rufinatscha@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260212135829.313029-1-s.rufinatscha@proxmox.com> References: <20260212135829.313029-1-s.rufinatscha@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1770904711594 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.258 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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: ZTXNHYA2EDA5PVPA5EOTGDDYQ7JMMLHJ X-Message-ID-Hash: ZTXNHYA2EDA5PVPA5EOTGDDYQ7JMMLHJ X-MailFrom: s.rufinatscha@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: The daily-update binary was missing initialization of the ACME config directory, causing certificate renewal to panic. Fixes: https://bugzilla.proxmox.com/show_bug.cgi?id=7311 Signed-off-by: Samuel Rufinatscha --- src/bin/proxmox-daily-update.rs | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/bin/proxmox-daily-update.rs b/src/bin/proxmox-daily-update.rs index 224103cc..025eb47f 100644 --- a/src/bin/proxmox-daily-update.rs +++ b/src/bin/proxmox-daily-update.rs @@ -6,6 +6,7 @@ use proxmox_router::{cli::*, ApiHandler, RpcEnvironment}; use proxmox_subscription::SubscriptionStatus; use proxmox_sys::fs::CreateOptions; +use pbs_buildcfg::configdir; use proxmox_backup::api2; async fn wait_for_local_worker(upid_str: &str) -> Result<(), Error> { @@ -104,6 +105,8 @@ async fn run(rpcenv: &mut dyn RpcEnvironment) -> Result<(), Error> { proxmox_notify::context::set_context(&PBS_CONTEXT); + proxmox_acme_api::init(configdir!("/acme"), false)?; + do_update(rpcenv).await } -- 2.47.3