FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login
    1. Home
    2. rickberon
    R
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 1
    • Best 0
    • Controversial 0
    • Groups 0

    rickberon

    @rickberon

    0
    Reputation
    1
    Profile views
    1
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    rickberon Unfollow Follow

    Latest posts made by rickberon

    • RE: Error 403 with Nginx in front

      The Nginx 403 Forbidden error occurs when a client attempts to access a section of the webserver without adequate permissions. When Nginx accesses a directory, it attempts to generate an index of its files and present them to the browser or client. However, the default configuration disables directory indexing, leading to the display of the 403 forbidden error instead.

      Incorrect Index File

      The try_files tries the literal path you specify in relation to the defined root directive and sets the internal file pointer. If you have directory indexing off, and is having this problem, it's probably because the try_files you are using has a directory option:

      location / {
        try_files $uri $uri/ /index.html index.php;
      }
      

      to

      location / {
        try_files $uri /index.html index.php;
      }
      

      Incorrectly set permissions

      This error can also result from files and directories having incorrectly set permissions. In order to resolve this , change the directories permission to 755 and the file permissions to 644 . Make sure that the user running the Nginx process owns the files. For example, set user to www-data:

      sudo chown -R www-data:www-data *
      

      Finally, set the directory and file permissions as:

      sudo chmod 755 {dir}
      sudo chmod 644 {files}
      
      posted in Q&A
      R
      rickberon