I've been trying to launch a designer from the designer launcher but I've consistently been getting this error:
I'm running Ignition on Windows 11 23H2. I saw other forum posts with the same error and have looked through the designerlauncher.log file. The logs look like this:
I think the download may be failing for some reason because I've also tried to download directly through various browsers to no avail. I've also tried downloading it via wget, which provided a tad more insight:
I've tried clean installs of all Ignition related software (Gateway/Designer Launcher) and I'm running the latest versions (8.1.39/1.1.39) and have tried the process without any kind of firewall turned on. At this point I'm open to any and all suggestions of things I can try.
Firewalls almost never impact access to localhost. But anti-virus and IT security lockdowns often do. Also, are you sure the launcher is at least as new as the gateway?
Yes, the launcher was newly downloaded and reinstalled, the version numbers seem to indicate that it is the newest version. I figured it probably wasn't a firewall issue but just to remove any doubt I turned it off. The anti-virus doesn't seem to indicate that it's detected/blocked anything. I'm not ruling out it being IT Security related but I'm not sure where to look now.
I seem to have resolved the issue. If anybody else has the displeasure of having ESET Endpoint Security installed (which I wouldn't if it were up to me), it seems that despite claiming that it allows the download from http://localhost:8088/system/launchbin/launchclient.jar (or whatever server:port configuration the gateway is running on), it does not.
Disabling the Web access protection fixed the issue, though that's obviously not perfect as a long term solution. I personally have configured ESET to not scan .jar files for now as I believe there's an issue in ESET and I'm going to raise a support ticket with them.
I think this is an issue introduced with the newest version of the launchclient.jar fwiw, possibly the fact that it's now signed?
1 Like
It would be remarkably ironic if improving our security by signing the jar was itself causing security scanners to balk, but it's sadly extremely plausible.
2 Likes
