serving flask app using gunicorn + nginx showing 404 [ec2]

Question

I am trying to serve a simple API by following this digitalocean tutorial. For testing I was earlier serving the API through gunicorn by doing a ``` $ gunicorn --bind 0.0.0.0:5000 trumporate.wsgi:app ``` And curling the API endpoint works inside the ec2 box ``` $ curl -X GET http://0.0.0.0:5000/api/v1/trump/rant/ { "foo": "bar" } ``` Now I shifted this gunicorn process to run at startup by making a systemd service ``` # /etc/systemd/system/trumporate.service [Unit] Description=Gunicorn instance for trumporate After=network.target [Service] User=ubuntu Group=www-data WorkingDirectory=/var/opt/trumporate ExecStart=/usr/local/bin/gunicorn --workers 3 --bind unix:trumporate.sock -m 007 --access-logfile /var/log/trumporate/gunicorn-access.log --error-logfile /var/log/trumporate/gunicorn-error.log trumporate.wsgi:app [Install] WantedBy=multi-user.target ``` I have created the files - `/var/log/trumporate/gunicorn-error.log` - `/var/log/trumporate/gunicorn-access.log` and changed the ownersh…

Accepted Answer

Did you do `nginx -s reload && systemctl restart nginx`?

Another thing which you could try is to make the bindings on a http port instead of a socket:

```
--bind 127.0.0.1:6767 #in systemd config
```

and change nginx config as follows:

```
location / {
    include proxy_params;
    proxy_redirect off;
    proxy_pass http://127.0.0.1:6767;
}
```

Also why do you have private_ip in nginx config?

```
server_name private_ip_address;
```

Change that to

```
server_name "_";
# OR
server_name PUBLIC_IP;
```

and remove all default configs from `/etc/nginx/site-enabled`

1) use of server_name private_ip_address;?

Nginx uses the server_name to check with the host header of the incoming request, and that isn't the private address. (You usually access using either a domain name or the public address in the URL bar)

2) I deleted /etc/nginx/site-enabled/default dir to make things to get to working.

If your server_name is not set correctly, nginx processes the request using the default file or the server block containing `default_server`. Thus I asked you to delete that file just in case there was an issue with your server name ^_^

Also, what difference would it make to the performance of the API if I am binding it to a port instead of the socket file as suggested by the blog post?

This would typically be premature optimization, any difference you get will purely be within a margin of error compared to the bottlenecks caused by flask/python and especially database connections. Though please take this with a grain of salt as I do not have any reliable source to quote this on.

serving flask app using gunicorn + nginx showing 404 [ec2]

Solution

Problem