some_available_site configuration file for nginx, result of some research and certbot generated configuration

some_available_site

server {
        root /opt/www;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html;

        server_name your_server www.your_server;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ =404;
        }

        location /some_app {
                alias /opt/some_app/www;
                try_files $uri$args $uri$args/ /some_app/index.html;
        }
        
    listen [::]:443; # not managed by Certbot 
    ssl on; # not managed by Certbot
    listen 443 ssl; # managed by Certbot
    
    ssl_certificate /etc/letsencrypt/live/your_server/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/your_server/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

}

server {
    if ($host = www.your_server) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    if ($host = api.your_server) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    if ($host = your_server) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    listen 80 default_server;
    listen [::]:80 default_server;

    server_name your_server www.your_server api.your_server;
    return 404; # managed by Certbot

}

Configuration included in article posted at https://medium.com/@JSantaCL/nginx-nodejs-and-spas-cc50c376b131