How to keep Nginx upstream for ExpressJS routes? - node.js

Question

I have an express app with two routes: an index route (/) and an article route (/article).
Now I try to deploy this application on an Ubuntu server behind a Nginx.
The problem I have is that the index route available at https://servername/app works fine, however, if I am entering a route (starting from index) via the upstream /app is lost and I am routed to https://servername/article/param which clearly is not available as I would like to be routed to https://servername/app/article/param.
It works smoothly on my local computer where no upstream/Nginx is interposed.
My Nginx config looks as follows:
upstream app {
server localhost:3000;
}
server {
#listen [::]:80 default_server ipv6only=on;
#root /usr/share/nginx/html;
# index index.html index.htm;
# Make site accessible from http://localhost/
server_name example.test.at;
#Enable the verification for letsencrypt
location /.well-known {
root /usr/share/nginx/html;
}
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_pass http://127.0.0.1:8080;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
# try_files $uri $uri/ noen;
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/example.test.at/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/example.test.at/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
location ~^\/(images|stylesheets|fonts|javascripts) {
expires 1M;
access_log off;
add_header Cache-Control "public";
add_header Access-Control-Allow-Origin *;
add_header Access-Control-Allow-Methods GET;
add_header Access-Control-Allow-Headers X-Requested-With,content-type;
add_header Access-Control-Allow-Credentials true;
root /var/www/webviews/app/public;
}
location ^~ /app {
#rewrite ^/noen(/.*)$ $1 break;
proxy_pass http://app/;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
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 $scheme;
}
}
server {
if ($host = example.test.at) {
return 301 https://$host$request_uri;
} # managed by Certbot
listen 80 ;
server_name example.test.at;
return 404; # managed by Certbot
}
Do you see any issues in my Nginx config?

Answer 1

I missed a location section for the article, where the (.*) handles the param (subpath):
location ~^/article/(.*) {
proxy_pass http://noen;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
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 $scheme;
}