# Fixing the 'Cannot GET' error in Node.js applications

> Fix the 'Cannot GET' error in a Node.js Selector app by checking your routes, startup file and application root.

Source: https://helpcenter.ruachost.com/cpanel/software/node-js-application-error-message-cannot-get-url/

When running a Node.js  application through the **Node.js  Selector in cPanel**, you may encounter the error:

This means the application received a request for a URL path, but no route was defined to handle it.

## Common Causes

- **Missing Route Definition** → The requested URL path is not defined in your application code.
- **Incorrect Startup File** → The file specified in the Node.js  Selector (e.g., `app.js` or `server.js`) does not contain the correct routing logic.
- **Wrong Application Root** → Files are not located in the directory set as the application root.
- **Port or Path Issues** → The app is listening on a port or path that doesn’t match the request.

## How to Fix

### 1. Verify Routes

Make sure your application defines routes for the requested URL. Example using **Express.js**:

```
const express = require('express');
const app = express();

app.get('/', (req, res) => {
  res.send('Hello World!');
});

app.get('/myapp', (req, res) => {
  res.send('This is my app route.');
});

app.listen(3000, () => {
  console.log('App running on port 3000');
});
```

If you visit `/myapp`, the app must have a corresponding `app.get('/myapp', ...)` route.

### 2. Check Startup File

- In **cPanel → Setup Node.js  App**, confirm the **Application Startup File** points to the correct file (e.g., `app.js` or `server.js`).
- Ensure this file contains the routing logic.

### 3. Confirm Application Root

- Verify that your app files are inside the directory specified as the **Application Root** in Node.js  Selector.
- If files are in a subfolder, update the root path or move them accordingly.

### 4. Restart the Application

- After making changes, restart the app from **Node.js  Selector → Restart App**.
- This reloads the configuration and applies your fixes.

> **Note:**
- The error is **not a server issue** , it’s caused by missing or incorrect routing in your code.
- Always test routes locally before deploying.
- Use **Error Logs** in cPanel to identify additional issues.