The auto-discovery of endpoints should be excluding the host “host.docker.internal” automatically, which it doesn’t.
@Prosys this is a feauture request to you guys.

Apparently the Servers tries to bind to the same port twice which let’s the whole start fail.

08/10/2022 10:59:00.661 ERROR [SimulationServer] com.prosysopc.ua.app.simserver.i [] – Could not start the application.
java.lang.IllegalStateException: Expected the service f [FAILED] to be RUNNING, but the service has FAILED
at com.google.common.util.concurrent.AbstractService.checkCurrentState(AbstractService.java:379) ~[guava-29.0-jre.jar:?]
at com.google.common.util.concurrent.AbstractService.awaitRunning(AbstractService.java:303) ~[guava-29.0-jre.jar:?]
at com.google.common.util.concurrent.AbstractIdleService.awaitRunning(AbstractIdleService.java:164) ~[guava-29.0-jre.jar:?]
at com.prosysopc.ua.app.simserver.i.b(SourceFile:94) ~[app-5.2.2-9.jar:5.2.2-9]
at com.prosysopc.ua.app.simserver.SimulationServer.main(SourceFile:32) ~[app-5.2.2-9.jar:5.2.2-9]
at com.prosysopc.ua.app.Main.main(Main.java:13) ~[prosys-opc-ua-simulation-server-5.2.2-9.jar:5.2.2-9]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84) ~[i4jruntime.jar:?]
at com.exe4j.runtime.WinLauncher.main(WinLauncher.java:94) ~[i4jruntime.jar:?]
at com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:25) ~[i4jruntime.jar:?]
Caused by: java.lang.IllegalStateException: Expected to be healthy after starting. The following services are not running: {FAILED=[b [FAILED]]}
at com.google.common.util.concurrent.ServiceManager$ServiceManagerState.checkHealthy(ServiceManager.java:782) ~[guava-29.0-jre.jar:?]
at com.google.common.util.concurrent.ServiceManager$ServiceManagerState.awaitHealthy(ServiceManager.java:594) ~[guava-29.0-jre.jar:?]
at com.google.common.util.concurrent.ServiceManager.awaitHealthy(ServiceManager.java:322) ~[guava-29.0-jre.jar:?]
at com.prosysopc.ua.app.simserver.services.f.startUp(SourceFile:77) ~[app-5.2.2-9.jar:5.2.2-9]
at com.google.common.util.concurrent.AbstractIdleService$DelegateService$1.run(AbstractIdleService.java:61) ~[guava-29.0-jre.jar:?]
at com.google.common.util.concurrent.Callables$4.run(Callables.java:119) ~[guava-29.0-jre.jar:?]
at java.lang.Thread.run(Thread.java:834) ~[?:?]
Suppressed: com.google.common.util.concurrent.ServiceManager$FailedService: b [FAILED]
Caused by: com.prosysopc.ua.server.ar: Failed to initialize server endpoint: opc.tcp://host.docker.internal:53530/OPCUA/SimulationServer
at com.prosysopc.ua.server.aq.cq(SourceFile:2239) ~[app-5.2.2-9.jar:5.2.2-9]
at com.prosysopc.ua.server.aq.AO(SourceFile:2254) ~[app-5.2.2-9.jar:5.2.2-9]
at com.prosysopc.ua.server.aq.start(SourceFile:2115) ~[app-5.2.2-9.jar:5.2.2-9]
at com.prosysopc.ua.app.simserver.server.d.start(SourceFile:186) ~[app-5.2.2-9.jar:5.2.2-9]
at com.prosysopc.ua.app.simserver.server.d$b.startUp(SourceFile:96) ~[app-5.2.2-9.jar:5.2.2-9]
at com.google.common.util.concurrent.AbstractIdleService$DelegateService$1.run(AbstractIdleService.java:61) ~[guava-29.0-jre.jar:?]
at com.google.common.util.concurrent.Callables$4.run(Callables.java:119) ~[guava-29.0-jre.jar:?]
at java.lang.Thread.run(Thread.java:834) ~[?:?]

Deleting serverSettings.xml would not help.
It got generated with.

I tried
false
and it would not help.
I tried

127.0.0.1

and it would not help.

I tried

localhost

and it would not help.

I tried pausing Docker Desktop and it would not help.
I tried quitting Docker Desktop and it would not help.
(always the exception with trying to bind to host.docker.internal)

I noticed this section in my hosts file:
# Added by Docker Desktop
10.254.81.31 host.docker.internal
10.254.81.31 gateway.docker.internal
# To allow the same kube context to work on the host and the container:
127.0.0.1 kubernetes.docker.internal

commenting these out, I still get
ERROR: Failed to initialize server endpoint: opc.tcp://:53530/OPCUA/SimulationServer

I gues workaround should be limiting the auto-discovery, but I don’t know how to configure it properly. Please advise.

I am willing to set up a Remote Call, feel free to get in touch with me.
I also have some code I could borrow, that I use for my own OPC UA Server (stuff in conjunction with NetworkInterface.getNetworkInterfaces()).

You can try adding “opcTcpAddress” tag with the IP value you wish to use inside “opcTcpAddresses” along with setting “useAllIPAddresses” to false in serverSettings.xml.

Thanks for reporting the issue and we will see if we can get some improvements in future releases. And yes the forum does not like XML.

Just as a heads up, this still does not seem to be solved with 5.4.6-148
I was using 2.2.2 because of this, but then I ran into Bind problems with 2.2.2 from one day to another.
There is nothing listening on 53530 as far as I can tell with “netstat” and PowerShell Get-NetTCPConnection.
Unfortunately, the UI stays empty if this initial Bind problem occurs, and I need to edit serverSettings.xml manually.
What is the syntax for this? the following does not have any effect? (trying to restrict the bind addresses to listen to)

127.0.0.1:53530

false