Free tools

HTTP 403 Forbidden

The server understood the request and refuses it. Free reference, no signup.

403 Forbidden

MeaningThe server understood the request and refuses it.
WhenThe caller is authenticated but is not allowed to do this.
CausesA permission check, an IP allow list, or a suspended account.
FixChange the permission or stop calling that route. A new password will not help if the role is wrong.
RetryDo not retry the same call.
Alert?Usually no. Alert on a sudden spike of 403s from your own jobs.

Runs in your browser. Nothing you enter is stored.

Most 403s are not an incident

Alert on a sudden spike of 403s from your own jobs.

curl -sS -X POST https://api.trigv.com/v1/events \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $TRIGV_API_KEY" \
  -d '{"channel":"ops","title":"HTTP 403","level":"warning"}'
Get an API key All status codes

How to use it

  1. Read what 403 means before changing a retry loop.
  2. Check the common causes against the response body and the server log.
  3. Follow the retry note. Retrying a 400 with the same body will fail again.
  4. Alert only in the cases the verdict describes.

About this tool

HTTP 403 Forbidden means The server understood the request and refuses it. Servers send it when The caller is authenticated but is not allowed to do this.

Common causes: A permission check, an IP allow list, or a suspended account. The practical fix is: Change the permission or stop calling that route. A new password will not help if the role is wrong.

Retry: Do not retry the same call.

Alert on it? Usually no. Alert on a sudden spike of 403s from your own jobs.

Trigv is a push for the moment a status starts mattering, not a log of every response. If the code is one you should hear about, the snippet posts a single event with level error or warning. The status page itself does not call your API.

Questions

What is HTTP 403?

The server understood the request and refuses it.

Should the client retry?

Do not retry the same call.

Should I alert on it?

Usually no. Alert on a sudden spike of 403s from your own jobs.

How is this different from reading the spec?

The page adds a plain retry note and an alert verdict for people running the service, not only for people parsing the response.

400 Bad Request The server could not understand the request. 401 Unauthorized The request is missing valid authentication. 404 Not Found The server has no resource at this URL. Cron Job Alert Script Wrap a command so a failed, slow, or finished cron job sends a Trigv alert.