Setting up an NGINX server to route requests to a node server without a specified path

Question

Setting up an NGINX server to route requests to a node server without a specified path

I have a server running Nginx with the following setup:

server
{
    listen 80;
    server_name example.ca www.example.ca;
    location / {

proxy_pass http://127.0.0.1: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;
}
}

On the Node server, I am listening on port 3000 using Node Express as follows;

app.get('*', function (req, res) {
  console.log('Request received ', req.headers.host);
});

I also have a domain www.example.com pointing to the IP of the Nginx server. The tests I am conducting are:

http://www.example.com/test result ===> Request received www.example.com

http://www.example.com/test/abc result ===> Request received www.example.com

http://www.example.com result ===> (I get no result !! It's like the app.get did not trigger)

Can anyone help me with this issue? When I visit the domain without any path parameter, I'm not receiving any result. It seems like Nginx is not forwarding this request to the node server!!

node.js express nginx nginx-location proxypass

Answer 1

Answer №1

When accessing abc.com through a browser or using curl, the path will always be sent as /. It is not possible to send a blank path.

Your nginx configuration seems to be set up for a socket.io implementation and should look like this:

server
{
    listen 80;
    server_name example.ca www.example.ca;
    location / {
       proxy_pass http://127.0.0.1:3000;
       proxy_http_version 1.1;
       proxy_set_header Host $host;
    }
}

If you are not ending your requests properly, they may time out. Make sure your code looks like this:

app.get('*', function (req, res) {
  console.log(' request received ', req.headers.host);
  res.status(200).send("all ok");
});

For troubleshooting purposes, you can use curl like so:

curl -v http://www.example.com

Answer 2

When accessing abc.com through a browser or using curl, the path will always be sent as /. It is not possible to send a blank path.

Your nginx configuration seems to be set up for a socket.io implementation and should look like this:

server
{
    listen 80;
    server_name example.ca www.example.ca;
    location / {
       proxy_pass http://127.0.0.1:3000;
       proxy_http_version 1.1;
       proxy_set_header Host $host;
    }
}

If you are not ending your requests properly, they may time out. Make sure your code looks like this:

app.get('*', function (req, res) {
  console.log(' request received ', req.headers.host);
  res.status(200).send("all ok");
});

For troubleshooting purposes, you can use curl like so:

curl -v http://www.example.com

Setting up an NGINX server to route requests to a node server without a specified path

Answer №1

Similar questions

NPM - Include in package.json without installation

Repetitive NodeJS event triggers within Electron-React application causing unexpected behavior

What is the true purpose behind the existence of package-lock.json and shrinkwrap?

I am currently in the process of verifying email addresses

Exploring the power of Mongoose geolocation queries

The fetch() POST request is met with an error message stating "415 Unsupported Media Type"

JavaScript encounters a parsing error when dealing with an async function

Is it possible to exclude certain static files from being served in express.static?

The property is returning an empty string, but the function is functioning perfectly

Encountering "environment.prod.ts path does not exist in file replacements" error while Dockerizing Angular build

What are the specific purposes of utilizing semantic versioning (semver) notation within the package.json file?

Module-alias cannot be resolved by esm

Removing a specific MongoDB document by its ID within an Express.js application

Creating a system for admin approval of blog posts in a node.js and express application

Tips for extracting and mapping a sub array from the category response JSON using SWR with MongoDB in a Next.js (Node.js) environment

Totally at a standstill. (Problem with MongoDB in my MERN stack)

Having trouble with mongoose-paginate and react using material-ui's TablePagination component? Encountering issues where the second page onwards does not render after

Strategies for resolving the nodejs $lte endpoint variable issue

Deployment failure due to undetected development keys in gitignore

FirebaseCloudMessaging : PlatformException (PlatformException(null-error, The host platform unexpectedly returned a null value for a non-null return value., null, null))