# Webdev to webdev API call failure: unable to find valid certification path to requested target

**URL:** <https://forum.inductiveautomation.com/t/webdev-to-webdev-api-call-failure-unable-to-find-valid-certification-path-to-requested-target/111521>\
**Category:** Ignition\
**Tags:** webdev\
**Created:** [October 16, 2025, 3:11pm UTC](https://forum.inductiveautomation.com/t/webdev-to-webdev-api-call-failure-unable-to-find-valid-certification-path-to-requested-target/111521 "2025-10-16T15:11:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 16, 2025, 5:43pm UTC](https://forum.inductiveautomation.com/t/webdev-to-webdev-api-call-failure-unable-to-find-valid-certification-path-to-requested-target/111521/2 "2025-10-16T17:43:41Z")

</div>

Is your Linux gateway even able to bind to the HTTPS port? By default services on Linux can't bind to ports \< 1024. You have to set up your service files to allow it with some extra capabilities:

> [@Setting Up Ignition Gateway on Ubuntu VPS](https://forum.inductiveautomation.com/t/setting-up-ignition-gateway-on-ubuntu-vps/96870/6):
>
> Consider uninstalling and starting over, with the executable installer. Here's one of my recent install command lines (running as root): ./ignition-8.1.38-linux-64-installer.run -- location=/usr/share/ignition user=ignition serviceName=ignition textMode=true Couple notes: I always override the defaults for user, location, and service name. Do as you see fit, but note that what I show are not the defaults. Always put the following in a SystemD override (not in the installed unit file): …

---

_[View the full topic](https://forum.inductiveautomation.com/t/webdev-to-webdev-api-call-failure-unable-to-find-valid-certification-path-to-requested-target/111521)._