> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/common-errors-and-known-issues/is-the-vdo-ninja-server-down.md). # Is the VDO.Ninja server down? Troubleshooting guide for Is the VDO.Ninja server down? in VDO.Ninja and OBS with likely causes and practical fixes. The "V" in VDO.Ninja, in the top left, will go red as an indication that the client cannot talk to the VDO.Ninja server. It will *NOT* try to reconnect automatically, although that is a coming feature I will add eventually. If on mobile and you tab away from the site, the server connection may be lost. If the O is red, then you will need to REFRESH the page to reconnect. I'll fix this hassle eventually. However, if the server goes down, the video stream will NOT stop if it has already started, as the video stream does not go through the server. If the server goes down it just means that no one new can connect to the stream anymore, but if you are already connected, you are fine. I may also fix this in the future, but I don't see the urgency for it. The video stream happens over a direct peer connection. This connection can be pretty unstable as cellular phones are not the most reliable things in the world. If a video stream dies, it is not the server's fault, but a failure of the peers to hold a reliable connection open. Auto-reconnecting does depend on the server though. When connected over a high quality LAN, two devices really should not see their connection fail, but if it happens often, please let me know. There is a **backup server** at if the main VDO.Ninja site ever goes down. --- # 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://docs.vdo.ninja/common-errors-and-known-issues/is-the-vdo-ninja-server-down.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.