Bottom Line: If the Network Widget and Web Terminals Fail Together, First Prove Whether the Host Is Healthy Outside the Dashboard
A black network panel plus failed host/app terminals can look like a network failure, but the dashboard itself is already reachable. Before reinstalling anything, separate browser/UI failure from host-service failure.
Test SSH as an Independent Control Path
The current ZimaOS SSH and web-terminal guide supports SSH, the built-in ttyd web terminal and ttydBridge. Enable SSH in Developer Mode and test:
ssh YOUR_ZIMA_USER@ZIMA_IPIf SSH works while the embedded terminals do not, the operating system and network path are alive. Focus on the browser, HTTPS, ttyd/WebSocket path or dashboard services instead of storage or Ethernet hardware.
Test the Per-App Terminal and Browser Console
Open an app's settings and try its terminal button. Then check the browser developer console for blocked WebSocket, certificate or mixed-content errors. MDN explains mixed-content blocking and WebSocket behavior, both of which matter for browser terminals.
HTTPS Is a Useful Diagnostic Branch
If the problem began after enabling HTTPS or changing certificates, test the dashboard from a trusted LAN over the normal supported local URL and compare. The ZimaOS HTTPS troubleshooting guide explains why the dashboard and app endpoints can have separate TLS behavior.
If SSH Also Fails
Then the issue is no longer just an embedded browser terminal. Check the IP shown on the local display, interface state and recent system logs from a directly attached keyboard/monitor if available. The ZimaOS installation and upgrade guide provides the current Developer Mode/terminal context.
