Oct 11, 2018, 7:31 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:31 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:31 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:32 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:32 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:32 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:32 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:32 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:32 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:32 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:32 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:33 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:33 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 7:55 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 7:55 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:55 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:55 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:55 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:55 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 7:55 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 7:56 AM CDT - 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: '' }
Oct 11, 2018, 7:56 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 7:56 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:56 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:56 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:56 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:56 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 7:56 AM CDT - 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: '' }
Oct 11, 2018, 7:56 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 7:56 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:56 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:56 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:56 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:56 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:56 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 7:57 AM CDT - 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: '' }
Oct 11, 2018, 7:57 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 7:57 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:57 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:57 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:57 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:57 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 7:57 AM CDT - 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: '' }
Oct 11, 2018, 7:57 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 7:57 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:57 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:57 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 7:57 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 7:57 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 7:57 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 7:57 AM CDT - info: [main/index] Shutting Down VM
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 8:00 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Oct 11, 2018, 8:00 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'machine-halted' ]
Oct 11, 2018, 8:00 AM CDT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Oct 11, 2018, 8:00 AM CDT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Oct 11, 2018, 8:00 AM CDT - info: [main/docker-machine] Starting "local-by-flywheel"...
Oct 11, 2018, 8:00 AM CDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Oct 11, 2018, 8:00 AM CDT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Oct 11, 2018, 8:01 AM CDT - info: [main/docker-machine] Machine "local-by-flywheel" was started.
Oct 11, 2018, 8:01 AM CDT - info: [main/docker-machine] Waiting for SSH to be available...
Oct 11, 2018, 8:01 AM CDT - info: [main/docker-machine] Detecting the provisioner...
Oct 11, 2018, 8:01 AM CDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Oct 11, 2018, 8:01 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:01 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:01 AM CDT - info: [main/docker-machine] checking IP
Oct 11, 2018, 8:01 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:01 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:01 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:01 AM CDT - info: [main/docker-machine] checked IP 192.168.94.100

Oct 11, 2018, 8:01 AM CDT - 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: '' }
Oct 11, 2018, 8:01 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:01 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:01 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:01 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:02 AM CDT - info: [main/index] Shutting Down VM
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 8:02 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Oct 11, 2018, 8:02 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'machine-halted' ]
Oct 11, 2018, 8:02 AM CDT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Oct 11, 2018, 8:02 AM CDT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Oct 11, 2018, 8:02 AM CDT - info: [main/docker-machine] Starting "local-by-flywheel"...
Oct 11, 2018, 8:02 AM CDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Oct 11, 2018, 8:02 AM CDT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Oct 11, 2018, 8:03 AM CDT - info: [main/docker-machine] Machine "local-by-flywheel" was started.
Oct 11, 2018, 8:03 AM CDT - info: [main/docker-machine] Waiting for SSH to be available...
Oct 11, 2018, 8:03 AM CDT - info: [main/docker-machine] Detecting the provisioner...
Oct 11, 2018, 8:03 AM CDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Oct 11, 2018, 8:03 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:03 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:03 AM CDT - info: [main/docker-machine] checking IP
Oct 11, 2018, 8:03 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:03 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:03 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:03 AM CDT - info: [main/docker-machine] checked IP 192.168.94.100

Oct 11, 2018, 8:03 AM CDT - 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: '' }
Oct 11, 2018, 8:03 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:03 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:03 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:03 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:03 AM CDT - info: [main/index] Shutting Down VM
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 8:06 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Oct 11, 2018, 8:06 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'machine-halted' ]
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] Starting "local-by-flywheel"...
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] Machine "local-by-flywheel" was started.
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] Waiting for SSH to be available...
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] Detecting the provisioner...
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Oct 11, 2018, 8:06 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine stop local-by-flywheel
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] Stopping "local-by-flywheel"...
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] Machine "local-by-flywheel" was stopped.
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] child process exited with code 0
Oct 11, 2018, 8:06 AM CDT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] Starting "local-by-flywheel"...
Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Oct 11, 2018, 8:07 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] checking IP
Oct 11, 2018, 8:07 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:07 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:07 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] checked IP 192.168.94.100

Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] Machine "local-by-flywheel" was started.
Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] Waiting for SSH to be available...
Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] Detecting the provisioner...
Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Oct 11, 2018, 8:07 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:07 AM CDT - 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: '' }
Oct 11, 2018, 8:07 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:07 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:07 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:07 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:07 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] checking IP
Oct 11, 2018, 8:07 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:07 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:07 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:07 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:07 AM CDT - info: [main/docker-machine] checked IP 192.168.94.100

Oct 11, 2018, 8:07 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:08 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:08 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:08 AM CDT - 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: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:08 AM CDT - 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: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:08 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:08 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:08 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:08 AM CDT - 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: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:08 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:08 AM CDT - 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: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:08 AM CDT - 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: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:08 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:08 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:08 AM CDT - 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: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:08 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:08 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:08 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:08 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:08 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:08 AM CDT - info: [main/index] Shutting Down VM
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 8:11 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Oct 11, 2018, 8:11 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'machine-halted' ]
Oct 11, 2018, 8:11 AM CDT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Oct 11, 2018, 8:11 AM CDT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Oct 11, 2018, 8:11 AM CDT - info: [main/docker-machine] Starting "local-by-flywheel"...
Oct 11, 2018, 8:11 AM CDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Oct 11, 2018, 8:11 AM CDT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] Machine "local-by-flywheel" was started.
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] Waiting for SSH to be available...
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] Detecting the provisioner...
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Oct 11, 2018, 8:12 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:12 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] checking IP
Oct 11, 2018, 8:12 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:12 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:12 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] checked IP 192.168.94.100

Oct 11, 2018, 8:12 AM CDT - 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: '' }
Oct 11, 2018, 8:12 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:12 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:12 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:12 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine stop local-by-flywheel
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] Stopping "local-by-flywheel"...
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] Machine "local-by-flywheel" was stopped.
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] child process exited with code 0
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] Starting "local-by-flywheel"...
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Oct 11, 2018, 8:12 AM CDT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:13 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:13 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:13 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:13 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:13 AM CDT - error: [main/downloader/DownloaderQueue]  TypeError: Cannot read property 'importImage' of undefined
    at Promise (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/downloader/DownloaderQueue.js:1:11455)
    at new Promise (<anonymous>)
    at DownloaderQueue.importDownloadedImage (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/downloader/DownloaderQueue.js:1:10003)
    at DownloaderQueue.downloadItem (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/downloader/DownloaderQueue.js:1:5792)
    at _0x28114c.then (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/downloader/DownloaderQueue.js:1:4672)
    at <anonymous>
Oct 11, 2018, 8:13 AM CDT - warn: [EnvironmentFlywheel] 
Oct 11, 2018, 8:13 AM CDT - info: [main/docker-machine] Machine "local-by-flywheel" was started.
Oct 11, 2018, 8:13 AM CDT - info: [main/docker-machine] Waiting for SSH to be available...
Oct 11, 2018, 8:13 AM CDT - info: [main/docker-machine] Detecting the provisioner...
Oct 11, 2018, 8:13 AM CDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:13 AM CDT - 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: '' }
Oct 11, 2018, 8:13 AM CDT - info: [main/downloader/DownloaderQueue] Cancelling environment Docker image import.
Oct 11, 2018, 8:13 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:13 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:13 AM CDT - info: [main/docker-machine] checking IP
Oct 11, 2018, 8:13 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:13 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:13 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:13 AM CDT - info: [main/docker-machine] checked IP 192.168.94.100

Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:13 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:13 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:13 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:13 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:13 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:14 AM CDT - 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: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - 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: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:14 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:14 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:14 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:14 AM CDT - 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: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:14 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:14 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:14 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:14 AM CDT - 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: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - 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: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:14 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:14 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:14 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:14 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:14 AM CDT - 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: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:14 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:14 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:14 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:14 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:14 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:14 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:14 AM CDT - 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: '' }
Oct 11, 2018, 8:14 AM CDT - 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: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:14 AM CDT - info: [main/index] Shutting Down VM
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-0-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-1-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-2-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/custom-1-3-1/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-0-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-1-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-2-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-0/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-1/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Loading Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/EnvironmentLoader] Successfully Loaded Environment: /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/environments/flywheel-1-3-2/out/environment.js
Oct 11, 2018, 8:17 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Oct 11, 2018, 8:17 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'machine-halted' ]
Oct 11, 2018, 8:17 AM CDT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Oct 11, 2018, 8:17 AM CDT - info: [main/docker-machine] Running  /private/var/folders/cw/3ht1n9rj601755wxqky6n3gh0000gr/T/AppTranslocation/961F37FB-71A5-4B96-92B7-BC19AC2354C8/d/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Oct 11, 2018, 8:17 AM CDT - info: [main/docker-machine] Starting "local-by-flywheel"...
Oct 11, 2018, 8:17 AM CDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Oct 11, 2018, 8:17 AM CDT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Oct 11, 2018, 8:18 AM CDT - info: [main/docker-machine] Machine "local-by-flywheel" was started.
Oct 11, 2018, 8:18 AM CDT - info: [main/docker-machine] Waiting for SSH to be available...
Oct 11, 2018, 8:18 AM CDT - info: [main/docker-machine] Detecting the provisioner...
Oct 11, 2018, 8:18 AM CDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Oct 11, 2018, 8:18 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:18 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:18 AM CDT - info: [main/docker-machine] checking IP
Oct 11, 2018, 8:18 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:18 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:18 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:18 AM CDT - info: [main/docker-machine] checked IP 192.168.94.100

Oct 11, 2018, 8:18 AM CDT - 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: '' }
Oct 11, 2018, 8:18 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:18 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:18 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:18 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:18 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:18 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:18 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:18 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:18 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:18 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:18 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:18 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:19 AM CDT - 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: '' }
Oct 11, 2018, 8:19 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:19 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:19 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:19 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:19 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:19 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:19 AM CDT - 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: '' }
Oct 11, 2018, 8:19 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:19 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:19 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:19 AM CDT - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Received Docker Machine env. 
Oct 11, 2018, 8:19 AM CDT - 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.94.100:2376": dial tcp 192.168.94.100:2376: i/o timeout
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.


Oct 11, 2018, 8:19 AM CDT - info: [main/set-docker-env] Going to regen machine certs.
Oct 11, 2018, 8:19 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'invalid-certs' ]
Oct 11, 2018, 8:20 AM CDT - 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: '' }
Oct 11, 2018, 8:20 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:20 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Running\n', stderr: '' }
Oct 11, 2018, 8:20 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:20 AM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Oct 11, 2018, 8:20 AM CDT - info: [main/index] Shutting Down VM