Perspective - Some view in localhost url is different with using IP url

Ignition
1

Hi,

The below is called using http://localhost:8088/data/perspective/client/xxxx

image
image1742×838 117 KB

While the below is called using http://192.168.xx.xxx:8088/data/perspective/client/xxxx where i have used the ip address of the pc instead of localhost.

image
image1860×894 122 KB

The above urls should show the same view but it is not so. I have tried clearing the .ignition folder and java cache but yet the problem remains.

Any help is greatly appreciated.

Thanks in advance.

2

Have you tried opening them in Incognito/PrivateMode to see if the problem persists?

It sounds like an internal Ignition navigation issue where either you are navigating views and not paths, or maybe you have some scripting that is firing and navigating you elsewhere.

3

From where are you running the designer? These sorts of nuances are most quickly caught and corrected if you don't run the designer on the same machine as the gateway. (If you are working in a laptop or local workstation, the gateway should be a VM or a container with an actual, separate, IP address.)

4

Oh yes you are right Benjamin!

It has navigated to another view meant for remote user to access which the view has not been updated to the latest. I think I have to find other work around instead of creating different views.

Thanks for the help!

1 Like
5

I have a pc onboard a boat which runs the perspective application and the gateway.

Would it be a better design if the GW is running on a VM instead ? And if so, do i need separate licenses for ignition ?

6

Having the gateway and client application on the same machine is not a problem, as long as that hardware can handle the workload. It is the designer that should not be run from the same machine, as "localhost" has peculiarities that can produce these kinds of problems.

7

You shouldn't keep two views for this unless they're wildly different views. If it's just to limit privileges, then set read/write permissions of tags based on security zones, and disable buttons and inputs based on reading the CanWrite tag prop of the tags. The tag writes won't go through without this, but this gives visual indication to the user.( I'd also add a security icon as well)