3rd party connection to remote Ignition OPC UA Server

I know this topic seems to get raised every couple of months but as far as I can tell I've followed the steps discussed in other posts to no avail. I've got a gateway running the opc ua server running on a remote machine (ip: 192.168.95.42) and I'm trying to connect to it currently using UaExpert (with the eventual intention of connecting using some C# I've written) and the /discovery endpoint. My server settings currently look like this:


I've restarted the gateway since applying them.

In UaExpert I'm attempting discovery at opc.tcp://192.168.95.42:62541/discovery and it is just failing. Interestingly trying to use that address for the gateway's own OPC connection also fails but works fine at opc.tcp://localhost:62541/discovery. I've turned off the firewalls on both ends for the time being also.

Is there anything else I'm just completely missing to make this work correctly?

Are you sure 192.168.95.42 is an IP address assigned to a network adapter on this machine? Are there multiple NICs?

Can you zip and upload your wrapper.log file(s)?

Yes I think so? I'm not so great with network related questions if I'm honest but that's the only IP address that's listed when I run ipconfig in a command prompt window. Here's my zipped wrapper.log file:
wrapper.zip (106.0 KB)

Can you zip all the logs? Hoping to see back to the last gateway startup.

Also make sure there's no 3rd party firewalls enabled. Another way to check what IPs are available to Ignition is to look at the Status->Overview page under the Environment section. There should be an entry named "Detected NICs" with a list of all your IP addresses that Ignition sees.

From the machine where UaExpert is installed, can you open the gateway web page at 192.168.95.42 ? If not, a network path between the machines may not exist.

Oh, sorry, I grabbed the wrong file, here are all the logs.
wrapper.zip (488.9 KB)

These logs don't suggest a gateway restart since you last set the Bind Address to 0.0.0.0:

[17:25:49.407]: Binding endpoint opc.tcp://IncorezServer:62541 to localhost:62541 [Basic256Sha256/SignAndEncrypt] module-name=OPC-UA
[17:25:49.440]: Binding endpoint opc.tcp://IncorezServer:62541/discovery to localhost:62541 [None/None] module-name=OPC-UA
[17:25:49.440]: Binding endpoint opc.tcp://localhost:62541 to localhost:62541 [Basic256Sha256/SignAndEncrypt] module-name=OPC-UA
[17:25:49.441]: Binding endpoint opc.tcp://localhost:62541/discovery to localhost:62541 [None/None] module-name=OPC-UA
[17:25:49.441]: Binding endpoint opc.tcp://127.0.0.1:62541 to localhost:62541 [Basic256Sha256/SignAndEncrypt] module-name=OPC-UA
[17:25:49.442]: Binding endpoint opc.tcp://127.0.0.1:62541/discovery to localhost:62541 [None/None] module-name=OPC-UA

But these are weeks old. You again only zipped one file instead of all the files, so maybe this is just the oldest.

Yes, I can.

Also @michael.flagler, it seems to be in the "Detected NICs".

1 Like

Oh lord, I've just realised I've been restarting the wrong gateway :upside_down_face:

...And now it's working as intended, thanks again folks, thankfully it's nearly friday.

1 Like