It's B

Category: Nginx

  • Fix 413 Request Entity Too Large in MaMP in 2 Minutes

    Fix 413 Request Entity Too Large in MaMP in 2 Minutes

    Video for who doesn’t like to read ;). And if you like the video then subscribe my channel and share this with others who has the same issue.

    When I was working on the local development, I had an issue as shown in this post image.

    When I tried to import a database from PHPMyAdmin, I was having the error “413 Request Entity Too Large“.

    After searching a bit on the internet, I found a very simple solution. It would take only a couple of minutes.

    So as this is nginx related error, open your Nginx config file. In my case, I was using MaMP. So my nginx.conf file was at this location:

    /Applications/MAMP/conf/nginx/nginx.conf

    Open the file and add the following lines into http { } section as shown in below image:

    client_max_body_size     1000M;
fastcgi_read_timeout     3600;

    11

    After adding that line, try to restart Nginx.

    In my case, I had a button to restart the server in MaMP. You might run the command like service nginx restart

  • Fix – upstream sent too big header while reading response header from upstream in Nginx

    For this fix please visit below link.

    https://bhargavb.wordpress.com/2020/02/28/fix-404-error-on-nginx/

  • Fix 404 error on nginx

    Fix 404 error on nginx

    Sometimes you get unexpected 404 error from Nginx server. And I am going to tell you how I fixed the issue.

    You can fix that easily by the following steps:

    Step 1 (Debugging):

    You first need to find out the reason. For that, you can the first login to your server via ssh and check the error log for Nginx server.

    Open the following file: /var/log/nginx/error.log and check the latest errors.

    In my case I was having the following error:

    2020/02/28 08:19:02 [error] 17627#17627: *14299 upstream sent too big header while reading response header from upstream, client: 172.31.4.43, server: yoursite.com, request: "GET /wp-login.php?action=switch_to_user&user_id=2928&nr=1&_wpnonce=9085bda773&redirect_to=https%3A%2F%yoursite.co%2Fmembers%2Fdesigner-buddyboss%2F HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.1-fpm.sock:", host: "yoursite.co", referrer: "https://yoursite.co/members/designer-buddyboss/"

    Step 2 (Solution):

    After exploring on google I found this solution which worked for me. We need to add the following lines into the Nginx config file:

    client_max_body_size 128m;
fastcgi_buffers 16 16k;
fastcgi_buffer_size 32k;

    Now the following file could be responsible for your site:

    Check if this file available /etc/nginx/sites-enabled/your_site.conf ( This was the responsible file in my case )

    OR

    /etc/nginx/sites-available/your_site.conf

    OR

    /etc/nginx/sites-available/nginx.conf

    Open one of the files.

    Step 3 (Apply Solution):

    Now add those 3 lines into the config file like this

    After adding this restart Nginx server by the following command:

    sudo service nginx restart

    That’s it!!!!