Cannot start a new workspace

[ywg1990]

When I try to run a new workspace, I get a 'Failed,certificates are required for https connection'.

Reproduction Steps:

1.run che.

2.run workspace

3.run stop

Observed behavior:

Che version: 4.3.4
OS and version: win7
Eclipse version: Mars

[ghost]

@ywg1990 Looks like VirtualBox issues.

Can you click on Docker QuickStart icon that you should have on your desktop after installing Docker Toolbox?

You will see a new terminal with docker-machine starting a new VM. Can you then successfully run docker commands, like docker ps?

[thyeun]

@ywg1990, i think you need to regenerate the cert for the docker-machine "Che" by using the command "docker-machine regenerate-certs Che", before you run the "Che run".

hope it help you up.

[TylerJewell]

Yes, @ywg1990 - was going to also suggest the cert regeneration issue with
docker-machine posted by Thomas. Can you give that a shot?

Tyler Jewell | CEO | tyler@​codenvy.​com | 9​78​.8​84​.53​55

On Mon, Jul 11, 2016 at 9:35 AM, Thomas Yeun notifications@github.com
wrote:

@ywg1990 https://github.com/ywg1990, i think you need to regenerate the
cert for the docker-machine "Che" by using the command "docker-machine
regenerate-certs Che", before you run the "Che run".

hope it help you up.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1686 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAX9ChcksLWAZP_4MZfRv2xA4buUTZRoks5qUnDsgaJpZM4JHtx3
.

[ghost]

@ywg1990 any update on this one? Were you able to get past this error?

[ywg1990]

@eivantsov I execute the command docker ps, then I get this.

[ywg1990]

@thyeun I execute the command "docker-machine regenerate-certs Che", then I get this.

[thyeun]

@ywg1990 after you regenerate, can you manage to start machine che, with "Che run"?

[ywg1990]

@thyeun I execute the command "docker-machine regenerate-certs Che". It always stay on "Detecting the provisioner...".

[ghost]

@ywg1990 Can you remove all docker-machines, and then remove host only adapters in virtual box Settings > Network. So far, this is a Docker-Machine/Virtual box problem.

[thyeun]

@ywg1990 it look like you have more than one docker-machine, the best way to make it work is to remove all and re-do.

[ywg1990]

@eivantsov @thyeun It WORKS! Thanks a lot! I remove all and re-do.

[ghost]

@ywg1990 Good to know!