# Localhost:1880 connection refused
**URL:** https://discourse.nodered.org/t/localhost-1880-connection-refused/97195
**Category:** Dashboard
**Created:** [22 May 2025 00:07 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195 "2025-05-22T00:07:28Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@torrmundi](https://discourse.nodered.org/u/torrmundi)
#### Post date: [22 May 2025 00:07 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/1 "2025-05-22T00:07:28Z")
I have embedded Node-Red via SignalK Server running on a RPI3. I can access localhost:3000 to see the SignalK Server. But when I try to access localhost:1880 to see the Node Red dashboard, it says Connection Refused. I’ve also tried 127.0.0.1:1880, and 192.168.50.46:1880 (the RPI WLAN IP address). I tried disabling the firewall (sudo ufw disable), but got the same result. The browser is Chromium. The OS is Ubuntu (Lysmarine BBN package). Any ideas here?
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [22 May 2025 00:46 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/2 "2025-05-22T00:46:47Z")
Welcome to the forum @torrmundi.
That's quite an esoteric setup! Interesting though.
I'm sure you've seen the [Bareboat Necessities documentation](https://bareboat-necessities.github.io/my-bareboat/bareboat-os.html#_nodered) where it says
> NodeRed is installed into SignalK. To use NodeRed login into SignalK by visiting [http://localhost:3000](http://localhost:3000) clicking 'login', choosing 'remember me' session and storing the password in a browser.
And [https://github.com/SignalK/signalk-node-red](https://github.com/SignalK/signalk-node-red) says
> You can access the node-red Admin console by navigating to Webapps on the node server admin console, or use a direct url like [http://localhost:3000/plugins/signalk-node-red/redAdmin/](http://localhost:3000/plugins/signalk-node-red/redAdmin/)
>
> If you install node red dashboard, then the url for the dashboard will be we be [http://localhost:3000/plugins/signalk-node-red/redApi/ui/](http://localhost:3000/plugins/signalk-node-red/redApi/ui/)
Do either of these work for you?
---
### Author:  [@torrmundi](https://discourse.nodered.org/u/torrmundi)
#### Post date: [22 May 2025 12:15 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/3 "2025-05-22T12:15:42Z")
Yes I did see the [http://localhost:3000](http://localhost:3000) link and it works well.
The direct link to node-red admin works in as far as it loads the page for designing flows. But it quickly thereafter says “Lost connection to server, reconnecting in XXs. Try now”. Try now fails. Refreshing the page works, but will lose the connection again.
Oddly, accessing the same page by clicking on Node-Red in the Signalk Webapps page via localhost:3000 brings up the localhost:3000/plugins/signalk-node-red/redAdmin page and it never disconnects.
The [http://localhost:3000/plugins/signalk-node-red/redApi/ui/](http://localhost:3000/plugins/signalk-node-red/redApi/ui/) link doesn’t give any error, but also doesn’t load any dashboard - it’s a totally blank page. Yes, I did add a single button and an audio out dashboard items to my flow1, and then deployed.
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [22 May 2025 13:17 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/4 "2025-05-22T13:17:09Z")
> [@torrmundi](#):
>
> The [http://localhost:3000/plugins/signalk-node-red/redApi/ui/](http://localhost:3000/plugins/signalk-node-red/redApi/ui/) link doesn’t give any error, but also doesn’t load any dashboard - it’s a totally blank page.
.../ui is the url (in a 'normal' installation) for the original dashboard component node-red-dashboard.
If you have the new one @flowfuse/node-red-dashboard i'd expect it to be at .../dashboard
---
### Author:  [@torrmundi](https://discourse.nodered.org/u/torrmundi)
#### Post date: [22 May 2025 13:52 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/5 "2025-05-22T13:52:40Z")
Hmm,
```auto
Cannot GET /plugins/signalk-node-red/redApi/dashboard
```
You lost me at the “@flowfuse/node-red-dashboard” part.
I have node-red-dashboard v3.6.5 installed. Not the @flowfuse/node-red-dashboard.
If I look at settings, On all flows, then edit Node-RED Dashboard, it shows that “This ui\_base node is the main node that all other dashboard widget nodes communicate to.”
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [22 May 2025 16:43 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/6 "2025-05-22T16:43:23Z")
> [@torrmundi](#):
>
> it’s a totally blank page.
Blank pages will often show errors if you open your browsers dev tools and go to the console tab.
---
### Author:  [@torrmundi](https://discourse.nodered.org/u/torrmundi)
#### Post date: [23 May 2025 11:47 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/7 "2025-05-23T11:47:50Z")
Console tab shows 3 errors:
```auto
Failed to load resource: the server responded with a status of 404 (Not Found) - http://localhost:3000/plugins/signalk-node-red/redapi/ui/socket.io/socket.io.js
Refused to execute script from 'http://localhost:3000/plugins/signalk-node-red/redapi/ui/socket.io/socket.io.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled. - http://localhost:3000/plugins/signalk-node-red/redapi/ui/
ReferenceError: io is not defined
at angular.module.service.connect (app.min.js:606:145)
at Object. (app.min.js:605:5924)
at Object.invoke (app.min.js:66:264)
at S.instance (app.min.js:120:161)
at p (app.min.js:94:161)
at g (app.min.js:87:186)
at app.min.js:86:311
at app.min.js:43:199
at m.$eval (app.min.js:177:180)
at m.$apply (app.min.js:177:423)
- http://localhost:3000/plugins/signalk-node-red/redapi/ui/js/app.min.js
```
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [23 May 2025 12:06 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/8 "2025-05-23T12:06:12Z")
This is absolutely an issue for signalk, it is not a node-red issue as such.
The 1st of those errors is the important one, the others are just noise.
The original Node-RED Dashboard (D1) requires [Socket.IO](http://Socket.IO) to function, running via signalk's proxy is failing to find the library.
---
### Author:  [@torrmundi](https://discourse.nodered.org/u/torrmundi)
#### Post date: [23 May 2025 12:44 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/9 "2025-05-23T12:44:54Z")
Thank you for the help.
I'll pursue this further with SignalK follks. I did find the missing resource at /.signalk/node\_modules/.pnpm/socket.io@4.8.1\_bufferutil@4.0.9\_utf-8-validate@5.0.10/node\_modules/socket.io/client-dist/socket.io.js
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [23 May 2025 13:40 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/10 "2025-05-23T13:40:10Z")
Potential problem with that is that it might not be the same version than Node-RED requires. Mismatched [Socket.IO](http://Socket.IO) server and client versions can cause odd issues.
---
### Author:  [@torrmundi](https://discourse.nodered.org/u/torrmundi)
#### Post date: [23 May 2025 15:21 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/11 "2025-05-23T15:21:03Z")
The socket.io.js file says v4.8.1. Is there any way to determine the other side?
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [22 June 2025 15:21 UTC](https://discourse.nodered.org/t/localhost-1880-connection-refused/97195/12 "2025-06-22T15:21:32Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.