# Error after changing port

**URL:** <https://discourse.nodered.org/t/error-after-changing-port/43582>\
**Category:** General\
**Created:** [3 April 2021 00:16 UTC](https://discourse.nodered.org/t/error-after-changing-port/43582 "2021-04-03T00:16:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Andrei](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andrei/32/10446_2.png) [@Andrei](https://discourse.nodered.org/u/Andrei)\
**Post date:** [3 April 2021 01:01 UTC](https://discourse.nodered.org/t/error-after-changing-port/43582/2 "2021-04-03T01:01:30Z")

</div>

The error message in the log indicates permission issue. The reason is that it is necessary root privilege's to use ports below 1024.

Some references:

> [@Raspberry Pi and UDP?](https://discourse.nodered.org/t/raspberry-pi-and-udp/7129/2):
>
> The error is exactly what it says: If you want to use a port number \< 1024, you need to run as root. We generally recommend not to run as root, so if you can, pick a port higher than 1024.

> [@Problems to open port 162 (SNMP-TRAP)](https://discourse.nodered.org/t/problems-to-open-port-162-snmp-trap/31555):
>
> I want to use node-red-contrib-snmp-trap-listener to receive traps via snmp, on port 162, but I get this error "can't open port: 162". I have the same problem with node-red-contrib-syslog, which uses port 514. I have read that only the root user can open privileged ports (1-1024). Is there any way for node-red to open privileged ports without error? Best regards

> [@Modbus TCP Server on port 502](https://discourse.nodered.org/t/modbus-tcp-server-on-port-502/4760/3):
>
> Not to bump an old thread, but for anyone who comes searching, the most likely culprit is needing root access to listen on a port less than 1024, assuming you're running Node-RED on a Linux device.

---

_[View the full topic](https://discourse.nodered.org/t/error-after-changing-port/43582)._