# UDP Port Binding Fail

**URL:** <https://forum.inductiveautomation.com/t/udp-port-binding-fail/61453>\
**Category:** Ignition\
**Created:** [July 2, 2022, 12:20am UTC](https://forum.inductiveautomation.com/t/udp-port-binding-fail/61453 "2022-07-02T00:20:17Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 14, 2022, 12:32am UTC](https://forum.inductiveautomation.com/t/udp-port-binding-fail/61453/4 "2022-07-14T00:32:10Z")

</div>

I recommend the AmbientCapabilities clause in this comment (same topic):

> [@Automation Professionals' Advanced Modbus Driver](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312/22):
>
> Instead of running as root, I recommend adding the following in your systemd configuration: [Service] AmbientCapabilities=CAP\_NET\_BIND\_SERVICE

You can stay on the standard HTTP and HTTPS ports while not running as root.

---

_[View the full topic](https://forum.inductiveautomation.com/t/udp-port-binding-fail/61453)._