Admin not found

Identifiers

Field	Value
Type URI	https://echo.labstack.com/pro/problems/admin-not-found
Code	admin_not_found
HTTP status	404

HTTP status	English title
404	Not Found

When it occurs

The requested panel, view or target does not exist or is not available to the signed-in principal. Both cases return the same response with an empty detail, so the response does not tell them apart.

Client handling

Check the path and the target parameters. If you expect access, ask the console’s administrator; the response itself gives no further reason.

Example response

If your application installs a custom handler, the body may differ.

HTTP/1.1 404 Not Found
Content-Type: application/problem+json
Cache-Control: no-store

{
  "code": "admin_not_found",
  "detail": "",
  "status": 404,
  "title": "Not Found",
  "type": "https://echo.labstack.com/pro/problems/admin-not-found"
}

Server correction

Check the mounted prefix, enabled panel and authorization callback. The response hides whether an unauthorized target exists.

Response fields

Admin console

• code (string, always): The stable code above.
• detail (string, always): The console always sends detail. It is often empty and never contains the underlying error.
• status (integer, always): The HTTP status of the response.
• title (string, always): The HTTP status text, such as Conflict, unless the panel supplies its own title.
• type (string, always): The exact type URI above.

Headers:

• Cache-Control (always): no-store. The console sends it on every problem response, along with its usual security headers.

Notes:

• Fields are written in alphabetical order.
• The console rewrites every 404 response to admin_not_found with an empty detail.

Related behavior

See the admin console for access checks, action IDs and audit failures.