As there was no response but topic seems still to be open:
@JohsH Could you add a more detailed explanation what you are doing? I also think we need to separate things like @webiq-sk mentioned.
Which ctrlX CORE app versions are used?
Which WebIQ version is used?
You are accessing ctrlX CORE web UI and WebIQ HMI on the other side?
Could you add screenshot of the browser pages you are accessing showing the error?
What is the URL you try to access for HMI?
Can you reproduce the behavior mentioned, so we could do some tests?
Did you test any of the solutions mentioned?
For general warning when accessing ctrlX CORE web UI see attachment in the first answer of @Sgilk.
The similar problems mentioned by @HmiGuide were caused by iframe integration in HMI screens and restrictive behavior of chrome/chromium based browsers. These are solved by using ctrlX CORE version 1.20 and WebIQ version 2.14. In that case the HMI is fully integrated in our reverse proxy and both sources are collected to a single one.
... View more