Hi,

Are you trying to start the application in a “server machine” that doesn’t have a display? The application isn’t designed for such environments, it will fail to start without the display. All interactions with the application are designed to be done via the UI. Technically the installer works in cli due to it being made with install4j, but the app does not.

Now then, there is a “non-official flag”

--headless

(or -h) that will disable the UI module, then most likely it manages to start, but then you run with default configuration. Technically you might be able to get something if you copy some of the configuration files from another machine that has a display (though note that the application’s own certificate has to be the one generated on that machine by the application), but any failures due to this or editing the files manually is outside of the scope of support.

Once the application manages to start, you will find configuration, logs etc. at /home/USER/.prosysopc/prosys-opc-ua-simulation-server/ for the USER who started the app. Note that there is no intended way to shut down the application properly without the UI (but things shouldn’t go bad if you just terminate it).