Admin Support Guide

• Dashboard: Central hub for managing all livestreams.
• Monitoring: Real-time health metrics (Bitrate, FPS, Viewer Count).
• Administration: User management, system settings, and global branding.

• Check Encoder: Ensure the source (OBS, vMix, or hardware encoder) is sending a stable stream to the RTMP/SRT entry point.
• RTMP Status: Visit the Monitoring page to check if Nginx is receiving the stream.
• Backend Logs: If the stream is active in Nginx but not showing in the dashboard, check the backend logs:

tail -f /root/.gemini/antigravity/scratch/OneSignal/logs/backend.log

This usually indicates an authentication issue or a local browser cache problem.

• Action: Perform a hard refresh (Ctrl+F5) to clear the browser cache.
• Check API: Ensure the backend service is running:

systemctl status onesignal-backend

If a stream cannot be rewound:

• Feature Flag: Check the stream's settings in the database or admin panel. dvr_enabled should be set to 1.
• HLS Proxy: Ensure the HLS proxy is correctly rewriting manifests. Look for errors in nginx/error.log.

• Transcoder Service: Clipping depends on the transcoder_service. Check its status in the logs:

tail -f /root/.gemini/antigravity/scratch/OneSignal/logs/transcoder.log

• Disk Space: Ensure there is enough space in the /tmp and clips/ directories:

df -h

• OBS Sync: If the stream is old, segments might have been offloaded to Huawei OBS. Ensure the obs_sync.py worker is running:

ps aux | grep obs_sync.py

If the system becomes unresponsive, you can restart all core components using the built-in script:

/root/.gemini/antigravity/scratch/OneSignal/scripts/run_background_services.sh

• Nginx Logs: /var/log/nginx/access.log and error.log
• Application Logs: /root/.gemini/antigravity/scratch/OneSignal/logs/
• OBS Sync Logs: /root/.gemini/antigravity/scratch/OneSignal/logs/obs_sync.log