> For the complete documentation index, see [llms.txt](https://prisma-logs.gitbook.io/prisma-logs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prisma-logs.gitbook.io/prisma-logs/docs/en/help/troubleshooting.md). # Troubleshooting ## Invalid license key or ip ``` [ERROR] Server shutting down, invalid license key or ip.. ``` * Is the IP correct in the panel under **Settings**? It must be the IP your FiveM server connects from, without the port. * Is your license still valid? Check **My servers**. * Did you download the resource from the right server? Every server has its own key. ## The resource starts, but no logs come in * Is `ensure prisma-logs` in `server.cfg` and do you see `[SUCCESS] Prisma Logs successfully started!`? * Is the category turned on in `Shared.AutoLogs`? * Deaths and vehicles only work with `ensure baseevents`. * Do you see `Sending ... logs failed`? Then the panel can't be reached. The logs are kept and sent later. ## The scan stays on "Scan pending..." After 2 minutes it cancels itself with a message. Usually an old version of the resource is running. Download it again under **Settings**, replace the folder and restart. ## A script isn't logged * Is it encrypted? Then it's listed in the console under `Encrypted (escrow) scripts that cannot be scanned`. * Is the action turned off under **Actions**? * Is the script in `Shared.ScanIgnoreResources`? * Otherwise log it with [your own events](/prisma-logs/docs/en/configuration/custom-events.md). ## "... fires very often, skipping logs this minute" An action happens more than 30 times a minute. Turn it off under **Actions** or raise `Shared.ScanMaxPerMinute`. ## My log doesn't show up in the panel (export) * Does a category with exactly that name exist? * Do you use the export server side? * Is `ensure prisma-logs` above your script in `server.cfg`? --- # 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://prisma-logs.gitbook.io/prisma-logs/docs/en/help/troubleshooting.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.