# Unable to Launch Vision from Launcher **URL:** \ **Category:** Ignition\ **Tags:** ignition80, vision\ **Created:** [April 19, 2022, 5:45pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602 "2022-04-19T17:45:21Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [April 19, 2022, 5:45pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/1 "2022-04-19T17:45:21Z")
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](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/c/1ca4617da9d5673c4ca7970f0f2ca0c3b60fccfd.jpeg) 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. ---
**Author:** ![josborn](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@josborn](https://forum.inductiveautomation.com/u/josborn)\ **Post date:** [April 19, 2022, 5:48pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/2 "2022-04-19T17:48:53Z")
Check the computer’s firewall, then if there are any other firewalls on your network i would look there. ---
**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\ **Post date:** [April 19, 2022, 5:50pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/3 "2022-04-19T17:50:42Z")
anything in the logs? ---
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [April 19, 2022, 5:58pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/4 "2022-04-19T17:58:03Z")
@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. ---
**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\ **Post date:** [April 19, 2022, 5:59pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/5 "2022-04-19T17:59:55Z")
Maybe something in the user permissions of that stops it from opening? Can you try different user account on same machine ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 19, 2022, 6:16pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/6 "2022-04-19T18:16:40Z")
Is the gateway actually listening on that IPv6 address? ---
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [April 19, 2022, 6:54pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/7 "2022-04-19T18:54:46Z")
how would I test that ? ---
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [April 19, 2022, 6:55pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/8 "2022-04-19T18:55:20Z")
let me try doing that ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 19, 2022, 6:57pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/9 "2022-04-19T18:57:25Z")
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. ---
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [April 19, 2022, 7:07pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/10 "2022-04-19T19:07:05Z")
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 ---
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [April 19, 2022, 8:19pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/11 "2022-04-19T20:19:13Z")
yup, tried that, don’t see anything there. But all the other active connections are also under `netstat -a` ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/d/dd787181f73cac4deeafa6cacd9bf621f16c16f2.png) ---
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [April 19, 2022, 8:19pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/12 "2022-04-19T20:19:36Z")
yup, from gateway server ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 19, 2022, 8:23pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/13 "2022-04-19T20:23:28Z")
> [@kaushik.shah](#): > > don’t see anything there That means Ignition isn't listening on IPv6, and attempts to reach it with an IPv6 address (shown in your OP) will fail. ---
**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\ **Post date:** [April 19, 2022, 8:33pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/14 "2022-04-19T20:33:43Z")
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. ---
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [April 20, 2022, 12:44pm UTC](https://forum.inductiveautomation.com/t/unable-to-launch-vision-from-launcher/58602/15 "2022-04-20T12:44:34Z")
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.