Tutorial — Troubleshooting 403 error

Edit on GitHub

A website functionality is not working properly, or there is a 403 status response code in the frontend logs.

Checking errors via browser console

To check 403 errors via browser console, do the following:

  1. In the page you want to check for errors, right-click and select Inspect.
  2. In the navigation bar of the inspect pane, switch to the Network tab.
  3. Search by the status code of the needed error, for example 403.

Checking the WAF rule that triggered the 403 error

If you found a 403 status response code in the frontend logs or in the browser console, it is most likely that it had been triggered by a WAF(web application firewall) rule. Knowing the rule that triggered the error will help you to understand the source of the issue.

To check the WAF rule that triggered the error, do the following:

  1. In the AWS Management Console, go to Services > S3.
  2. In the Buckets pane, select the WAF bucket of the desired environment.


  1. According to when the error occurred, navigate to the respective folder by year > month > day > hour.


  1. Based on the date and time in Last modified column, select the needed log file.


  1. To download the file, select Download.

  2. Open the file in an editor and find the triggered WAF rule by the following parameters:

  • clientIp
  • "action":"BLOCK"
  • uri
  • requestId

An example of a blocking request from the WAF log file:

{"clientIp":"85.90.*.*","country":"UA","headers":[{"name":"host","value":"SITE_URL"},{"name":"user-agent","value":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:94.0) Gecko/20100101 Firefox/94.0"}],