Subdomain with Nginx example below not working

[ademir10]

Hi guys! I'm trying to find some example about to make a simple subdomain Nginx config but unfortunately i can't find any example to make it works in my project.

Basically i have a subdomain: bola.mytab.com.br
running in a custom port using this command:
rails lift --prod --port 3012

and after to install my certbot in a available sites with the same name: bola.mytab.com.br i also configured my nginx file this way:
could you help me please? thank you so much!

upstream app {
server http://127.0.0.1:3012;
}
server {

    server_name bola.mytab.com.br;
location /app/ {
     proxy_pass http://127.0.0.1:3012;
     proxy_set_header X-Real-IP $remote_addr;
     proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
     proxy_set_header X-Forwarded-Proto https;
     proxy_set_header X-Forwarded-Server $host;
     proxy_set_header Host $http_host;
     proxy_redirect off;
    }

    error_page 500 502 503 504 /500.html;
    client_max_body_size 4G;
    keepalive_timeout 10;

listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/bola.mytab.com.br/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/bola.mytab.com.br/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 = bola.mytab.com.br) {
return 301 https://$host$request_uri;
} # managed by Certbot

    listen 80;
    server_name bola.mytab.com.br;
return 404; # managed by Certbot

}

[sailsbot]

@ademir10 Thanks for posting! We'll take a look as soon as possible.

In the mean time, there are a few ways you can help speed things along:

• look for a workaround. (Even if it's just temporary, sharing your solution can save someone else a lot of time and effort.)
• tell us why this issue is important to you and your team. What are you trying to accomplish? (Submissions with a little bit of human context tend to be easier to understand and faster to resolve.)
• make sure you've provided clear instructions on how to reproduce the bug from a clean install.
• double-check that you've provided all of the requested version and dependency information. (Some of this info might seem irrelevant at first, like which database adapter you're using, but we ask that you include it anyway. Oftentimes an issue is caused by a confluence of unexpected factors, and it can save everybody a ton of time to know all the details up front.)
• read the code of conduct.
• if appropriate, ask your business to sponsor your issue. (Open source is our passion, and our core maintainers volunteer many of their nights and weekends working on Sails. But you only get so many nights and weekends in life, and stuff gets done a lot faster when you can work on it during normal daylight hours.)
• let us know if you are using a 3rd party plugin; whether that's a database adapter, a non-standard view engine, or any other dependency maintained by someone other than our core team. (Besides the name of the 3rd party package, it helps to include the exact version you're using. If you're unsure, check out this list of all the core packages we maintain.)

---

Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.

For help with questions about Sails, click here.