Visualizer in console showing error on simplified docker compose file

1

Hi there,

I just installed the simplified docker-compose network and created a simple webservice which appears to work ok:

helen.ziti
helen.ziti1482×292 12.8 KB

However in the console, if I look at the Visualizer for the identiy, it shows an error from th edge router to the webtest:

visualizer1
visualizer11437×618 34.1 KB

The webserver I added to the simplified-docker compose file is very basic:

nginx

Is this a bug in the visualizer in the console or is something not working correctly for me ? The last logs of me accessing the web service show:

logs1
logs11849×375 149 KB

I also tried this with the web-test-blue webserver from the full docker compose file (putting it into the simplified docker compose file) and got the same issue.

However if I set up the full docker compse network with red and blue ZTNA, the visualizer appears to work ok for identities - showing green all the way for connected services and identities.

So im just trying to see if there is a problem with that simplified docker file and the visualizer or is something not working correctly for me - even though connecting to the service works ??

thanks

2

Has anyone got the simplified docker tutorial running with a test service that can check if the visualiser working in the console all the way through for an identity ?

Cheers

3

Hi @colin,

I haven't tried the visualizer myself in a minute. I'm not personally too familiar with what it does nor how but I can get someone who does to look at this. :slight_smile: I'll point this out and ask someone to follow up.

4

Thanks for that, as I said, it works ok on the full blue/red ziti network - I was working off the fact that identities are working for access to services when I can see the visualiser following the service all the way through - that was my assumption.

So when not working in the simplified ziti, yet me going to the service works anyway, it is confusing me whether things are set up correctly or not !

5

Hi @colin. I'll look into this issue. Let me set up the same scenario (simplified Docker), and test it.

6

I have the same problem. I have just upgraded from 0.28.1 in a test instance to 1.1.5 (haven't gone above that yet) and can confirm I have the same issue, even though I can connect to the service.
Haven't tried a new service to see if it is and old service definition related or not, but a new identity does not resolve it.

7

@colin @gooseleggs The root cause of this issue has been identified in visualizer's router hosted service link functions. We are working on the issue and have created defect #487 to track it.

8

@gooseleggs Thank you for confirming and looking at the issue

@harishnf thanks for working on this to fix - i use it a lot to confirm services in the GUI