From e3f673ecb948b11da550f1b70b3f32de2199b05d Mon Sep 17 00:00:00 2001
From: officer <noreply@officer.dev>
Date: Wed, 19 Aug 2026 09:09:07 +0000
Subject: [PATCH] log why the frame fetch failed

'gitea unreachable' on its own is not a diagnosis. The sidecar was answering
200 to a direct curl while the panel showed that message, which sent the search
to the wrong half of the system twice.
---
 api/router.ts | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/api/router.ts b/api/router.ts
index 2bd4cf8..ea9bfe8 100644
--- a/api/router.ts
+++ b/api/router.ts
@@ -98,7 +98,10 @@ router_.all('/_web/*', async (ctx) => {
       redirect: 'manual',
     });
     return new Response(upstream.body, { status: upstream.status, headers: upstream.headers });
-  } catch {
+  } catch (err) {
+    // Logged, not swallowed. "unreachable" on its own sent two people to the wrong half of the system:
+    // the sidecar was answering 200 to a direct curl the whole time, and the failure was here.
+    console.error(`[gitea] frame ${method} ${subpath} -> ${sidecar} failed:`, err);
     return ctx.text('gitea unreachable', 502);
   }
 });