Repository navigation
Troubleshooting
Check whether the service is loading the intended environment file. Validate panel JSON, unique IDs, HTTPS base URLs, and required provider fields. Restart after configuration changes. Check only safe metadata and permissions; do not print secret values.
Pterodactyl Client and Application APIs are separate. User-facing server listing can use the Client API endpoint GET /api/client, while panel-wide listing can require Application API permissions. Use the endpoint and token matching the selected namespace. Do not assume Admin API exists on Pterodactyl 1.x.
Check the installed panel version and confirm that its documented API implements the Admin namespace. A new token cannot add an endpoint that the installed version does not provide. Use APIs supported by that version.
Confirm the provider and credential type. Check expiry, scopes, account permissions, and whether the integration expects a Client key, Application key, generic provider token, or AMP session. Avoid solving every authorization failure by using an unnecessarily powerful key.
Confirm the selected native provider, API version, auth flow, and base path. These APIs are not interchangeable with Pterodactyl. Check the installed version's official documentation and verify the action exists in the deployed MAP build.
Check API prefix handling, method, path capitalization, query parameters, and body format against the vendor docs. Some adapters add prefixes automatically, so avoid duplicating them.
MAP expects a valid HTTPS origin without embedded credentials, query strings, or fragments. Ensure the host resolves from the MAP machine. Loopback, link-local, private, or reserved destinations may be intentionally blocked for SSRF protection.
Check Client API permission, server ID, path parameters, configured Wings hostname, and inline size limits. The signed URL must use HTTPS and an explicitly trusted exact hostname. Do not disable these checks as a first-line fix.
Redirect following may be disabled to prevent credentials being forwarded to another origin. Configure the canonical panel URL and check proxy/login redirects. Do not bypass redirect protections without reviewing the security implications.
Check bind address/port, auth headers, TLS, proxy route, and streaming compatibility. A non-loopback HTTP deployment may require a token at startup. For stdio, check the command path and virtual environment configured in the MCP client.
Search existing issues. Include MAP version/commit, OS/Python, provider and panel version, tool name, sanitized path, status code, and redacted logs. Never attach API keys, cookies, signed URLs, or private keys.