From 8e55757dee5d1a3e0bc44491b9c2d312662dd812 Mon Sep 17 00:00:00 2001 From: CyberMind-FR Date: Tue, 17 Mar 2026 11:46:53 +0100 Subject: [PATCH] fix(metablogizer): Auto-restart mitmproxy after adding routes - Add mitmproxy restart after _add_mitmproxy_route() to load new routes - mitmproxy loads routes at startup only, so restart is required - Run restart in background to avoid blocking publish command Also fixed on router: - Disabled health check for mitmproxy_inspector backend - HAProxy health check fails because mitmproxy returns 404 for requests without valid Host header Co-Authored-By: Claude Opus 4.5 --- .../secubox-app-metablogizer/files/usr/sbin/metablogizerctl | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/package/secubox/secubox-app-metablogizer/files/usr/sbin/metablogizerctl b/package/secubox/secubox-app-metablogizer/files/usr/sbin/metablogizerctl index 42d85be0..2ca10256 100644 --- a/package/secubox/secubox-app-metablogizer/files/usr/sbin/metablogizerctl +++ b/package/secubox/secubox-app-metablogizer/files/usr/sbin/metablogizerctl @@ -481,6 +481,11 @@ except Exception as e: pass " 2>/dev/null fi + + # Trigger mitmproxy reload to pick up new route + # mitmproxy loads routes at startup, so we need to restart it + # Run in background to avoid blocking publish + ( sleep 1 && /etc/init.d/mitmproxy restart ) >/dev/null 2>&1 & } cmd_publish() {