Memory 019eafd2

Memory ID (Session ID): 019eafd2-22bd-7000-abc8-8b7f05ab29af
Last Updated: 2026-06-10 06:54:13

Fact Summary

• System Architecture: Nginx is configured as an SSL (HTTPS) reverse proxy using htpasswd for basic authentication to secure telemetry/dashboard endpoints (e.g., port-19030|Langfuse Dashboard)]]).
• Service Persistence: Agentic and dashboard processes are managed as systemd user services (pi-dashboard.service, omp-stats.service), requiring loginctl enable-linger and systemctl --user enable to ensure they persist across reboots.
• Pitfall (pi-langfuse telemetry 400 error): The pi-langfuse extension cached its config.json (host URL) in memory on startup. When the target port was wrapped in an Nginx SSL proxy, the active session continued sending plain HTTP requests to the newly secured HTTPS port, resulting in Nginx throwing 400 The plain HTTP request was sent to HTTPS port.
• Resolution (Code Patch): The pi-langfuse extension source code (dist/index.js) was patched to skip in-memory caching and dynamically hot-reload the configuration from ~/.pi/agent/pi-langfuse/config.json on every session boot. A full /restart in the OMP terminal is required to flush the Node/Bun process memory after such architectural changes.

Reference Session

• Associated Chat Session: 019eafd2-22bd-7000-abc8-8b7f05ab29af