My client and I seem to be having the same issue as above.
Unable to launch from the designer launcher, but if I create a bat file with the following, it works.
C:\Users\jae\.ignition\cache\resources\runtimes\11.0.6\bin\java.exe -classpath C:\Users\jae\.ignition\clientlauncher-data\launchclient.jar -Djavaws.sr.gateway.addr.0=https://xxxxxxxx:443 -Djavaws.sr.launchts=1589913325154 -Djavaws.sr.main=com.inductiveautomation.ignition.designer.DesignerStartupHook -Djavaws.sr.platform.edition= -Djavaws.sr.platform.plugins= -Xms64M -Xmx1024M -Djavaws.sr.memory.init=64M -Djavaws.sr.memory.max=4096M -Dsun.java2d.d3d=false -Dsun.java2d.noddraw=false -Djavaws.sr.screen=0 -Djavaws.sr.scope=D com.inductiveautomation.ignition.client.launch.BootstrapSwing
Contents of the designerlauncher.log
There is a AWS load balancer in front. What's weird is that it works on some systems but not others. Why does it act differently between the designer launcher and command prompt?
INFO [GatewayConnect ] [2020/07/16 12:05:37]: Attempting to connect to gateway https://xxxx.com:443...
INFO [GatewayConnect ] [2020/07/16 12:06:07]: Retry attempt 1 to gateway https://xxxx.com:443 failed
INFO [GatewayConnect ] [2020/07/16 12:06:07]: Attempting to connect to gateway https://xxxx.com:443...