Im having problem on the display. this is using customized embed Web Page
On the server side its good.
But in the end user side view this is what im encountering.
In Web.config add below line in <httpProtocol>
<add name="X-Frame-Options" value="ALLOW" />
thanks for the reply.
in here i add the line or replace the SAMEORIGIN to ALLOW?
because when i tried this both are not working :
adding another line for the "allow" command
When replacing the SAMEORIGIN to ALLOW
Still the same error
What is the URL configured for? If it is using https://localhost/... then you won't be able to connect as localhost translates to the machine performing the data request. We'd recommend that you try configuring as https://<hostname>/....
Thanks for the reply,
Tried this screenshot below.
I believe Jesse is referring to the targetURL from the embedWebPage custom symbol.
This is line 43 when viewed from our GitHub page: targetURL: "https://techsupport.osisoft.com", in the sym-embedWebPage.js. Of course, it's subject to difference if you changed the source.
The user side web browser also checks whether your webpages are coming from the common/single origin. What is the target URL?
I see, sorry, Attach is my screenshot below.
This was by the help of one of the osisoft support also. He help me regarding on this post PI Vision: How to change image per asset in pi vision?
Seth Sauder able to help me with this. But I was unable to double check it when accesing outside server.
change already the target url;
but still encountered same error.
If you have your targetURL as https://localhost/PIVision/KAM/alabang.png, then try changing localhost with your web server URL.
From above picture, it would be similar to: https://pi-wbserver/PIVision/KAM/alabang.png
Hi sir Jinmo,
Did your procedure sir, but still encountered same error. Left side is outside server then Right side is the web server.
I also change on my AF with the assets on it. instead of localhost i use also the web server (hostname), but when i run it in pivision. On server itself connect theres an error reportedly it was block and not signed by a valid sec certificate. then outside server it is only blank.
I see that your asset is different for the 2 machines. Does your Bulacan asset also have URL Image configured with hostname as : https://pi-wbserver/PIVision/KAM/<XXX>.png?
I feel that this is related to your security issue by your setup. Could you try connecting in both cases via your webservers' hostname?
Unifying the URL is important as we specify all contents come from a single source. Browsers usually have a built-in security feature, where it blocks cross origin resources.
As far as I know, the localhost/hostname and IP Addresses are different except in the web server itself. In the client node, localhost means the each client node so it will not find images there.
Thanks! It already works when using the hostname.
But what if on the DNS side it has already configured it, and with new alias for the url.
the default pivision url https://localhost/pivision. Then ill configure the url of the pivision on the DNS and name it https://pi.vision.sample/pivision , this will be the only the url that will access by any outside users. When accessing the new url the error the same, images will still not be viewable.
example screenshot: this when i access the new url name and connect outside network.
If you wish to configure PI Vision so that your users connect via DNS Alias, then this issue really needs help from your IT department. But please find below pointers as well:
KB01574 - Configuring Kerberos for DNS Aliases (ANAME and CNAME)
KB01691 - Configuring PI Vision to be accessed by a DNS Alias https://livelibrary.osisoft.com/LiveLibrary/content/en/vision-v2/GUID-14FF804E-61C3-4A1C-AF3B-6FCB0AE65752
PI Vision 2017 R2 Admin Guide - Configure database to support connections through an alias
You will most likely need a good certificate as well that's well accepted from the client machines as well.
Retrieving data ...