Kitematic: Start-up stops at 99% - IP: 192.168.99.100 is not in the cert's list: 192.168.99.101

[dev-guy]

This guaranteed to happen if I reboot and run Kitematic again. Dropping dev and recreating it works; however, I would like to avoid the productivity loss of reinstalling containers every time I reboot.

Cannot connect to the Docker Engine. Either the
VM is not responding or the connection may be
blocked (VPN or Proxy): Hostname/IP doesn't
match certificate's altnames: "IP: 192.168.99.100 is
not in the cert's list: 192.168.99.101"

[mchiang0610]

@dev-guy We are testing out a pre-release that should fix this problem! Do you mind giving it a try?

https://github.com/kitematic/kitematic/releases/download/v0.5.27-intel-nic/Kitematic-0.5.27-intel-nic.zip

Let me know if you are still running into the issue after.

[mchiang0610]

Also consolidating this issue to: https://github.com/kitematic/kitematic/issues/236

[ynagarjuna2012]

I have the same problem how ever if I reinstall everything seems to be fine ..But again I will face the issue

Waste of time

Please fix the the issue

[FrenchBen]

@ynagarjuna1995 It looks like you had multiple machines setup at some point - Whenever the certs above appears, you can always regenerate the certs via: docker-machine regenerate-certs default

[peter-mw]

i have the same error

IP: 192.168.99.100 is not in the cert's list: 192.168.99.101

After running docker-machine regenerate-certs default its fixed

[HimaniSinghai]

Thanks

[ccaspanello]

@peter-mw Thank you for that command. Saved me from blowing away my VM and starting from scratch. You rock!

[Happpy]

@peter-mw Thank you for the command, also saved my work

[peter-mw]

hi, i'm glad it worked, but credit for the command goes to @FrenchBen

[muzfr7]

It saved my day! Cheers..

[heliortf]

Really really thanks +1

[dinesh1gore]

Thanks! It really helped.