Looks good for me.
You could check does you have some redirect server block enabled.
Enabled block are stored in /etc/nginx/sites-enabled. You can see list of enabled by doing ls:

ls /etc/nginx/sites-enabled

Check does you enabled this block too.
Sites are enabled by symlinking them from sites-available to sites-enabled:

sudo ln -s /etc/nginx/sites-available/block_name /etc/nginx/sites-enabled/

Make sure this is only block that have default_server for listen 80, as only one is allowed.

You can make one block of these two, like this:

server {
    listen 80 default_server;
    listen [::]:80 default_server;
    listen 443 ssl;
    server_name example.com; # Replace with your domain

    root /usr/share/nginx/html;
    index index.html index.htm;

    ssl on;
    ssl_certificate cert location;
    ssl_certificate_key key location;

    client_max_body_size 10G;

        location / {
        proxy_pass http://localhost:2368;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_buffering off;
    }
}

Please make sure you change highlighted values with real ones.

Save that and test nginx config:

sudo nginx -t

Make sure you restart nginx after changes!:

sudo systemctl restart nginx

Try now to access it. If problem persist, clear cache or try another browser/incognito.

If you are running Ruby on Rails, there is a chance that the “config.force_ssl = true” value is set. That alone will force HTTP to redirect to HTTPS.

To solve this, navigate to your Ruby on Rails site

cd /path/to/#{your_site}/current/config/environments

and edit any file in there that is active (I did them all in my case since I am deliberately eliminating SSL from my Chef cookbook since SSL termination will occur at the load balancers.

The particular line to search for will be like this:

config.force_ssl = true

Change that line to this:

config.force_ssl = false

For me, it ended up being a URL Redirect DNS that I had put in place and completely forgot about. It redirected @ to https://www.<domain>.com. If NGINX isn’t redirecting, maybe something else in the pipeline is.