Nginx default page showing. Cannot get app to display - django

Question

first time Nginx user. Trying to connect Nginx to Gunicorn running a django app. The app is not actually written yet so once everything is configured, it would just display an under construction page.
I can't seem to get the Nginx configuration correct to pass requests on to Gunicorn then to Django. Instead it always shows the Nginx default page. Greatly appreciate any help!
Here is /etc/nginx/sites-available/mysite:
server {
listen 80;
#server_name <server IP>;
server_name <mysite.com>;
location = /favicon.ico { access_log off; log_not_found off; }
location /static/ {
root /home/<my user acct>/<my app>/<my site>;
}
location / {
include proxy_params;
proxy_pass http://unix:/home/<my user acct>/<my app>/<my site>/<my site>.sock;
}
}
Here is /etc/nginx/sites-available/default:
##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##
# Default server configuration
#
server {
listen 80 default_server;
listen [::]:80 default_server;
# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuration.
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;
root /var/www/html;
# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
#server_name <mysite.com> <www.mysite.com>;
#server_name localhost;
server_name _;
#server_name <server IP>;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php7.0-cgi alone:
# fastcgi_pass 127.0.0.1:9000;
# # With php7.0-fpm:
# fastcgi_pass unix:/run/php/php7.0-fpm.sock;
#}
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<mysite.com>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<mysite.com>/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
# listen 80;
# listen [::]:80;
#
# server_name example.com;
#
# root /var/www/example.com;
# index index.html;
#
# location / {
# try_files $uri $uri/ =404;
# }
#}

Answer 1

i think you should delete the default configuration in sites available and your sites available configuration should be within the sites enabled directory as well.
/sites-available/
|
|-> site.com
|-> site2.com
|-> disabled.com
/sites-enabled/ **this links to the files in /sites-available**
|
|-> site2.com
|-> site2.com