Fresh install on Raspberry Pi 4 fails with "Cannot GET /" #1116
-
| 
         Hello, I'm trying to do a fresh installation on a Raspberry Pi 4 to control my Pentair system. I'm following the standard installation steps, but after running npm start, the web page shows a "Cannot GET /" error. Here is what I have already tried: Confirmed the rs485Port is set correctly to /dev/ttyUSB0 in config.json. Manually ran npm run build before npm start. Deleted the node_modules and dist folders and ran a full npm install again. Even after a completely clean installation, the problem persists. It seems like the web page files are not being built or served correctly. Can you offer any advice?"  | 
  
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
| 
         This app, njsPC, runs on port 4200 and has API endpoints. dashPanel has the web UI and runs on port 5150.  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Thank you for the corrections. The application starts and the log shows 'Configuration Complete' and I can see RS485 stats, so the communication is working. However, the dashPanel web server on port 5150 never starts, and the page cannot be reached. I have confirmed that dashPanel is enabled in my config.json file. Here is my startup log: 
 
 Init state for Pool Controller Thank you for any help you can provide.  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Thank you for the help! I am able to get everything up and running but once I run the pm2, I start having connection issues. Details below, any suggestions? The njsPC backend and dashPanel frontend work perfectly when I run them manually in separate terminals using npm start. However, when I manage dashPanel with pm2, the service shows a status of online, but I cannot connect from a browser and get an ERR_CONNECTION_REFUSED error. What Works: njsPC connects to my IntelliCenter panel and the log shows "Configuration Complete." dashPanel loads and is fully functional at http://:5150 when I run npm start manually. What Fails: When dashPanel is started via pm2, the browser connection is refused. The pm2 logs dashPanel command shows that the log files are empty, indicating the app is crashing silently and getting stuck in a restart loop. My pm2 Status (shows everything "online"): ┌────┬───────────┬───────────┬────────┬──────┬───────┬────────┬───┬──────────┬──────┬─────────┬────────┬──────────┐ JavaScript module.exports = { Device: Raspberry Pi 4 OS: Debian (Raspberry Pi OS) Node.js Version: v22.17.1 (installed via nvm) Any suggestions would be greatly appreciated. Thank you!  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Thank you again for all the help! It is up and running now, no issues.  | 
  
Beta Was this translation helpful? Give feedback.

There's an entire PM2 ecosystem.config.js file in the Wiki you should start with.
pm2 monitis also your friend for looking at the logs.