>_ IzzyLab

Topic breakdown

An HTTP 403 with nginx running and a valid config almost always means the worker process (running as a user like www-data) can't read the site's files — look in the filesystem, not the config. The failure point is shown by error.log: a Permission denied entry with the specific path. Permissions are checked along the whole chain: a directory needs the x bit to be traversed, and a file needs the read bit r; a common mistake is to fix only the file and forget the directory (or vice versa). The tool for fixing permissions is chmod.

What's checked

  1. Home page returns 200
  2. the original site page is served
  3. permissions aren't opened for writing by everyone

What it looks like