Regenerating Machine Certificate

It been almost @ weeks now and I have been getting the same error message, “Regenerating Machine Certificates. Local detected invalid Docker Machine TLS certificates and is fixing them now.” It stuck here for the whole time, I have tried some of the fixes stated on other treads but to no avail. Is there anything else to do?

Thanks

Hey @Nyarkoweb

What version of Local is installed? You might try updating to the most recent version of Local from the releases page.

If updating Local doesn’t work for you, Can you please provide your local-by-flywheel.log file? See
How do I retrieve Local’s log file?” for instructions on how to do so.

– Ben

Hey, I have saw the update yesterday and I have updated it, but it didn’t change anything. My log is below.

I was not allowed to paste all from the log but I have attached it below.

local-by-flywheel.log (321.9 KB)

And here is a sample of it

 Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 8:57 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 8:57 PM EST - info: [main/docker-machine] Running  C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe stop local-by-flywheel
Dec 18, 2018, 8:57 PM EST - info: [main/docker-machine] Stopping "local-by-flywheel"...
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 8:57 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 8:57 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 8:57 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 8:57 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:57 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - info: [main/docker-machine] Machine "local-by-flywheel" was stopped.
Dec 18, 2018, 8:58 PM EST - info: [main/docker-machine] child process exited with code 0
Dec 18, 2018, 8:58 PM EST - info: [main/docker-machine] Checking Boot2Docker.iso hash
Dec 18, 2018, 8:58 PM EST - info: [main/docker-machine] Running  C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel
Dec 18, 2018, 8:58 PM EST - info: [main/docker-machine] Starting "local-by-flywheel"...
Dec 18, 2018, 8:58 PM EST - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Dec 18, 2018, 8:58 PM EST - info: [main/docker-machine] (local-by-flywheel) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - error: [renderer/app] TypeError {
  mode: 'callers',
  name: 'TypeError',
  message: 'Cannot read property \'props\' of undefined',
  stack:
   [ TypeError {
       url: null,
       func: 'traceKitWindowOnError',
       args: [],
       line: null,
       column: null } ],
  incomplete: true } true
Dec 18, 2018, 8:58 PM EST - info: [main/index] Shutting Down VM
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-0-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-0-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-1-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-1-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-2-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-2-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-3-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-3-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-3-1\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-3-1\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-0-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-0-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-1-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-1-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-2-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-2-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-0\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-1\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-1\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-2\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-2\out\environment.js
Dec 18, 2018, 9:00 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:00 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:00 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 9:00 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 9:00 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 9:00 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:00 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:00 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:00 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:00 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:00 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 9:00 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 9:00 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:00 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:00 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:00 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:00 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:00 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 9:00 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 9:00 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:00 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:00 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:00 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:00 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:00 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:00 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 9:00 PM EST - info: [main/index] Shutting Down VM
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-0-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-0-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-1-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-1-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-2-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-2-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-3-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-3-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-3-1\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\custom-1-3-1\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-0-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-0-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-1-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-1-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-2-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-2-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-0\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-1\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-1\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Loading Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-2\out\environment.js
Dec 18, 2018, 9:03 PM EST - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-2\out\environment.js
Dec 18, 2018, 9:04 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'machine-halted' ]
Dec 18, 2018, 9:04 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] Checking Boot2Docker.iso hash
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] Running  C:\Users\nyark\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] Starting "local-by-flywheel"...
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] (local-by-flywheel) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] Machine "local-by-flywheel" was started.
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] Waiting for SSH to be available...
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] Detecting the provisioner...
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] checking IP
Dec 18, 2018, 9:04 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:04 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 9:04 PM EST - info: [main/docker-machine] checked IP 192.168.95.100

Dec 18, 2018, 9:04 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 9:04 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:04 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:04 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:04 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:04 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 9:04 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 9:04 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 9:04 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 9:04 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:04 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:04 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:04 PM EST - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Received Docker Machine env. 
Dec 18, 2018, 9:04 PM EST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.95.100:2376": dial tcp 192.168.95.100:2376: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.


Dec 18, 2018, 9:04 PM EST - info: [main/set-docker-env] Going to regen machine certs.
Dec 18, 2018, 9:04 PM EST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Dec 18, 2018, 9:05 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n',
  stderr: '' }
Dec 18, 2018, 9:05 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:05 PM EST - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Dec 18, 2018, 9:05 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:05 PM EST - info: [main/set-docker-env] Getting Docker Machine env.
Dec 18, 2018, 9:05 PM EST - info: [renderer/RegenMachineCertsPage] Regenerate machine cert response. 
{ error: null,
  stdout:
   'Regenerating TLS certificates\nWaiting for SSH to be available...\nDetecting the provisioner...\nCopying certs to the local machine directory...\nCopying certs to the remote machine...\nSetting Docker configuration on the remote daemon...\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually <ip>:2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configura

I’m having the same problem. I’ve tried uninstalling Local and reinstalling it several times and each time I get the same message “error creating machine: Error checking the host: error checking and/or regenerating the certs: there was an error validating certificates for host “192.168.93.100.2376”: dial tcp 192.168.93.100.2376: i/o timeout”
Did you ever figure it out? This is what my log is saying local-by-flywheel.log (12.3 KB)

I’m getting this message also. I’ve made no changes to my system (OSX 10.14.3). I’ve tried uninstalling Local by Flywheel and Virtual Box (several times each) and deleting required files etc.

Why is there no response from Flywheel on this? I think it’s time to look elsewhere for reliable software. Flywheel has been flaky for me since I first installed it 2 months ago.

I wanted to say that I found a solution in the forum that did seem to work for me on macOS. The article below links to the actual steps.

Hey @Nyarkoweb

Thanks for your patience on this. Were you able to get it figured out?

If you still are having issues, can you try the solution that @richb-hanover suggests above?

– Ben

I ended up downloading the VM and docker using a different site, then re-installed flywheel. I’m not sure why but it works beautifully now and I don’t use a different program!

1 Like