← All documentationSearch guides

Diagnose HTTP 403 Forbidden

Identify the rejecting layer before changing permissions or security.

  • All
  • Beginner
  • 1 min read
  • Reference: 101.18.15
  • Reviewed

Before you begin

Failing action, address, timestamp and sanitized response.

Use the controls offered by your installed version and account permissions. This guide describes the workflow; it does not grant additional access.

Follow the steps

  1. Check whether navigation works and only one action fails.
  2. If the session actually expired, sign in and reopen the form.
  3. For persistent failures, correlate application and WAF/server logs with the administrator.
  4. Check authorization, CSRF, ownership and request limits as appropriate.
  5. Retest after a narrow correction.

Check the result

The original action works and the rejecting cause is known.

If something goes wrong

Do not use chmod 777 or disable all WAF rules/authentication as a generic fix.

Prepare useful details for support