Hello !
I can`t load designer on my PC, i get error like in attachment 
Ignition 8.0.0 (b2019040718)
Windows 10

Hello !
I can`t load designer on my PC, i get error like in attachment 
Ignition 8.0.0 (b2019040718)
Windows 10

Are you able to actually connect to the Gateway at the specified address in a browser? I’ve only ever seen this dialog appear in a few instances:
I think that IP address is wrong, it is not my IP address, maybe taken from VPN networks.
Correct IP for this gateway is 192.168.2.117 or localhost
The IP which is shown in your screenshots - is it the IP listed for the Designer you’re trying to launch? Could you please post a photo of your Designer Launcher configuration? Something like this:
Errors happens before I can see this window.
It sounds like you might have set a “default” Application somehow. if you examine your .ignition/clientlauncher-data/designer-launcher.json file, do you see a value other than an empty String for global.default-application?

If so, change that value to be an empty String, and then try launching the Designer Launcher again.
Also, just to be clear, you have already downloaded and installed the Designer Launcher for 8.0.0 from your Gateway, correct - and you’re not using a 7.9.X Designer Launcher?
I’ve had this error before: Sometimes the launcher picks the wrong IP address, and it never recognizes that a host is localhost unless 127.0.0.1 is the only address assigned. Even when it does use my true local IP, that’s useless if I happen to go to a coffee shop for the afternoon, since a 10.* will turn into a 192.* on the interface.
169.* is a special address that means “Automatic IP” when DHCP fails, so it’s almost certainly picking up an IP from an interface that isn’t actually connected to anything. Delete those and re-add them, cross your fingers and hope for the best.
I`m still using 7.9.x designers with clientluncher for my customer.
{
"global": {
"default.application": "Ignition-DF",
"multicast.address": "231.1.1.1",
"multicast.receive.port": 4446,
"lock.configuration": false,
"logger.level": "TRACE",
"client.defaults": {
"timeout": 30,
"retries": -1,
"init.heap": null,
"max.heap": null,
"use.custom.jre": null,
"custom.jre.path": null,
"jvm.arguments": [
"-server -XX:MaxPermSize=512m -XX:+UseG1GC"
],
"client.tag.overrides": {}
},
"autoexit": false
},
"applications": [
{
"name": "Ignition-DF",
"description": null,
"main.class": null,
"gateway.info": {
"gateway.name": "Ignition-DF",
"gateway.address": "http://169.254.139.42:8088",
"redundant.gateways": []
},
"window.mode": null,
"timeout": 30,
"screen": null,
"retries": -1,
"init.heap": null,
"max.heap": null,
"sun.java2d.d3d": null,
"sun.java2d.noddraw": null,
"jvm.arguments": [
"-server -XX:MaxPermSize=512m -XX:+UseG1GC"
],
"last.updated": 1541488977765,
"client.tag.overrides": {},
"image.path": null,
"fallback.application": "",
"use.custom.jre": null,
"custom.jre.path": null
}
]
}
Two things here:
This issue was fixed in the 8.0.3 nightly build that was uploaded today (6/17).