# Serial communication problem

**URL:** <https://discourse.nodered.org/t/serial-communication-problem/33407>\
**Category:** General\
**Created:** [27 September 2020 12:47 UTC](https://discourse.nodered.org/t/serial-communication-problem/33407 "2020-09-27T12:47:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [27 September 2020 20:03 UTC](https://discourse.nodered.org/t/serial-communication-problem/33407/2 "2020-09-27T20:03:39Z")

</div>

This sounds very like a problem a week or two back. Have you configured node red to autostart on boot? If so then if you disable autostart  
`sudo systemctl disable nodered`  
and reboot, then start nodered is it ok? If so then node-red is starting too quickly and the serial port doesn't function for some so far unknown reason. Have a look at this post which tells you how nodered can be delayed on boot, which fixed the problem in this case [Serial woes.. buffer issue?](https://discourse.nodered.org/t/serial-woes-buffer-issue/33141/18)

---

_[View the full topic](https://discourse.nodered.org/t/serial-communication-problem/33407)._