Unable to Launch Vision from Launcher

Ignition
,
1

Hello Everyone,

One of the client PC is having something weird going on and I was wondering if someone has experience/suggestion about it.

This client has Launcher installed and we I configure to install new client project, the project is imported but it never opens when I try. This is the screen I see. Also, as you can see I am pinging the gateway at the same time and it seems fine.

image
image1390×712 173 KB

Things I tried already :
deleted all the cache, .ignition folder, even the vision client launcher was reinstalled.
Gateway opens and pings really normally.
Tried launching project from another gateway and it works fine.
Tired launching the project from another client and it works completely fine.
The client is remote on network.

The issue with specific client not being able to launch specific gateway projects.

any updates/suggestions/remarks are welcome.

2

Check the computer’s firewall, then if there are any other firewalls on your network i would look there.

3

anything in the logs?

4

@josborn, no issues if the Firewall. It has the exact same policy for any remote gateway within the company where one gateway works completely fine and another one doesn’t.
@andrews, not really anything in the gateway logs.

5

Maybe something in the user permissions of that stops it from opening?
Can you try different user account on same machine

6

Is the gateway actually listening on that IPv6 address?

7

how would I test that ?

8

let me try doing that

9

In a Linux server I would look at the output of netstat -lnp to see what is listening and on what addresses/ports. I’m sure there’s something similar for Windows.

1 Like
10

Something like netstat -op IPv6 should do the trick I would think.

Note @kaushik.shah you should run this on the Gateway server if that isn’t obvious

2 Likes
11

yup, tried that, don’t see anything there. But all the other active connections are also under netstat -a

image
image890×603 31.4 KB

12

yup, from gateway server

13

That means Ignition isn't listening on IPv6, and attempts to reach it with an IPv6 address (shown in your OP) will fail.

1 Like
14

That is just the default ping in Windows 10 going with IPv6
Do the ping with a -4 on the end to get the IPv4 address
Then try connecting to it by the IPv4 address instead of the netbios name.

1 Like
15

The issues was with IPv6. The VPN user was trying to connect only supported IPv6 whereas all the Ignition Server connection were IPv4.

Thanks for the support everyone.