cipherli.st | Ciplerli.st - strong ciphers for NGINX , Apache | Runtime Evironment library

So my stack is running on a Digital Ocean droplet. Initial node.js application is served at https://domain_name.com/. The requests are processed through NGINX reverse proxy to port 3000.

I now have a second application running on port 3001; both instances are running in PM2. The second application is reached by way of https://domain_name.com/cards/.

When this address is accessed it delivers the first page as expected. However when a POST request is placed. to address https://domain_name.com/cards/api_route/. Console in the browser displays a 404 error. This, however, functions perfectly on Localhost node instance.

My sites-enabled 'default' file contains the following location blocks.

I have a digital ocean droplet running Ubuntu 18.04 and inside is is an lxc container. I have two applications in that container.

The first application (a client) lives at /var/www/html and the second one is the NodeJS application that lives at /var/www/my-site/. The Node application inside the container is managed by pm2 and everything seems to be working fine thus far because when I type in curl http://localhost:3000 at the container terminal, I get back the desired output.

Inside the main droplet (not the container) under /etc/nginx/sites-available, I have the following two server blocks - default and my-site.

The first app works fine when I try to access it through the browser via my domain but the NodeJS application returns a 502 Bad Gateway when I try to access it through sub.mydomain.com. pm2 start inside the container tells me that the node application status is online.

Here is my default server block file. This works. When I visit mydomain.com, my site shows up fine.