# Updating ignition OPC server discovery endpoint

**URL:** <https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [January 22, 2026, 4:55pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487 "2026-01-22T16:55:00Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Leor\_Fishman](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@Leor\_Fishman](https://forum.inductiveautomation.com/u/Leor_Fishman)\
**Post date:** [January 22, 2026, 4:55pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/1 "2026-01-22T16:55:01Z")

</div>

```python
Connecting with UA Discovery
Ignition's OPC UA server is initially, and intentionally, difficult to discover on new installations. To aid with discovery attempts, a separate unsecured endpoint is available, allowing UA clients a means of finding the server. When attempting to discover the server, the endpoint URL should include "/discovery" at the end:

opc.tcp://192.168.2.134:62541/discovery

```

Is there any way to set this to bind to localhost instead or additionally?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 22, 2026, 5:04pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/2 "2026-01-22T17:04:16Z")

</div>

Change the bind address to "localhost" on the OPC UA Server Settings page. Any change here requires a gateway restart.

> **[OPC UA Server Settings​ - Ignition's OPC UA Server | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/opc-ua/ignitions-opc-ua-server#opc-ua-server-settings)**
>
> Ignition's OPC UA server, provided by the OPC UA module, allows an ignition installation to utilize Ignition's various device driver modules. In addition, with the module installed, OPC UA clients can connect to Ignition's UA server, exposing any...

"localhost" is the default, so if it's not already configured for localhost then somebody has changed it.

---

<div class="post-metadata">

**Author:** ![Leor\_Fishman](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@Leor\_Fishman](https://forum.inductiveautomation.com/u/Leor_Fishman)\
**Post date:** [January 22, 2026, 5:05pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/3 "2026-01-22T17:05:39Z")

</div>

It is set to localhost on their page –

is ```Ignition's OPC UA server is initially, and intentionally, difficult to discover on new installations. To aid with discovery attempts, a separate unsecured endpoint is available, allowing UA clients a means of finding the server. When attempting to discover the server, the endpoint URL should include "/discovery" at the end:

opc.tcp://192.168.2.134:62541/discovery```

not accurate?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 22, 2026, 5:08pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/4 "2026-01-22T17:08:30Z")

</div>

That's example text. Everybody's gateway says the same thing. Or user manual, or wherever that is quoted from. I don't even know.

---

<div class="post-metadata">

**Author:** ![Leor\_Fishman](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@Leor\_Fishman](https://forum.inductiveautomation.com/u/Leor_Fishman)\
**Post date:** [January 22, 2026, 5:13pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/5 "2026-01-22T17:13:43Z")

</div>

That’s a quote from the docs –

I’m asking because external browsing of the discovery endpoint on _localhost_ from a node opc client was failing with

Error: End point must exist opc.tcp://localhost:62541/discovery securityMode = None securityPolicy = [http://opcfoundation.org/UA/SecurityPolicy#None](http://opcfoundation.org/UA/SecurityPolicy#None)

even after the server was set to anonymous access allowed.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 22, 2026, 5:16pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/6 "2026-01-22T17:16:06Z")

</div>

Not sure exactly what that error message implies, but it doesn't sounds like you're getting far enough for authentication to matter. If you can get a Wireshark capture and maybe some logs from Ignition that will help clear things up.

---

<div class="post-metadata">

**Author:** ![Leor\_Fishman](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@Leor\_Fishman](https://forum.inductiveautomation.com/u/Leor_Fishman)\
**Post date:** [January 22, 2026, 5:24pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/7 "2026-01-22T17:24:07Z")

</div>

I don’t think it’s an authentication issue, i think it’s that external services can’t browse discovery on localhost, they need to use that weird IP from the docs?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 22, 2026, 5:29pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/8 "2026-01-22T17:29:54Z")

</div>

> [@Leor\_Fishman](#):
>
> they need to use that weird IP from the docs?

No, man... ignore that. If you haven't changed any of the default config, the discovery endpoint URL is `opc.tcp://localhost:62541/discovery`.

If the client is not running on the same server as the gateway you first need to reconfigure the bind address to `0.0.0.0`, restart, and then the endpoint URL you configure for that client will be `opc.tcp://<whateveripaddress>:62541/discovery` where it's whatever IP address you can reach the server at.

---

<div class="post-metadata">

**Author:** ![Leor\_Fishman](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@Leor\_Fishman](https://forum.inductiveautomation.com/u/Leor_Fishman)\
**Post date:** [January 22, 2026, 5:30pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/9 "2026-01-22T17:30:30Z")

</div>

Ok, thanks – so the docs are inaccurate there, then. Just wanted to confirm that.

(Note, i’m quoting [Ignition's OPC UA Server | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/opc-ua/ignitions-opc-ua-server) )

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [January 22, 2026, 5:36pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/10 "2026-01-22T17:36:24Z")

</div>

Well, they're accurate, but maybe instead of using an example IP they need to put a placeholder in the documentation, or just call out that the example is using that IP as the example and that you need to use your own IP address in place of it.

---

<div class="post-metadata">

**Author:** ![Leor\_Fishman](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@Leor\_Fishman](https://forum.inductiveautomation.com/u/Leor_Fishman)\
**Post date:** [January 22, 2026, 5:44pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/11 "2026-01-22T17:44:14Z")

</div>

I see, so by “Ignition's OPC UA server is initially, and intentionally, difficult to discover on new installations. To aid with discovery attempts, a separate unsecured endpoint is available,”

the docs literally just mean ‘adding /discovery to the end of the preexisting endpoints’?

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [January 22, 2026, 5:46pm UTC](https://forum.inductiveautomation.com/t/updating-ignition-opc-server-discovery-endpoint/113487/12 "2026-01-22T17:46:21Z")

</div>

Essentially, yes, that's all they're doing, but the wording could definitely be improved.

Feel free to reach out to them at [docs@inductiveautomation.com](mailto:docs@inductiveautomation.com) and give them suggestions/improvements on this and anything else that's confusing as it will help others who also encounter the same problems interpreting the documentation.
