From 2392f04e0271ebe15e34de9debe9a68cdf0fba2f Mon Sep 17 00:00:00 2001 From: Rustam <74133907+Taov-Russo@users.noreply.github.com> Date: Mon, 22 Jun 2026 16:54:20 +0300 Subject: [PATCH] fix(cli): apply -webCert/-webCertKey on the setting subcommand (#5482) The setting subcommand registers the -webCert and -webCertKey flags but the "setting" case only calls updateSetting(), which ignores cert paths. The flags were silently accepted and discarded, so a fresh panel stayed HTTP-only (no webCertFile/webKeyFile written, "Panel is not secure with SSL", browser ERR_SSL_PROTOCOL_ERROR). updateCert() was reachable only through the separate "cert" case. Call updateCert(webCertFile, webKeyFile) inside the "setting" case when either flag is set, mirroring the "cert" subcommand. saveSetting() already upserts, so this works on a fresh DB. Co-authored-by: taov.rustam Co-authored-by: Claude Opus 4.8 --- main.go | 3 +++ 1 file changed, 3 insertions(+) diff --git a/main.go b/main.go index a2dca3136..e4f6c13dc 100644 --- a/main.go +++ b/main.go @@ -623,6 +623,9 @@ func main() { return } } + if webCertFile != "" || webKeyFile != "" { + updateCert(webCertFile, webKeyFile) + } if show { showSetting(show) }