Home > Error > 401

401 Authorization Required

This server could not verify that you are authorized to access the document requested.

Either you supplied the wrong credentials (e.g. bad password), or your browser doesn't understand how to supply the credentials required.

Authentication flow

client
→
edge
→
resource (401)

The resource refused your request because no valid Authorization header was present, or the token provided was expired, malformed, or revoked.

How to fix it

  1. Sign in with the username and password for this site
  2. If you forgot the password, request a reset on the sign-in page
  3. For API clients, include an Authorization header with valid credentials
  4. If basic-auth is required, your browser will prompt for credentials
  5. If you use a bearer token, verify it has not expired

Example of a valid request

# bearer token
GET /api/v2/me HTTP/1.1
Host: api.example.com
Authorization: Bearer eyJhbGc...<rest of token>
Accept: application/json

Request information

Status:401 Unauthorized
WWW-Authenticate:Basic realm="Restricted"
Method:GET
Request URI:/admin/users
Server:nginx/1.24
Request ID:req_8a92-2f04-bb01
Trace ID:tr_4c91-aa12
Time:Tue, 19 May 2026 14:18:02 GMT
Note: Even valid credentials will not grant access if the account doesn't have the right role — in that case the server returns 403 Forbidden instead.
For developers: Make sure you store tokens securely and refresh them before expiry. Long-lived tokens should be avoided where possible.

Quick links

Sign in Create account Forgot password API docs Help

server — Linux — IPv4/IPv6 — TLS 1.3