> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/fix-a-problem/troubleshoot-live-monitor.md).
# Troubleshoot Live Monitor
Is your live monitor down? Use this guide to troubleshoot.
If you encounter any of the following issues, please read the instructions in this section to attempt to troubleshoot the issue or reach out to our support team via live chat, phone or email.
### No Input/Blank Screen
If the live monitor displays no input or a blank screen, try troubleshooting the issue with the following steps:
1. Check if the recording device is turned on. If not, turn the device on (this could take up to 10 minutes). The photos below display two different models of the recording device, for reference:
2\. If the recording device is on but the live monitor is still not working, ensure the cables are connected correctly; you should have an HDMI cable connected to HDMI port 1 or port 2. Additionally, follow the cord and ensure that it is securely plugged in to your monitor as well.
3\. Reboot the HDMI/VGA adapter (the device shown in the following image). To reboot this device:
* Locate the VGA/HDMI adapter on the cord between the recording device and the monitor.
* Unplug both sides of the cord and wait 20-30 seconds.
If you followed the steps above and the issue still persists, please contact our support team via live chat, phone or email:
* **Live Chat**: Available in the bottom corner of the Solink platform, Help Center, mobile apps, and our website ([solink.com](https://solink.com/))
* **Phone**: 1-888-335-9844
### TurboNAS Login Screen
Please contact Solink Support for assistance if you see a "TurboNAS Login Screen".
### Frozen Cameras
If any cameras are frozen on your live monitor, try the following steps to troubleshoot the issue:
1. Navigate to the **Video** page.
2. Each of your locations display the number of online cameras. Additionally, if you hover over a location, a health indicator displays to inform you of any offline cameras. In the following image, the health indicator is showing that the store has 21 out of 22 cameras online and which camera is offline:
3\. If all cameras are online and your device is online or offline - please contact our support team using the information at the bottom of this section.
If some cameras are offline, please follow the steps in [Troubleshoot Offline Camera](/docs/fix-a-problem/troubleshoot-offline-camera.md).
As always, you can contact our support team with the following methods:
* **Live Chat**: Available in the bottom corner of the Solink platform, Help Center, mobile apps, and our website ([solink.com](https://solink.com/))
* [**Open a Support Ticket**](https://solink.com/contact-us/#ticket)
* **Phone**: 1-888-335-9844
### PDF Guide
Download the following guide for a PDF version of this article.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.solink.com/docs/fix-a-problem/troubleshoot-live-monitor.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.