# Troubleshooting: Hardware & integrations

> Deck, database and agents.

Glider documentation · Reference · Web page: https://cgglider.com/docs/troubleshooting/hardware/

Sections of this page: [Editor](https://cgglider.com/docs/troubleshooting.md) · [Data & bindings](https://cgglider.com/docs/troubleshooting/data.md) · [Output](https://cgglider.com/docs/troubleshooting/output.md) · [Hardware & integrations](https://cgglider.com/docs/troubleshooting/hardware.md)

| Symptom | Cause and fix |
| --- | --- |
| The Stream Deck is not detected | Elgato's own software may own the device; or GLIDER_STREAMDECK=0 is set. The server logs “[streamdeck] not started”. |
| “Cannot find native binding” | A native module was bundled. It must stay in serverExternalPackages. |
| A deck key shows a warning marker | Its binding outlived its target — the page, unit or clip is gone. |
| Chat history is unavailable | MongoDB is down. Pages still work. In the desktop app, restart it; mongod.log in the app's log folder says why its database stopped. |
| The selected agent is locked | Glider can't find its CLI on PATH or in the installer's folder. Run the two commands on the card (PowerShell on Windows), then Check again. GLIDER_LOCAL_AGENTS=0 hides every CLI. |
| A probe fails with “Unknown secret” | The poller references a secret this page does not have. |
| Another machine on the LAN loads /editor but nothing is interactive | Dev-mode cross-origin requests are only allowed from the configured origins. |