Proxy Pass Fails for Port 3000

Hi there,

The Nginx configuration you’ve provided shows that you’ve set up a reverse proxy specifically for the /login path to pass requests to http://localhost:3000/login. If you want your entire application to be served without specifying the port in the URL, you should set up a more general reverse proxy configuration that handles all paths, not just /login.

You can modify your location block to handle requests to the root of the domain (/) and any other paths accordingly. Here’s an example of how you can adjust your configuration:

server {
    server_name app.domain.com;

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/app.domain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/app.domain.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

    location / {
        proxy_pass http://localhost:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}

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

    listen 80;
    server_name app.domain.com;
    return 404; # managed by Certbot
}

With this setup, any requests to app.domain.com will be passed to http://localhost:3000, where your Node.js application is presumably running.

Here are some additional tips to make sure your setup works correctly:

• Ensure that your Node.js app is configured to listen on the correct port (3000 in this case) and is set up to accept connections from localhost.

• Verify that any firewall running on your server is configured to allow traffic on port 443 for HTTPS and port 80 for HTTP.

• After making changes to your Nginx configuration files, always reload Nginx to apply the changes:

  sudo systemctl reload nginx
  

• If you encounter issues after updating the configuration, check the Nginx error logs for any detailed error messages that could help you troubleshoot the problem:

  sudo tail -f /var/log/nginx/error.log
  

• Ensure that there are no conflicting server blocks for app.domain.com that could be interfering with your reverse proxy setup.

Let me know how it goes!

Best,

Bobby