Dev modes and OPC connections Endpoint missing

Hello,

I am configuring development modes. I have two instances dev and crash. I sync via git from dev to crash.

I configure everything in dev and move it to crash, which is a playground. When I sync, I overwrite everything in crash.

I am configuring local loopback OPC connection. On dev the server is on 62542 port and on crash it is at 19542. I create override I cannot set directly I get:

Error retrieving discovery server information for endpoint Url 'opc.tcp://localhost:19542

Of course. I use advanced, I set, OK. I sync to crash, I get:

UaException: status=Bad_ConfigurationError, message=no matching endpoints found

Wierd. There is no endpoint setting:

When I go back to dev, I see there is no endpoint setting on the active dev override. But I can see endpoint setting on the non active crash override.

I think it worked day before yesterday. It is weird I cannot edit active’s dev override endpoint.

Any ideas where to go?

UaException: status=Bad_ConfigurationError, message=no matching endpoints found	at com.inductiveautomation.ignition.gateway.opcua.client.ManagedClientKt.initialize(ManagedClient.kt:157)	at com.inductiveautomation.ignition.gateway.opcua.client.ManagedClientKt.access$initialize(ManagedClient.kt:1)	at com.inductiveautomation.ignition.gateway.opcua.client.ManagedClientKt$initialize$1.invokeSuspend(ManagedClient.kt)	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)	at java.base/java.lang.Thread.run(Unknown Source)

I delete all Override and I see Endpoint settings:

I click Create Override for dev (active), it connects, but I cannot edit Endpoint anymore.

Is this a BUG? Or how it should work?

This issue with overrides for OPC UA connections not showing the endpoint option should be resolved in the upcoming 8.3.2 version. There is currently an early release candidate 8.3.2-rc1 that should have this fix currently in as testing it on my end I can see the available endpoint option for the deployment mode.