# Node-Red on remote PC

**URL:** <https://discourse.nodered.org/t/node-red-on-remote-pc/96505>\
**Category:** General\
**Created:** [10 April 2025 14:44 UTC](https://discourse.nodered.org/t/node-red-on-remote-pc/96505 "2025-04-10T14:44:05Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [16 April 2025 21:42 UTC](https://discourse.nodered.org/t/node-red-on-remote-pc/96505/21 "2025-04-16T21:42:34Z")

</div>

> [@tgottie](#):
>
> One work around I discovered while using a syslog server is using ncat to send a message from one machine to another under port 514

This seems rather extreme given the existing communications features already built into Node-RED. Websockets, TCP, UDP, http-in/-response, MQTT.

> [@tgottie](#):
>
> but with the new version of mosquito i have had issues getting to work on node-red

What issues, hundreds of us if not more rely on Mosquitto and have done for over a decade. Other than occasionally making a mistake with some default settings between versions, I've never had any issues with it.

> [@tgottie](#):
>
> I havent play played much with hiding the terminal window for node-red, but should work.

Much easier to set it as a service using nssm or run it under PM2.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [15 July 2025 21:43 UTC](https://discourse.nodered.org/t/node-red-on-remote-pc/96505/22 "2025-07-15T21:43:34Z")

</div>

Closed on 15 July 2025 21:43 UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/node-red-on-remote-pc/96505.md?page=1)
