[BUG] Metrics Collection Continuously Failing - Non-Docker and useSidebar

[FaboulousSan]

Title

Metrics 404 failed

Platform

Website - Firefox

Server Installation Method

Manual Build

Version

1.9.0

Troubleshooting

• I have examined logs and tried to find the issue
• I have reviewed opened and closed issues
• I have tried restarting the application
• I have read Known Issues (Known Issues (Read Before Posting) #296)

The Problem

Metrics Collection Continuously Failing - Non-Docker Installation v1.9.0

Hello, I'm experiencing persistent metrics collection failures on Termix v1.9.0
(manual compilation, non-Docker installation).

Issue:

• Metrics collection fails every 30 seconds for host ID 1
• Frontend shows 404 on GET /metrics/1
• Status endpoint works fine (200 OK on /status/1)
• SSH terminal works intermittently
• File manager operations succeed

Backend Logs (every 30 seconds):

[1:34:08 PM] [WARN] [📊] Failed to collect metrics for host [op:metrics_poll_failed,host:1]
[1:34:38 PM] [WARN] [📊] Failed to collect metrics for host [op:metrics_poll_failed,host:1]
[1:35:08 PM] [WARN] [📊] Failed to collect metrics for host [op:metrics_poll_failed,host:1]

Frontend Console:

⚠️ [WARN] 🌐 [API] Not found: GET /metrics/1

What works:

• /status/1 returns 200 OK
• SSH folders fetch successfully
• SSH terminal connection (intermittent)

Database: Using encrypted SQLite database (db.sqlite.encrypted)

No additional error details are logged about why the SSH connection for
metrics collection fails. Any suggestions for debugging this?

### 2. Bug React Sidebar (Login page error)

React Error on Login Page: useSidebar must be used within SidebarProvider - v1.9.0

Issue:
Persistent React error appearing on login page and after authentication on
Termix v1.9.0 (manual build from source, non-Docker).

Error (repeated in console):

Dashboard operation failed: Error: useSidebar must be used within a SidebarProvider.
    at hh (index-CPmKTuyW.js:629)
    at qre (index-CPmKTuyW.js:766)
    at ZD (index-CPmKTuyW.js:48)

Environment:

• Version: 1.9.0 (release-1.9.0-tag)
• Installation: Manual compilation (npm run build + tsc)
• Frontend build date: Nov 18, 2025
• Tested on multiple browsers (Chrome, Firefox) including private mode
• Error persists after complete cache clear and rebuild

Impact:
Error appears in console but application seems partially functional. However,
it suggests an architectural issue with React context providers.

Steps to reproduce:

Is this a known issue in v1.9.0? Should I try a different version?

### How to Reproduce

1. Access login page
2. Open browser console
3. Error immediately visible

### Additional Context

_No response_